The problem comes when I don't know I've screwed up and I don't find it until I'm past the 32 levels of History.
Yesterday I somehow overwrote a whole section of multicam cutting. Redoing that cut was far more work than redoing what I'd have lost by moving back far enough in History (if the program would have let me move back far enough).
32 Undos just doesn't cut it. I can't believe this remains unchanged for CS6.
Nice to know. Thanks, Wil.
I'd like to ask everyone reading to submit a Feature Request on this to push it up in the rankings. Even if you don't need more than 32 yourself, having more than 32 won't hurt you, but it sure will help others.
https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
I can't agree more about incremental saving. I too have learned the hard way.
I date the filename, ending with a numerical stamp. Throughout the day, at key edit moments, I increment the stamp, thus...
GWQ-150512-6
At the start of the next day, before any edits are committed, I change the date and reset the stamp, thus...
GWQ-160512-1
(British date format, guys!)
I do need to resort to it quite often!
More than 32 undos...? What is this, iMovie Pro? Ah, shooternz already beat me to the "pro" dig, so I'll just pass.
I actually went and checked it out myself, was a bit surprised also. But it didn't even make it onto my "PPro CS6 Pros/Cons" list that I'm assembling, so that tells you the priority for me.
I probably will put in a feature request, because I know of at least 1 time in the last year I needed more (although I don't know if I needed 45 or 60 or 100). It was the dad-gum TITLER that did it to me, it adds a history point for every breath taken while editing a title, eats up the history pretty quickly.
it adds a history point for every breath taken while editing a title, eats up the history pretty quickly.
That's exactly how I lost my multicam edits the other day. I'd much rather redo the titles than redo the multicam cut, if only I could have gone back far enough to undo the mistake.
Same thing happens with a Nudge. Every frame is another Undo level.
It's cases like that where even incremental saving might not save your bacon. Unless you want to end up with several dozen project versions per day, which could add up to several hundred or even into the thousands over the life of any given project. And I definitely do NOT want that.
No...proper Undo levels is the solution here. 99 at a minimum. And with today's high memory rigs, I can even see allowing the user to set as many as 999.
North America
Europe, Middle East and Africa
Asia Pacific