That's fine for a single instance of AL, but less fine when there are multiple instances in place because we do all the work to set up the state machines in every instance, and then forget about them entirely in all but our lead instance (the one with an OSC offset of 1, for instance). This does not make me happy.
I tried doing
Code: Select all
getParameter(getParameterID('OSC Port Offset'))
Code: Select all
sendOSC(pathToLeadInstance, '/exec', 'registerInstance', getParameterID('OSC Port Offset'))
Hmm this should work, but it feels kludgy as heck and relies on the MIDI script being up and running before the GUI script (fixable with a timer if it isn't) and on it not dropping any OSC messages, which seems slightly hopeful given that OSC is transmitted over UDP (but sort of doable by randomising the timer to hopefully avoid everything arriving at once).
Which is a long-winded way of asking if it would be possible to expose the OSC Offset (and ideally the base port too because that could allow for distributing far more robust scripts) to the MIDI Scripting environment?