save MIDI-Mapping in devices and/or tracks

[BjornE]

Saving midi mappings other than for a project should really be implemented. Big like button for this one!

[dr_kant]

Please +100 for this!

It's a pain to have to remap everytime you import a custom device.
And also an advanced midi mapable undo with custom options, but that's not the topic..

[Horselover Fat]

I just came across a situation where I needed this and to my surprise this is not implemented. Having to remap all MIDI CCs after loading a device renders the whole thing useless. I very much support this feature request.

[Koon Vega]

+100000000 for this one!! I need it!

[oOvac]

Yessss we need this!!

[chris harbin]

Again, dittos.

Key commands should be included in this IMO.

[Irrlicht]

agreed. Many plugins default to very unintuitive or incomplete midi-mappings and while mapping them is easy, it's still a thing we should be able to save and load into any session. There needs to be an option to save midi mappings both for ableton devices and third party plugins.

[rlarosse]

Yes, please.

[Mangrove]

just found this... But I still have issues. Does somebody know a updated version ?

http://jgarcia.hungry.jp/project/manual-cc-mapper/

For any one having the same question.
This device is by far the easiest to use.
Just add this device to 1 midi track and change the input to the correct device and midi channel.

It's awesome!

[agustinvolpe]

This feature is a no brainer, being able to save the MIDI mappings on devices would speed up workflows so much.
Must implement this Ableton!

[marlasky]

Just bumped into this while trying to make user templates for some VSTs using Novation LaunchControl XL. Creating the user templates with the right CC values is easy enough, but they only work once I midi map the parameters to the knobs I have assigned in the template, and then I cannot save it per plugin.
It would be an awesome way to expand on the params available in my Push1, as the LaunchControl XL has many more knobs, buttons and sliders.