mauricenorris

I can’t seem to get the sysexin object to respond in MaxForLive.

I’m just sending the sysexin object to a bang, then testing it by performing a program dump on my Minilogue.

This works fine in Max 8 standalone, doing a program dump from the Minilogue results in a bang. However, when doing exactly the same in M4L, nothing happens.

I have the track in Ableton set to the correct MIDI device with Monitor set to ‘In’. Note and CC are being picked up just fine, just not any sysex messages.

I’m also having the same trouble with the MIDI Filter M4L device. All MIDI data is being picked up, just no sysex when I do a program dump from the Minilogue.

I’m sure I must be just missing something really simple. Could anyone please suggest where I may be going wrong?

I can’t seem to get the sysexin object to respond in MaxForLive. 

This works fine in Max 8 standalone, doing a program dump from the Minilogue results in a bang. However, when doing exactly the same in M4L, nothing happens. 

I can’t seem to get the sysexin object to respond in MaxForLive. 
I’m just sending the sysexin object to a bang, then testing it by performi

sysexin-object-working-in-max-but-not-in-maxforlive

I got it working the end but just in case anyone else ever has the same problem...

I was connecting my Minilogue through the IN/OUT MIDI ports to a USB MIDI interface, and then to my Mac. I changed to a direct USB connection between Minilogue and Mac and the sysex is coming through just fine.

Not sure why this is the case (as sysex was coming through perfectly fine in Max Standalone), but changing to a direct USB connection appears to have solved it. 

I'd still greatly appreciate it though if anyone could explain why... 

I got it working the end but just in case anyone else ever has the same problem...

I was connecting my Minilogue through the IN/OUT MIDI ports to a USB MIDI interface, and then to my Mac. I changed to a direct USB connection between Minilogue and Mac and the sysex is coming through just fine.

Not sure why this is the case (as sysex was coming through perfectly fine in Max Standalone), but changing to a direct USB connection appears to have solved it. 

I'd still greatly appreciate it though if anyone could explain why... 

:)

Sysexin object working in Max but not in MaxForLive