Quirk with raw decimal MIDI message in M4L // Live 12 ?

Brian Bender's icon

Brian Bender

10月 20 2024 | 8:06 午後

Hello! I am working on a patch which controls a bit of hardware via MIDI. I have a pretty realized control schema up and working, including reverse engineering the sysex. We now have a successful implementation which is intermediating Sysex dumps via JS and a byte table in a json dict etc, my colleagues and I have gone pretty far with this.

The manual for the HW device provides a raw MIDI formatted message to call a preset dump of the current edit. (240 28 96 1 0 124 70 69 52 54 66 67 is the message itself)

I am working in Live Suite 11, max 8.6.1, and simply putting that decimal sequence into a message box and banging it to a Midiout has been sufficient to call preset dumps. It seems a little sketchy, sometimes two commands have to be issued for it to work, but it is essentially functional. My colleague is working in live 12, max 8.6.5 however (he just updated) and this same message formatting does not seem to call the current edit dump as expected // as it does in my environment. What gives?

Was there a change to the handling of this type of midi message in the recent update? Do I need to prepare the decimal string somehow now with a ctlout et al ? Is there a better approach I should consider to handling this type of sysex request globally ?

Thanks so much!

Source Audio's icon

Source Audio

10月 21 2024 | 7:39 午前

that is sysex dump message which MUST end with 247.

Your one is not valid because of missing eof sysex

240 28 96 1 0 124 70 69 52 54 66 67 ???

Maybe live 11 fixed that in background ?

Brian Bender's icon

Brian Bender

10月 21 2024 | 9:36 午後

That's got it! thanks so much.


I'd wondered the same but this was exactly as the message was printed in the manual, funny enough. You're probably right, perhaps the new 240 was enough to signify the end of the old message somehow? Hence needing to pop it twice, perhaps?

At any rate, we confirmed this solution to work on his end, too. thanks so much again!

Source Audio's icon

Source Audio

10月 22 2024 | 7:42 午前

It is possible explanation for having to send incomplete message twice.

sysex specs state that any status byte that gets received before sysex message gets

terminated with F7 should mark messsage as "done" and ABORTED.

that could be difference between live 11 and live 12.

they finally fixed one of many holes in the sock.