SWS's MidiToReaControlPath Souce Code

[mschnell]

Is same available and legally usable for enhancing it ?

Thanks,
-Michael

[mschnell]

@ Xenakios :

What I have in mind is a plugin that features three sliders:
- Midi channel
- CC # "mute"
- CC # "unmute"

When receiving a Midi CC message with fitting Channel and CC # "mute", it will mute the track denoted in the CC val. Same with "unmute".

I did - extremely simple - workalike ReaScripts for mute and unmute, so I do know that simply two API calls need to be done for that. But using the scripts need "MidiToReaControlPath" and hooking actions, which of course is not really user friendly for the "Reaper Live" toolbox I intend to publish (of course free of charge).

As I know that you are experienced with such stuff and have all the tools in place, maybe it's really easy for you to put this together. What do you think ?

-Michael

[Xenakios]

Originally Posted by mschnell

maybe it's really easy for you to put this together. What do you think ?

It's always bit of a pain to do new plugin projects, unfortunately. I am not even sure if you mean a VST plugin or a Reaper extension plugin, though...?

MidiToReaControlPath isn't a plugin by SWS, by the way, it was done by Jeffos. I don't think the source code is available.

[nofish]

Yeah, your best bet is probably to try to ask Jeff(os) directly.

https://www.cockos.com/team.php

e.g.
https://fr.linkedin.com/in/jean-fran...ague-697236129

[mschnell]

Unfortunately AFAIK, Jeffos is not available at all, any more.

And MidiToReaConttrolPath is special in that it is a VST (receiving Midi Messages in the normal VST way) that additionally uses the Reaper API (Pushing Midi Messages onto the Reaper Control Path). This obviously is possible, but supposedly needs some spacial care.

-Michael

[azslow3]

It probably use StuffMIDIMessage API call for commands and just bypassing otherwise.
There is no comments it should be used specially, so I guess it is safe to use it from whatever place.