Standalone MIDI problem
Hi,
I'm finishing a pedagogical app, which is basically a block diagram-style front-end for Reason Subtractor. It uses MIDI CC msgs to from the Max to Reason, with the "From Max 1" MIDI out. Because of Reason's limitations, the communication is only 1-way.
Because it has such a narrow use, I didn't provide a way to set the MIDI out from Max– I used the the "From Max 1" argument to the MIDI out objects. But when I build the application, that port changes its name to the one I gave the app ("from Reason Subtractor 1"). Thus, the app is no longer sending MIDI to Reason.
Obviously, I can just change the port name in the argument to "Reason Subtractor 1". But then when I open the patch to edit, that MIDI port changes back to "from Max 1", so it doesn't match the argument again. For various reasons, I'm using a few different [noteout] and [ctrlout] objects scattered around the patch. So then every time I open the patch to edit, the MIDI out port has to be changed on all of those objects.
Outside of re-working the patch to use central MIDI out object, is there any other way around this problem? I do a fair amount of internal MIDI between apps, so I'm thinking it might come up again sometime in a more complex patch.
Thanks,
Brian
If You are on Mac, try IAC driver instead.
The main advantage is that IAC is allways active,
ports "from ..." " to ..." get only created when the Standalone starts.
You can also send message containing midi device name as symbol
to all midi objects in the patch.
Thanks, good idea– but IAC didn't work properly. Somehow, there is what I think is intense MIDI feedback from Reason, probably in note msgs. Everything in the patch is the same, except I changed the argument of all [noteout] and [cntrlout] to the IAC bus. Never had this happen with it, so very confused...
If You think too many midi data is being sent to IAC port,
maybe You could create several instances of IAC busses and split data between them.