Ralf from Ableton and I worked on a little workaround for those like me want to send & receives midi messages over 16 midi channels.

I put a zip file here with all the files required to understand the concept.

Open the liveset.
There are 2 groups.

1/ from patch to midi channels
Deploy the 1st group named from patch to midi channels
in the first sub-track, there are a patch handling the send to the other patch.
the other tracks are routed to my UNO midi usb interface ; one track per midi channel.
in each track, a little patch handling the receive from the first patch described above.

et voilà.

all that you need to send to another midi device has to be send like that from any patch in your live set.

now, the reverse way...
Collapse the first group in order to save space..

2/ from midi channels to patch
Deploy the 2nd group named from midi channels to patch
in the first sub-track, there are a basic patch that make the proof of concept by printing notes and CC value received by itself. (you can click on the print object)
the other tracks are currently routed from All Inst, one channel per track but could be routed from ANY midi device. I selected All Inst in order to make the proof easier: fire clips inside these tracks, and see how the max window prints the result... it works!
each track are routed to the first sub-track named ReceiveFromMIDIChannels
et voilà (bis)


This little workaround is nice and useful !
I hope I had been clear enough!
If I had not, please post questions.
and send a kiss to Ralf !!

Ah cool. I thought you guys cooked up something more elegant. It works, I wont argue with that.
I've been looking to port my snapshot matrix patch to M4L, but all these MIDI racks just make it messy.
I'll stick with runtime for this. As the patch updates controllers and does it fast enough.
Thanks for sharing though. And thanks to Ralf for looking at this. It may come in handy for other purposes.

I completely agree and didnt test it with my real liveset.
btw, it works.

fmo, I'd and will do things differently I guess...
I'll probably code differently my events mapping for the protodeck to only use one midi channel! finally!

It's indeed only a workaround which gives us some time
to fix bugs for the release. Something more elegant will
be done after the release, at least I hope so.

Ralf

Ahh, and thank you to Julien for working it out!

Ralf

I just hope too

I'll look at this tonight if my Max is working? Still got the saveaschooser error but i imagine i need these patches for my APC40 template which i don't have the chopice of running it on one channel!

Cheers
D

We all do!
M4L is loads of fun and I'm very close to the control I always wanted.

If Ralf can figure out that little live.remote~ issue we have, I can finish my piece de resistance! Looks like I'm in the pocket for another round of beers.

I have yet to dig deeper into this grid controller surface stuff. But from what I can see with that CS step Sequencer example, you could actually remap specific buttons from specific modes.
No mucking about remapping midi messages of a device that reconfigures itself based on which preset its in.
No clue on how to do this yet, but the step sequencer is a proof of concept.

ahah!
you meant this post: viewtopic.php?p=1010402#p1010402 ?

No. Its a post I made earlier asking how to disconnect a live.remote. And where I found that there is no undo event when the remote is disconnected. Ralf will bring it to the table and see what can be done.

Alternatively, for my purposes it would also work to have live.object NOT create an undo history. As it seems fast enough for manual control. Not sure if there's a CPU increase on either objects.
Or even if its pointless to set values in remote with normal max integers.

it was the question of the last post in the thread I quoted: what is the benefits of live.remote use instead of live.object/set value use ?

Yeah. Its an unanswered question. But not the problem stopping me from finishing the patch.

ok
btw, I guess you answered with the undo handling or not.

Julien, the link you provided to your workaround isn't working, would you mind sharing another link? I'm hoping this will allow me to access the different channels offered by the Livid Code. I'd like to use the different banks of the Code to create up to 4 step sequencers, each bank sending midi data on its own channel.

Thanks,
Jeff