Serious problem with saved state of parameters

[[jur]]

When this happens:
- delete e.g Convolution Reverb,
- and then undo the delete action...
Does CR come back with the expected values or the wrong ones?

[chapelier fou]

I’ll try this but it happens only when I open the set. So not much hope.

[[jur]]

Yep, let me know please.

[jbone1313]

I ran into a similar issue today, and I think I recall seeing it in the past. That is, when I reopened my set, the mappings on Expression Control were showing as though they were not mapped. When I inspected the target device dial, it was showing it as mapped. When I went back to Expression Control, it was still showing as not mapped.

Then, I reloaded the set. I changed nothing before reloading the set.

After reloading, the devices behaved normally.

Speculation time:

Perhaps something is going wrong with the loading or instantiation of M4L. Like, the data is saved, but it is not being loaded correctly. Perhaps certain conditions happen intermittently, perhaps more on some users' machines, which cause hiccups in the loading or instantiation of M4L.

Win 10
Intel 9900k
32GB RAM
M.2
Live 11 beta

[jbone1313]

Adding some more data:

I have had this happen more. It has happened after I caused a MIDI feedback loop.

In some cases, reloading the set resolved the issue. In other cases, restarting Live resolved the issue.

In any case, the state was saved. It just was not recalled.

Users interpret the behavior as a lack of saving/persistence, but again, I think this could have something to do with how Live loads M4L and or these types of devices.

What conditions would cause Live to not load these devices correctly? Probably a question for the Ableton team.

[tmoore]

I've had this happen a few times. I wrote to Ableton support and they suggested I follow these instructions to reset Max for Live: https://help.ableton.com/hc/en-us/artic ... x-for-Live

It fixes it every time, and all my saved sets behave properly. I never figured out exactly what triggers the problem, but I think it might have to do with multiple sets stored in the same project folder. I'm hoping the problem will go away with Live 11, but in the meantime, maybe this will help someone.

[chapelier fou]

Hope at last !
I'll try this asap, thanks a lot !!!!
Can you confirm that you encounter the exact same situation where previous sets, that you didn't touch, also load with wrong parameter values ?

[chapelier fou]

Well. Didn't work. Opened a fucked up set, still fucked up.

[tmoore]

Bummer. Sorry to hear it. The symptom I saw was that saved sets, including older backups, loaded with all of the Max for Live devices reset to their default parameters. After I reset Max for Live, those projects opened with the values I set.