Page 1 of 1

Ableton won't respond to Lemur system realtime midi message

Posted: 29 Jul 2013 19:34
by RonF
I have searched extensively for an answer to this....hoping someone may have some insight....

I created two simple custom buttons in a lemur template: Start and Stop. I assigned each one to a midi message, one to midi start and one to midi stop (system realtime messages).

Using MidiMonitor-app on my mac, I can see that the proper message is being sent by the template via Dameon 1 (as assigned). However, when I send the message into Ableton Live, which is set to EXT tempo sync (I am sending a midi clock signal into Live via a separate midi port from an Octatrack), Live won't respond to or recognize the start/stop commands. However, if I press start or stop on the Octatrack itself...Live does respond and act as expected.

Yes, Dameon 1 is set up as an active port for both sync and remote in Live's preferences.

Interestingly, I have a similar template in TouchOSC, with these same exact two buttons, and Live responds to that just fine!

Don't know if its relevant, but for full disclosure, I have the iPad in an Alesis I/O dock....but the messages are not sysex, and I'm using the Dameon wireless connection anyways....so I don't think the IO Dock is a factor.

Any ideas why Live would not respond to the messages? They don't even seem to "register" as an incoming message in Live. In other words, when Live is in EXT sync mode, any system realtime commands cause the virtual LED's just to the left of the EXT 'button' to light orange. A clock signal, or a stop/start/continue signal will cause these "LED's" to flash. With the Octatrack, and with Touch OSC, they flash as expected, and Live responds as expected. With the Lemur Dameon connection: Nothing.

Any advice?