Ciaran

Ableton 11 now supports MPE, (hooray) but I don't care for the Roli. What I want is MPE support between Max4Live devices and Ableton instruments.

So Ableton now supports MPE... but does Max4Live? When you plug MPE into a new M4L device, the [midin] object still siphons all this data into a single voice (-1 or 1).

What I want to know is who is to blame here? Does Ableton have a wrapper around the M4L devices that causes this? Or is M4L still yet to catch up to some extent? I'm hoping for the latter, as I doubt Ableton would fix an issue like this anytime soon.

The picture shows how MPE voice is seen locally (within the first M4L patch) vs how it is seen in the following device. So this problem occurs between the two devices, or inside of either the [midiin] or [midiout] objects.

I'm aware of the workarounds that involve using MIDI busses, communicating with Ableton from Max MSP instead of M4L etc... But I think we can do better than that!!

I'm hoping some of you can shed some light on this one.

Screenshot 2021-03-19 at 19.31.26.png

So Ableton now supports MPE... but does Max4Live? When you plug MPE into a new M4L device, the [midin] object still siphons all this data into a single voice (-1 or 1).

What I want to know is who is to blame here? Does Ableton have a wrapper around the M4L devices that causes this? Or is M4L still yet to catch up to some extent? I'm hoping for the latter, as I doubt Ableton would fix an issue like this anytime soon.

Hey everyone,
Ableton 11 now supports MPE, (hooray) but I don't care for the Roli. What I want is MPE support between Max4Live devices and A

mpe-m4l-and-ableton-11-who's-to-blame!

 about Live 11 and M4L for some examples. To enable MPE on M4L devices, it says:

Hi there! You can check out a recent set of articles about Live 11 and M4L for some examples. To enable MPE on M4L devices, it says:

In the new Max for Live category in the Patcher Inspector you can use an attribute (@is_mpe) to specify whether your MIDI Effect or Instrument is an MPE device. Setting the @is_mpe attribute enables your device to modify and generate MPE data.

"When you plug MPE into a new M4L device, the [midin] object still siphons all this data into a single voice (-1 or 1). "

there is probably a misconception at one point. midiin outputs everything you tell it to, including sysex.

if you dont want to fiddle with the data on your own, the [mpeparse] helpfile should tell how to do it with 3 clicks.

"When you plug MPE into a new M4L device, the [midin] object still siphons all this data into a single voice (-1 or 1). "

there is probably a misconception at one point. midiin outputs everything you tell it to, including sysex.

if you dont want to fiddle with the data on your own, the [mpeparse] helpfile should tell how to do it with 3 clicks.


Sounds like there's people to celebrate (rather than blame)

Isabel, thank you so much this looks very promising!

Roman, I see what you're saying but as you can see from the pictures this is very real in practice...

Audiomatt, just a bit of tongue and cheek I celebrate all my fellow humans day in and out.

MPE, M4L and Ableton 11. Who's to blame!?