MPE Input for M4L Device (Roli Rise)

OK it's now clear that a M4L device can't do MIDI routing in Max. I've decided to stick with Live & M4L, especially because it's widely expected that they add MPE support this year with the release of Live 10. So: using Live's limited MIDI system with M4L devices:

It seems the only method to getting that data from each note is to make a 10+ MIDI channels (as many voices as I want to be able to use simultaneously), and put in each of them a M4L Midi Send device using the [send] object, each which routes note input info to corresponding [receive] objects in my synth. I could then have my [poly~] voices each individually handle things like note pressure, y-axis movement, etc.

I'm wondering if anyone has an example patch of this, or advice? Thanks in advance!

Alright I've built a little M4L midi routing device that gets 10 voices of MPE data into my synth. Screenshot attached--it works fine. If anyone has any experience working with MPE synths in Max or M4L, I'd love to hear about it!

Here is how the routing in the above screenshot looks like inside my patch. Does anyone know if multiple inputs in this way will confuse a [mpeparse}?

Perhaps not coincidentally, since I started using this method, and using [polymidiin], my synth can only play 1 voice at a time :( A tutorial demonstrating these new MPE objects would be much appreciated.

I think the send/receive objects are not needed at all since you could use the routing of a *multi-timbral instrument* as explained in the Live manual, chapter 14.6.2 'Making Use of Internal Routing'.

Hey Broc--thanks for the suggestion. I read the manual, but my set-up though is all about live-sampling, it's a granular synth that can record a new sampling buffer on the fly.

For that reason, I put my sampler-synth in a audio track and route the MIDI performance data from MIDI track. I could alternatively put it in a MIDI channel and record into the buffer~ in another track, but I feel sharing buffer~ data between M4L devices is more processor intensive than simply sending MIDI data between them (though this is a question of the architecture of M4L).

Can anyone speak to whether I can send in 8 streams of MIDI data into an [mpeparse] without losing speed/efficiency of processing?

I've come to the conclusion, after dozens of hours of tests and patch edits, that there's probably something fundamentally wrong with the above M4L routing. Sending MPE data through separate LIVE channels using the [send] object in each, to be received by a corresponding number of [receive] objects in the M4L audio object DOES NOT seem to work. The patch that receives the MPE midi data becomes monophonic.

It seems like the result is this: however many voices the poly~ is supposed to be able to play (e.g. 8), it ends up playing all of those voices (e.g. 8) on the latest note to be hit.

I would love to see some tests done by someone else, to see if they could successfully route mult-channel MPE data in Live to a Max synth.

Actually, it's probably not the problem of the routing, it's something with M4L and mpeevent messages. If I run all 16 of my MPE channels into my 1 M4L device, they work as long as I use [mpeparse] to only send my poly~ object note-on and note-off messages.

If I use the last outlet of that [mpeparse] to send poly~ mpeevent data, then suddenly is doesn't work in M4L, though the identical set-up will work perfectly in Max.

If you are sending/merging multiple streams of raw MIDI bytes, the receiver may not recognize correctly the bytes that belong together as messages. So I would pack the bytes on the senders into MIDI messages (notes, CCs) and unpack on the receiver side.

Hey Broc--thanks for the reply. Here's the thing: if I send my poly~ just ONE note on ONE mpe channel using a send and receive object, then it still activates all 16 of my poly~ voices. And this is only if that data is sent to poly~ in mpeevent format--if poly~ receives the data in midinote format it works fine with all 16 send/receive objects.

Further reason for thinking this is a M4L bug: the PGS1 MPE device doesn't doesn't play polyphonically in M4L. It's an .amxd file, and works fine in Max, but no matter how you try routing the MIDI in Live--using the *multi-timbral method* outlined in the Live manual and on the ROLI website, or by using [send] and [receive] routing... nothing works! It has the same issue in M4L--every voice available gets used on the first note that is played.