Drew Boles

I'm having a strange problem which I cannot seem to solve.

I am a building a large MIDI interface instrument in which I am using various MIDI channels to send my data. Because I am using different channels, it is important to the patch that the proper channel is identified so that I do not end up with mixed controls.

I have created a Max MIDI Effect on a MIDI track (set to the appropriate controller, All Channels selected). In the patch, I have midiin connected to midiparse. Unfortunately, midiparse is always reading the incoming signal as transmitting on channel 1. ALWAYS. The track's MIDI indicates that Ableton is reading the correct channel. Then, if I open MAX/MSP as a standalone app and connect my controller via midiin there, MAX then reads the channel properly as well.

It seems that there is something in the translation from the Ableton MIDI track into the midiin object within a Max for Live patch that is getting screwed up. Has anybody else seen this? Any remedies?

Hi everybody -
I'm having a strange problem which I cannot seem to solve.
I am a building a large MIDI interface instrument in which I am using various MIDI channels to send my data. Because I am using different channels, it is important to the patch that the proper channel is identified so that I do not end up with mixed controls.
I have created a Max MIDI Effect on a MIDI track (set to the appropriate controller, All Channels selected). In the patch, I have midiin connected to midiparse. Unfortunately, midiparse is always reading the incoming signal as transmitting on channel 1. ALWAYS. The track's MIDI indicates that Ableton is reading the correct channel. Then, if I open MAX/MSP as a standalone app and connect my controller via midiin there, MAX then reads the channel properly as well.
It seems that there is something in the translation from the Ableton MIDI track into the midiin object within a Max for Live patch that is getting screwed up. Has anybody else seen this? Any remedies?
Thank you!

channel-not-reading-properly-in-a-m4l-midiparse-object

It's a general limitation of Live that MIDI channels are not separated internally.

Can anyone elaborate on this old post from Broc? Does midiparse in Live truly read only a value of "1" for all messages with no workaround? Sorry to post in an old topic but I'm wondering if anything has changed in the 9 years since this topic was started.

Screen Shot 2021-11-22 at 14.08.08.png

Screen Shot 2021-11-22 at 14.15.31.png

okay, yeah I'm practically totally new to all of this so I'm glad you confirmed M4L's limitation has not changed since then. While it's unfortunate that Live can't handle this natively, the external object imp.midiin is great and does exactly what i need it to do

yep, still as dumb as in 2012
imp.midi objects could help with that

channel not reading properly in a M4L midiparse object