Send sysex to vst~?

Miscbeginner
Michael DeFiore's icon

Michael DeFiore

Hi,

Is it possible to send sysex to a vst loaded into [VST~]?

A group created a Virus C emulator (called Osirus) and the group advised the emulator can't be controlled by external programs due to ableton not being able to send sysex to a VST.

So I was thinking of helping them out and creating a Max object to take sysex in directly from Max, and send the MIDI directly to the emulator through VST~.

But before I go down that path wanted to find out from the experts here if sending sysex to the VST~ object was even possible?

If so, seems like this would be an easy patch:

[Imp.midiin] --> [VST~] and we're done. That would bypass the entire Ableton midi stack and get around the lack of ableton sysex support.

Thanks,
Mike

Roman Thilenius's icon

Roman Thilenius

"midievent" still has a limit of 4 list elements.

Michael DeFiore's icon

Michael DeFiore

Thanks Roman.

Maybe [sysexin] --> [VST~]?

Source Audio's icon

Source Audio

forget sysex & vst in live or max.
If you have enough time and good reason, make sysex - vst parameter converter.

Roman Thilenius's icon

Roman Thilenius

then you can use a CC controller to remote sounddiver which sends sysex to a max4live device which can transform sysex into CC again to control the plug-in. no, wait.

NeedMoreCepstrum's icon

NeedMoreCepstrum

Or we could just add a [sysexevent]? It really should be a simple as distinguishing between param240 and sysex status byte.

Or is there a deeper limitation that I'm not aware of?

Roman Thilenius's icon

Roman Thilenius

as you almost said yourself in the other thread will the implementation of sysex for the vst~ object most likely end up under the good old "midievent".


eventually it is not even a big change but only not filtering it and allowing messages longer than the current 24 bytes?

sysex is present in the VST API since 2.4