Ableton Forum

Tarekith wrote:Did you save the set before you tried to use Undo?

Sometimes yes sometimes no

I have the same problem

downloaded Max4Live last week and now my Command Z doesnt work

makes ableton 10x harder to use

can anyone help
?

I had the same problem but noticed it only occurred if I changed parameters whilst the track was playing.

I have been using Robert Henke's awesome LFO 2.0 and it turns out that the cause of the apparent inability to undo changes was that I was modulating the GUI element.

Switching to the Engine modulation method fixed the issue.

I'm not sure if it will work for you, but to me shortcut ctr+shift changes letters "z" with "y". Maybe you pressed it accidentally. May only work for certain system keyboard settings though, not sure.

The same here, with all versions, random and very often

If you are using Max For Live, then typically Max devices are spewing out steps you're not aware of, that makes it seem as if undo isn't working. For when you're using those devices you will need to hammer undo many times unfortunately.

Sometimes I feel an undo history list would be nice to have.

ok,I was going crazy until I do a research and found this old threat.
The undo problem is still present in the 10.0.2, without any Max device.
Automation filling the undo list is weird...
I hit the stop button in the middle of the track, boum, undo list populate with "output trim" => I have dozens of this entry, almost impossible to undo anything.

John

[quote="john "leborgne""]
The undo problem is still present in the 10.0.2, without any Max device.
Automation filling the undo list is weird...[/quote]

If you did automation changes then that is naturally in the undo list. Why does this surprise you? If there are multiple steps unknown to you then what did you do to initiate them?

I think the undo problem of this discussion is not at all present in Live 10.0.2, except for Max For Live devices that need to be updated to report steps to the undo history differently. I've never seen this issue — spewing of multiple steps that the user did in one step — in any version of Live in the last seven years that did not involve MFL. I've seen other problems though.

If you have a specific problem in a set, which certainly is possible — my suggestion is that this is not typical nor widely present in every installation of Live 10, which you imply — you should report that to Ableton. They will be able to help you identify the cause, perhaps devise a workaround, and in the process you might assist to a bug getting fixed, either in Live or in a plug-in (a likely cause).

[translation protocol]

Stromkraft wrote:[quote="john "leborgne""]
The undo problem is still present in the 10.0.2, without any Max device.
Automation filling the undo list is weird...

If you did automation changes then that is naturally in the undo list. Why does this surprise you? If there are multiple steps unknown to you then what did you do to initiate them?

I think the undo problem of this discussion is not at all present in Live 10.0.2, except for Max For Live devices that need to be updated to report steps to the undo history differently. I've never seen this issue — spewing of multiple steps that the user did in one step — in any version of Live in the last seven years that did not involve MFL. I've seen other problems though.

If you have a specific problem in a set, which certainly is possible — my suggestion is that this is not typical nor widely present in every installation of Live 10, which you imply — you should report that to Ableton. They will be able to help you identify the cause, perhaps devise a workaround, and in the process you might assist to a bug getting fixed, either in Live or in a plug-in (a likely cause).[/quote]

the condescending parts and useless drivel are highlighted in red.

if Stromkraft was just trying to be helpful he could have wrote:If you have a specific problem in a set, which certainly is possible — my suggestion is that this is not typical nor widely present in every installation of Live 10, which you imply — you should report that to Ableton. They will be able to help you identify the cause, perhaps devise a workaround, and in the process you might assist to a bug getting fixed, either in Live or in a plug-in (a likely cause).

[/translation protocol]

H20nly wrote:

if Stromkraft was just trying to be helpful he could have wrote:If you have a specific problem in a set, which certainly is possible — my suggestion is that this is not typical nor widely present in every installation of Live 10, which you imply — you should report that to Ableton. They will be able to help you identify the cause, perhaps devise a workaround, and in the process you might assist to a bug getting fixed, either in Live or in a plug-in (a likely cause).

Actually H20nly has a good point. Taken!

Control Z & other keyboard parameter short cuts tend to discontinue working when your Ableton sessions latency (in your preferences - audio tab) is on a high buffer size eg; 1024 samples or above & your in/out sample rate (also in preferences - audio tab) is set to the lowest rate ; 44100.
Set your in/out sample rate to 48000 & shift your buffer size between 512 & 1024 samples. Personally i never go above 48000 & stick to 512 samples, but may need to shift to 1024 depending on how large my project becomes.
Ø

ody-z wrote: ↑

Mon Dec 02, 2019 12:27 pm

Control Z & other keyboard parameter short cuts tend to discontinue working when your Ableton sessions latency (in your preferences - audio tab) is on a high buffer size eg; 1024 samples or above & your in/out sample rate (also in preferences - audio tab) is set to the lowest rate ; 44100.
Set your in/out sample rate to 48000 & shift your buffer size between 512 & 1024 samples. Personally i never go above 48000 & stick to 512 samples, but may need to shift to 1024 depending on how large my project becomes.
Ø

Is this something you can observe consistently?

[jur] wrote: ↑

Mon Dec 02, 2019 2:26 pm

ody-z wrote: ↑

Mon Dec 02, 2019 12:27 pm

Control Z & other keyboard parameter short cuts tend to discontinue working when your Ableton sessions latency (in your preferences - audio tab) is on a high buffer size eg; 1024 samples or above & your in/out sample rate (also in preferences - audio tab) is set to the lowest rate ; 44100.
Set your in/out sample rate to 48000 & shift your buffer size between 512 & 1024 samples. Personally i never go above 48000 & stick to 512 samples, but may need to shift to 1024 depending on how large my project becomes.
Ø

Is this something you can observe consistently?

To be completely honest, this was something that i recently come across. As soon as i had followed the directions i gave in my first post, everything started working again. i can not think of any other reasons why this may be occuring.
Ø

Do you have any M4L device in your set?
If so, which one?

2020 here, Live 10, still have that problem. Although I did find a max for live device that was literally inactive and doing nothing. Deleting that off the empty track fixed the problem for a few seconds, and now it's back randomly not undoing (not moving clips back in place!)

Edit: I removed izotope RX and now works perfectly.