Ableton Forum

Publishing the Python source-scripts used by Live for its supported controllers would probably be enough to build your own map. Unfortunately these scripts are only bundled with Live in a compiled form.

Just replaced my original post with the following:

There is one simple solution to enable support for any controller or any software that sends MIDI: Make a MIDI implementation chart for all Live devices!
And not just 8 parameters, ALL of them.

There are 16 times 128 CC messages in the MIDI specification. That is more than enough to cover all the parameters on a device like Operator.

Select a device, control it from any MIDI controller - or more importantly - any combination of MIDI controllers without having to "MIDI Learn" a single parameter.

That is what I call AutoMap!

I hate when I learn parameters for a device and accidentally load a preset the wrong way, inadvertently trashing all of the midi learns.

I think that learnable permanent maps are the way to go. No charts, just learn per device and it's permanent until you reedit it.

The Automap idea was ok, but severely flawed in a way that hurt newbees and experts. Ableton was like "we know, but we don't have time to fix this now, we will fix it as soon as we can...."

I now only use Automap for the 8 current macros...