Why doesn't UNDO work for tempo changes?

[madFloyd]

Anyone know? I like to experiment with tempo changes but because undo doesn't work, I have to keep track of the values before I change anything.

 

[Trucky]

Undo for tempo changes work as expected for me.

Can you post the steps or provide a video link showing where it doesn't work for you so I can test on my system?

 

[madFloyd]

Thanks for looking into this, Trucky. I've experienced it enough times that I just assumed it wasn't supported. I should be able to repro it.

 

[madFloyd]

I think I might know why I'm confused.

So I'm about to use the TRIM function inside the tempo (you can't see the cursor in the screengrab) to raise this section from 114

to 133

If I immediately hit undo, it doesn't revert this. However, looking in the undo history I see:

So the tempo change IS in there, it's just followed by a series of 'Modify Chords' ... and I'm not sure why but I'm guessing there's a reason.

It seems in order to undo tempo changes, I need to use the History panel.....?

 

[reginaldStjohn]

Do you have audio files that are set to follow tempo? If so then when you change the tempo S1 has to stretch or compress those files. Maybe that is what is showing?

 

[SwitchBack]

... It seems in order to undo tempo changes, I need to use the History panel.....?

Depending on your song's content and settings one tempo change can trigger several actions. The History panel allows you to undo all those actions in one go rather than painstakingly undoing them one by one (if that's even possible with actions required after the initial one).

 

[madFloyd]

Yes, I understand that. And while the History panel is a great feature, one could argue that either the automated changes should be broadcasted to the user - or the undo should undo all of these. After all, the user did one action - that triggered the equivalent of a macro.

Anyway, I'm sure Presonus must have internally debated what to do in this situation and chose the route that exists now.