Mapping issue - mappings go back to previous assignment when cleared and saved in live set
This started happening with Max 8.3 : if i assign a mapping to a M4l device, save the set, then open it again, delete that mapping, and save the set again, the mapping reverts to the first saved assignment next time I load it . If I map it to something else, it saves that change. Tried it with many map buttons, as bpatcher, embedded bpatchers, etc. Live 11.1.6. Also tried to set map Parameter to " Automated and stored" Very frustrating, anybody have any idea how to fix that?
Does it happen with devices you aren’t developing?
If you are making any changes to the Parameters in your M4L device that might be mucking with the Parameter ids contained in the device (which is what the Live set uses for setting up MIDI mapping assignments).
and to be clear, I’m understanding you saying Mapping to mean Live‘a MIDI or Key Mapping, not like the “Map” functionality for assigning parameter takeover from an M4L device Via live.remote~
Hey Tyler thanks for the reply .
So yes, I mean the latter map function, and yes it happens with devices I'm not developing , say "Envelope" that ships with Ableton ( let's say i set it to control the pan of a track or something, then clear the mapping with the little x then save the set , it'll come back up set to pan when i re-load the set ) . I have been using whatever the map buttons that are in those devices ( map button. maxpat, or multi map.maxpat ) as bpatchers in a lot of the devices i built myself, and it's chaos right now.
Check this out: just to be able to keep working/ performing, I started using this workaround : If I am trying to get rid of a mapping in a device, ( a lot of them have like 5-8 map buttons that control many things ) without having to edit the device and take out the unused map button, (and having to re-assign the old mappings again as I lose them when I edit) , I assign it to something in a dummy track then delete the track and that worked for a while but now I see very weird assigments pop up- I assume the IDs are getting all messed up and what used to be an assigment in the dummy track is now something else.... Should I post a patch or a video or something?
Please report this to Ableton Tech Support.
Ok I talked to Ableton - if anybody wants to read up on it - https://help.ableton.com/hc/en-us/requests/2676574?page=1
The gist of it is that I was using the map button patcher from their old devices ( blue design ) and the newer ones ( black/orange ) do not have the problem descibed. Not exactly sure why the blue one doesnt update when saved.