From the original SynthMaker forum (2004–2014), with its members’ names and dates.
matti ·
Schematics compiled to VST or VSTi seem to send out midi just fine, but all sysex commands disappear. Can someone please confirm this?
Hoping for a quick fix as this is totally blocking my synths sysex loaders.
Another way of sending sysex out is to have a Midi-Out port inside the VST. But unfortunately that causes crackles in the ASIO output. Another bug perhaps?
DigitalWhiteByte ·
I was just working on this thing lately, I'm using a midi out to send the sysyex out, but I do not cause any crackling. I noticed that in Reaper seems to receive directly from the primitive trig sysex out, but no message is passed. However it is not a new thing, but it's always been a limit of SM. 🙁
rl ·
To which destination do you send sys-ex? External devices should work (at least did, when I checked last time). Sys-ex to the host highly depends on the limitations of the VST specification / VST host.
matti ·
rl wrote: To which destination do you send sys-ex? External devices should work (at least did, when I checked last time). Sys-ex to the host highly depends on the limitations of the VST specification / VST host.
Yes, you could be right. It might just be a limitation of Reapers sysex spec. I haven't tested that out yet.
Anyhow, if I'm sending midi out to an external device from the VST or VSTi, the ASIO driver starts to crackle(try it with plenty of notes.. just a couple won't do any damage). I'm guessing it has to wait for the midi commands to terminate before it can release the focus from the plugin, and this causes crackles because it cant keep up with the latency(tho it does it with any latency.. seems like a synchronizing problem). I'm using a usb-midi interface right now.. ill soon try it on a pci-system.
When i disable the SM-plugin the crackles stop. They also stop if i select "None" as the midi-device, or enable the mode where Reaper renders plugins ahead of time on multiple cores... but that ofcourse messes the midi timing completely.
I'm on a system with 64bit Win7, 3ghz quadcore.
rl ·
I just checked: VST synthesizer on one track in Orion sequenzer, on the other track a midi plugin sending sys-ex directly to the midi interface. No problem, no crackles. (XP SP3 32 bit). Maybe a driver issue.
DigitalWhiteByte ·
I also have an x64 system, I remember that at the beginning I also had problems with crackling sound. I solved it by removing the power saving option that adjusts the CPU as a percentage according to the load. However Reaper is perhaps the only host that supports iteration midi sysex transmission total, to the host VST plugins and VST host to plugin. Reaper for me is making great strides.
DigitalWhiteByte ·
matti wrote: Anyhow, if I'm sending midi out to an external device from the VST or VSTi, the ASIO driver starts to crackle(try it with plenty of notes.. just a couple won't do any damage). I'm guessing it has to wait for the midi commands to terminate before it can release the focus from the plugin, and this causes crackles because it cant keep up with the latency(tho it does it with any latency.. seems like a synchronizing problem). I'm using a usb-midi interface right now.. ill soon try it on a pci-system.
When i disable the SM-plugin the crackles stop. They also stop if i select "None" as the midi-device, or enable the mode where Reaper renders plugins ahead of time on multiple cores... but that ofcourse messes the midi timing completely.
I'm on a system with 64bit Win7, 3ghz quadcore.
Check your system with this http://www.thesycon.de/deu/latency_check.shtml
matti ·
DigitalWhiteByte wrote: Check your system with this http://www.thesycon.de/deu/latency_check.shtml
I've already done several stuff like that. Can't remember if i've used that particular tool but I've ran some similar tests and there were no latency issues with my system.
I've already bypassed the problem by using my plugin only for sending and receiving sysex. So there's no other midi data going thru it(notes or cc, etc). This way there's no crackles when i sequence.
Odd thing tho about SM. My midi drivers seem to be fully multiclient, but SM won't open a port more than once(between several instances.. different plugins). And even when a port is deselected it still remains as a "used port". It's not releasing the ports properly. So it seems the SM's midi functions might still need some tweaks.
All in all i got to steer around my crackle problem. Took some time to spot it tho. Now I'm back to sailing with a steady 64 sample latency 🙂
matti ·
Recent developments... I changed to Cubase5. There's no way of sending data out of a plugin, except through SM's midi-out port. Unfortunately that causes audiostream instability(crackles) on all latency settings. So it seems the only way for my sysex librarians to work is if Outsim fixes the Midi issues described.. 😝
(I also tried all virtual midi-cables i could find to solve the issue, but it seems they don't support sysex either.. odd. Am i the only one still using HW synths??)
Wrote something here? To have a post removed or your name hidden, write to [email protected].
SynthMaker