Ableton Forum

None of my mapped LFO's are saving with presets. Anyone having this issue? Is this a bug? i could have sworn this was possible in earlier iterations of Live.

if this isnt a bug why would this not be possible? Its amazing making clusters of modulation and saving it with a preset , but to recall that preset and remap everything is a huge pain and timesuck

Just to be sure, you mean racks containing an lfo ?

Are you saving them in racks? With AU plugins?

same as expression control viewtopic.php?f=35&t=246519

yes- apologies. saving LFO's with racks. I am very certain that this was once possible before.

Yep, this is an issue, especially with AU plugins afaik.
To everyone who encounter this: don't forget to report to Support, we need this to be on top of the priority list

just submitted it

Damn, Ableton, i wish I could trust your devices.
This is the major issue with M4L. Problems with lost mappings/parameter values upon saving. Don’t get me wrong, I use M4L all the time, but I wish I could rely on it more. In a way, after more the 10 years of M4L, to me, it’s a fail (look at Bitwig and the modulators…).

chapelier fou wrote: ↑

Wed Jan 25, 2023 6:49 am

after more the 10 years of M4L, to me, it’s a fail (look at Bitwig and the modulators…).

Yea it's a shame they're in this situation, seemingly painted themselves into a corner. Modulators should've been native from the very start but Ableton are too far along with Max now – If they went native, they'd be admitting Max devices are unreliable.

14 years since Max was integrated into Live, 6 years since Ableton acquired Cycling74, and we're still seeing these failings

siliconarc wrote: ↑

Wed Jan 25, 2023 9:27 am

14 years since Max was integrated into Live, 6 years since Ableton acquired Cycling74, and we're still seeing these failings

Damn, 14 years. I remember the excitement so clearly. I still believe in the concept, but had some bad experiences during these years. Convolution Reverb losing its params, for instance ('solved' with Hybrid Reverb which, in my case, is a great replacement).

May be related to the fact that M4L doesn't work when the audio engine if off.

People that use bluetooth, USB mics or multiple interfaces may have more problems, since they are turning the audio engine on and off all the time.

it happens in any scenario with any audio interface

The new update does not fix this issue. Seriously? How are we supposed to use this wealth of modulation possibility in Live/M4L if our racks are not going to stay mapped to the correct parameters

Yeah, the maintenance of M4L devices is a JOKE. Please Ableton, can we ask for some seriousness ?

Would you be able to give me the set as a file or provide a set of reproducible steps? I would love to see this fixed, but I need to be able to recreate the problem in its entirety.