Why is undo sometimes too slow?
I edit podcasts, which means I'm working with lengthy wavs or sometimes mp3s of people talking on separate tracks, and I make hundreds (thousands?) of little edits throughout, tweaking timing, cutting out hesitations etc, usually with ripple edit on.
Sometimes, rarely, on certain projects, pressing undo after an action that triggered the ripple edit will take around 2 seconds to respond - which doesn't sound like much until you're doing it. I've developed an automatic response to flinch as I hit undo on the current project, because I know I'm about to take light damage.
Now, until recently, I thought this happened when I had imported a problematic file into the project. It's not unusual, for instance, for me to use a video in a podcast timeline, if YouTube was the best source for the audio of some old clip I need to use. Makes sense that a video would slow down the response time if it's a funny format.
But the current job is just wav files, which I've been sent in a batch. Why would they cause the undo slowdown problem?
This is on windows, a win10 desktop with a great CPU that means everything is usually very zippy, and a win11 laptop with a worse but tolerable one. Same effect on both. I've encountered this in enough different projects now that I wonder if it's a known issue.