Ableton 10 glitches and bugs

[gkmachine]

Hi,
I think we need a sticky for all the glitches and bugs with Live 10. I've contacted tech support but not had any response yet. For me, I have experienced the following:

Not saving edit history: I currently have a session on the go that the last edit that I can undo is when I opened it last week. This is a complete nightmare as I have a deadline to reach by this Thursday and need a track finished....but when I open it it doesn't sound like what we last saved. What this means is that, in my case, I can do 100 edits but when I go to File - Undo, the last thing is always "Undo change bpm" (I changed bpm almost a week ago)

Crackle and glitches: if a track is playing in arrangement view even if I move the cursor from one clip to another it crackles and pauses for a microsecond, sometimes it does it without having to do anything.

Re-enable automation is permanently coloured red: this implies that automation has been changed and to revert to the session's settings you need to click on it to over-ride any recent changed. However, when I do this it immediately jumps back to being red. This is impossible!!!

I have tried saving sessions as a new session but all these glitches cary over to amy new sessions too. I don't have time to convert all these channels to stems and open a completely fresh session with them! It's pretty infuriating.

[Stromkraft]

Not saving edit history:…
….but when I open it it doesn't sound like what we last saved. What this means is that, in my case, I can do 100 edits but when I go to File - Undo, the last thing is always "Undo change bpm" (I changed bpm almost a week ago)

The emboldened statements seem unrelated to me. What does "doesn't sound like" even mean in this case?

Crackle and glitches: if a track is playing in arrangement view even if I move the cursor from one clip to another it crackles and pauses for a microsecond, sometimes it does it without having to do anything.

What happens if you increase your audio buffer?

Re-enable automation is permanently coloured red: this implies that automation has been changed and to revert to the session's settings you need to click on it to over-ride any recent changed. However, when I do this it immediately jumps back to being red. This is impossible!!!

Do you have any Melda plug-ins or Max For Live devices in the set?

I have tried saving sessions as a new session but all these glitches cary over to amy new sessions too. I don't have time to convert all these channels to stems and open a completely fresh session with them! It's pretty infuriating.

This is to be expected. One way to look for culprits is to save as a new set and delete tracks until the issues disappears, undo and then delete devices. I've had to do that multiple times and have got rid of the involved devices/plug-ins.

[gkmachine]

Hey, thanks for the response.

Right, forget about "doesn't sound like" (this could be subjective).... the main thing is the edit history......the last thing I can Undo is the change I made to bpm automation (slowing the track down at the end) I made this change during the 4th last time that I had the session open and have made many changes since.

Tried increasing audio buffer.....no improvement

Yes, M4L space echo. Are there known issues?

[re:dream]

Yes, M4L space echo. Are there known issues?

viewtopic.php?f=1&t=230396

[Stromkraft]

…the main thing is the edit history......the last thing I can Undo is the change I made to bpm automation (slowing the track down at the end) I made this change during the 4th last time that I had the session open and have made many changes since.

That's odd, yes. But is this only in this song or is it stuck at that in every song? Commonly Max For Live devices that spew data into the undo action list is behind the undo function breaking. Could you make a set without any MFL devices and see if that helps?

[Alexander Dorodeiko]

I have the same annoying issue with "undo change bpm". I actually can undo to a previous state, but need to click undo 20-30 times (all the times I see "undo change bpm".
Indeed, I use Max devices in the project, could be because of them.
Also, I have changing tempo in the project, but the undo bugs happen even when I am working on the parts with stable tempo.
Suuuuuuper annoying bug

[nemoy]

That same undo history spamming occurs also, when you map one Midi controller Knob to multiple parameters in live.
Turning that knob then results in loads and loads of tiny increments of the two or more mapped parameters being written into the undo history.
very, very super annoying.