Blue Cat Audio

Moka Disco Express · Post by **Moka Disco Express** » Sun Oct 05, 2014 9:30 pm

I did not find detailed info about it, but we assume that it can also handle midi sysex messages?
If it is not currently possible, take it as a feature:
for example having the ability to have both midi by host and hardware for both input and output, and the ability to handle midi sysex.

rrichard63 · Post by **rrichard63** » Mon Oct 06, 2014 12:40 am

Moka Disco Express wrote:I did not find detailed info about it, but we assume that it can also handle midi sysex messages?
If it is not currently possible, take it as a feature:
for example having the ability to have both midi by host and hardware for both input and output, and the ability to handle midi sysex.

I don't think the default MIDI implementation handles sysex. But I do think you could expand the implementation yourself. Look for the file Midi.hxx. On Windows systems it is in \My Documents\Blue Cat Audio\Blue Cat's Plug'n Scripts\Scripts\library. It includes event handlers for note off, note on, control change, program change, and pitch wheel. It would be easy to add a sysex event type. The functions to process sysex events might be easy or hard depending on what you want them to do.

If you decide to do this, use a different file name, for example MyMidi.hxx. At the top of your script, write

#include "../library/mymidi.hxx"

instead of

#include "../library/midi.hxx"

Hope this helps,
Bob Richard

Blue Cat Audio · Post by **Blue Cat Audio** » Mon Oct 06, 2014 7:55 am

MIDI Sysex is not "officially" supported right now, because some hosts actually handle sysex data differently from MIDI messages. However, depending on your host application, it may indeed work sending sysex as consecutive 3 bytes packets.

rrichard63 · Post by **rrichard63** » Mon Oct 06, 2014 12:45 pm

Blue Cat Audio wrote:MIDI Sysex is not "officially" supported right now, because some hosts actually handle sysex data differently from MIDI messages. However, depending on your host application, it may indeed work sending sysex as consecutive 3 bytes packets.

Thank you for this information. Does this also apply to MMC (MIDI machine control)?

Blue Cat Audio · Post by **Blue Cat Audio** » Mon Oct 06, 2014 1:17 pm

MMC being Sysex data, it is not sure that it is fully supported in all hosts (we haev not tested yet). Some hosts are handling sysex in very specific ways and we have not checked it out yet. But you may want to give it a try and see if messages go thru.

gnd2 · Post by **gnd2** » Wed Oct 08, 2014 9:34 am

Dear Blue Cat Audio.

Is it possible to use Script to send audio between instances of plugin on different tracks? For example, to pick audio on track1 at insert plugin position, and route it to track2 to be insert into signal chain at plugin insert?
I would use this to temporarily route audio from insert slot to another channel's insert, and bounce it to another track. Would this be possible with script?

Blue Cat Audio · Post by **Blue Cat Audio** » Thu Oct 09, 2014 9:13 am

It is currently not possible to share audio data between scripts, so I am afraid this is not possible. Anyway, please be aware that such routing under the hood (not known by the host) requires additional buffering and will lead to potential synchronization issues between tracks, depending on how the host manages the tracks and the order in which plug-ins are processed.

Blue Cat Audio · Post by **Blue Cat Audio** » Thu Oct 16, 2014 8:37 am

Blue Cat's Plug'n Script intro offer has been extended: get the plug-in with 25% off until Sunday evening! Don't miss it!

Blue Cat Audio

KVR Audio

Blue Cat's Plug'n Script Unleashed, with Audio and MIDI Scripting Inside!