Dear all
I am using Ableton and a Remote Script and an Ipad as controller device.
I have recognized a strange behaviour of the button widget (configured as toggle - also checked with push and tap - same behaviour) sending midi:
When want to trigger a mute button of the selected channel, each press the widget sends the values 127,1,0
With this, the mute button does not change it's state. It only flickers one time, but reverts back to it's previous state.
When I use Midi Designer (ipad Midi App) it works as expected. Midi Designer does only send 127 or 1 depending of the state.
Does anybody use OpenStage Control in conjunction with Ableton Live + Remote Scripts. This strange behaviour occurs only with buttons. Faders work as expected.
That's not very clear to me, what are the button's on/off/preArgs properties ?
MIDI Monitor Log:
Can you enable the server's debug option and copy the messages printed in the console instead, it should provide similar informations but from OSC's point of view.
With this, the mute button does not change it's state. It only flickers one time, but reverts back to it's previous state.
This happens when the buttons receives its "off" value.
In "tap" mode, the button only sends its "on" value and blinks once, it also blinks once when it receives its "off" value.
On a sidenote you should not specify the "path" option in the server's midi config unless you don't want to use the built-in in midi binary. Python and python-rtmidi are not needed since v1.7.
On mac (and linux) you don't need to use IAC, you can create midi virtual ports directly from OSC by writing "OSC:virtual" instead of "OSC:1,1", could you please try that as it could eliminate possible routing errors.
