Device Details

Thank you! Looking forward to setting this up to control my East West libraries :)

Hi! Really great tool! Can you please add bank change functionalty. And may be some sort of NRPN.

Excellent with Emu e6400 Ultra nice one

Labels don't show up after restarting the project/drag'n'drop from pre-saved configuration (for example, from User Library) or after loading a preset. If I copy my labeled device to another track of the same project, they won't show up either.
Ableton 10.3.1

^ 10.1.3 of course. And thank you for the device, it helps a lot, but it's really puzzling to remember all the parameters without labels.

v1.1 update

The main 8 labels on the device should now be stored with the presets/pgm save/recall.


Working on getting the EXPAND labels working the same next

v1.2 update

Labels and settings now properly save across expand and alter sections.
Removed bank read/write as it's sort of redundant with Live's max device presets.

Hi, at first, thanks for absolutely great MAX device! I am using latest version (1.2) running under Live 11, but there are no save/load buttons for Presets section so presets cannot be used. Could you please check? Thanks!

Same problem with Live 11 as AbSynth, no save/load buttons... presets not recalling properly...any update?

Hi, this is a great device.
I have an issue with it though: controls in the EXPAND window do not emit any MIDI data. I had to load 6 instances of the plugin instead of 2 to achieve what I wanted.
I'm using Live 10.1.41.

Cheers !

Hey all, apologies for the delays in addressing some of the feedback.

EXPAND is now working again and I've fixed an issue reported about MIDI flooding. I've also removed the preset storage, so instead just save your setup as a device preset in Live. It will be much more reliable this way :)

cool device but I'm having an issue with automation recorede on non-armed tracks...
I've assigned my midi CC 1 to modulation wheel of my kontakt instruments, which control dynamics.

But when I record it on an armed track it overwrites the automation of the other instruments as well, even tough they are not armed...
Is there a fix or a workaround for that problem? Thanks !

Thanks! It work perfectly with Emu X Treme Lead :)

Hey! I absolutely love this, except I'm having one odd issue whereby for some reason no matter what channels I have the track set to, I seem to be getting CC message sent to another synth - so I have a Moog on channel 5, and a pedal on channel 11, but no matter what I try, I seem to be controlling the synth with the CC from the track that's supposed to only work on 11. I've tried a couple of other CC M4L devices and it doesn't do this, but yours is by far in a way the most elegant and capable solution.

Would love to know if you've got a solution for this or if it's a user error ;D

Ah I've just noticed that it looks like it's the Expand section that might be causing this which I can see you've already tried to fix (I'm using 1.3.3)

Thanks for these devices. Using them to test the ISE-NIN Firmware update. Insane!

Hello and thanks for this wonderful plugin.

I have a little problem tho, in the automation lanes, the parameters appears as Value X instead of the renamed parameter, like a macro pot would, I guess I can encapsulate this in an effect rack but this seem like an extra unnecessary step, do you think there could be a way to rename the parameter with its label so in the arrangement view automations, it's visible instead of Value 1 2 3 4 etc ?

Also I can confirm that the bug reported by Okubi is still happening on my end with the expand section in 1.3.3. It looks like any CC entered in the expan section will be broadcast the cc in all channels, no matter if they're routed to a specific channel or not. This creating absolute havoc in my live session.

I was so eager to have such a simple plugin that I replaced a dozen of devices for it, but now I'm kinda stuck

More information about the problem, it seems that as long as the cc number has been assigned to some other instance of CC mapper expand section, it's going to trigger them all as one

Sorry I can't edit my comment so I'll post another one:
It's even worse than that, any expand cc is being broadcasted to the output of all CCmaper instances