Ableton Forum

While chasing down another problem, I've been looking at the MC display sysex that Live sends to the controller, and it appears Live makes very inefficient use of the protocol. Not so great on slower machines.

Live updates the entire upper or lower MC display line whenever even a single character changes. This results in sending repeated long sysex messages to the controller at a high rate.

The protocol includes a display-offset byte, which allows for updating the display from any specific character, for any desired number of characters. Thus a changing parameter can just update the required number of characters, resulting in considerably shorter sysex messages.

Something to look at when optimizing for a future update, perhaps?

Heyo. We seem to be grappling with some of the same problems. REALLY hoping you might be able to share a few thoughts.

I'm trying to get my BCR-2000 control surface set up to control my Oberheim Matrix-1000. I've been using a combination of a sysex editor/lib for the Matrix and MIDI-OX to program the BCR via it's "learn" function.

With me so far?

The BCR seems to "learn" the sysex messages sent from the ed/lib in that it will register "GOOD" upon recieving an incoming string. Bummer is that the BCR can't display the exact string which makes troubleshooting a pain in the ass.

So with a given message programmed in to a given controller on the BCR, I try to route it thru Live to the Matrix. The MIDI recieve indicator on Live does not register. Furthermore, the Matrix itself does not see any incoming MIDI being transmitted by the BCR.

I noticed that you've found some shortcomings in the way that Live handles sysex and thought that maybe you could shed a little light on this one.

Thanks,

d.