sysex

[mbncp]

I didn't really look closely in the sdk so far but I was wondering if it's possible to hook a MIDI port.
The idea would be to trap sysex messages on input and convert them to nrpn or some other coding sequence and do the same on an output port.

Any idea ?
Thanks

[Deric]

Not sure what you mean by "hook a MIDI port" - but you can monitor incoming MIDI messages, receive and send SYSEX, etc.

[mbncp]

I need to trap the midi flow before it hit's a track and also once it leaves a track to a midi out port.

Normaly with have something like this:

Midi In -> Track -> Midi Out

I would need to do this

Midi In -> myplug -> Track -> myplug -> midi out

And not on all midi ports, only the ones I want to.

When I say Track, I mean anything between MIDI in and MIDI out.

This would prevent me to do it in an external app using a virtual port:

midi in -> my app-> virtual midi in -> reaper -> virtual midi out -> my app -> midi out

[spacelabstudio]

Originally Posted by mbncp

I need to trap the midi flow before it hit's a track and also once it leaves a track to a midi out port.

Normaly with have something like this:

Midi In -> Track -> Midi Out

I would need to do this

Midi In -> myplug -> Track -> myplug -> midi out

And not on all midi ports, only the ones I want to.

When I say Track, I mean anything between MIDI in and MIDI out.

This would prevent me to do it in an external app using a virtual port:

midi in -> my app-> virtual midi in -> reaper -> virtual midi out -> my app -> midi out

I'm not sure if you can do that with the SDK but I'm pretty sure you can with JS, which is much easier to deal with. Check out JS.

chris

[mbncp]

Originally Posted by spacelabstudio

I'm not sure if you can do that with the SDK but I'm pretty sure you can with JS, which is much easier to deal with. Check out JS.

chris

It is indeed to be used in a JS plug, but JS doesn't receive/send sysex messages.
That's why the idea to convert first to something else that would be interpreted by a JS plug.