Ableton Forum

Yep, just that:

right click on any plug/device/etc...
and find an option that says "store preset with midi mappings"

some controllers I use for exactly the same things all the time... but I don't want to have them all loaded in my default template... and I don't want to have to rebuild/remap them each time either.


[/b]

That could be handy, yes.

I like it

thank you.

maybe the saving of midi assignments hasn't been implemented yet because of the complexities?

or maybe because it makes it far too easy to make a mess, particularly for newbies.

I think having the option to deliberately save assignments, especially to presets would avoid the mess, but keep the option open to those who want it.

yeah

i'd be interested to hear how you would want the potential problems to be handled

well... I think this would address the problems that are incurred by importing anything pre-mapped.

if you could already import pre-mapped material then you could easily end up with a jumble of things mapped to the same cc's, etc

by this method you already know that you are importing a preset that is pre-mapped - because you saved it that way. A simple naming protocol or symbol would suffice - as with the current system of displaying .adv's and .adg's

note that this feature request doesn't extend to importing pre-mapped tracks/clips and other Live Set components... cos I have no solutions as to how to avoid complications there.

would be glad to hear any other problems/solutions you can think of longjohns

bland_handl wrote: if you could already import pre-mapped material then you could easily end up with a jumble of things mapped to the same cc's, etc

by this method you already know that you are importing a preset that is pre-mapped - because you saved it that way. A simple naming protocol or symbol would suffice - as with the current system of displaying .adv's and .adg's

Saving to a special folder (midi-mapped presets), then manually opening the mapping browser and check for conflicts.
I don't think this is something that Live should do by itself, because it has no way of knowing if your mapping of 2 things for the same cc is a conflict or intended.
If the user wants to do things this way, he gets the otion, but he also has to think things through and work out sensible mappings for his needs.

i like certain things about this concept, but it just seems problematic to be importing mappings into a set which can have conflicting mappings already in it

i find that automapping a racked plugin is a good way to go. so with two improvements there could be another option:

1) more macros

2) ability to split a single controller preset into several virtual instant mapping controllers. so for example a BCR could have four sets of encoders, operating as distinct controllers

so if you want certain controls to operate a reverb every time you drag it in, you rack the reverb with your macro assignments, and when loaded into a set you'd lock it to that virtual controller.

that gives you more options. you can have "saved mappings" which are locked to a surface, or you can have them operate only when the device is selected

i think they'd be up for grabs for manual assignment too - can't check at the moment how that works.. I imagine an assigned control which is part of an instant mapping controller would just get booted out of the instant mapping scheme

?

longjohns wrote: 1) more macros

Yes, please. And with buttons too.