A basic USEFUL upgrade request for Vegas

craftech wrote on 3/20/2006, 8:34 AM
Aside from those requests that users have harped upon for years like fixing the credit roll generator and the titler I see no reason for not being to implement a basic editing function that would save hours and hours of re-doing work already done.

If the Vegas editor is non-destructive, why can't the history in an ongoing project be saved when you close and that same history be used to jump to any point in the editing process to "fix" something then go forward to where you left off without having to redo what in many cases took hours. Right now I am working with 13 tracks.

John

Comments

GenJerDan wrote on 3/21/2006, 8:49 AM
Vegas may be non-destructive, but it makes no assumptions about what *you* do when it isn't looking.

An Undo History can keep track of changes...but if the user makes a change outside the program (deleting a file, for instance), the process will blow up.
craftech wrote on 3/21/2006, 8:53 AM
Vegas may be non-destructive, but it makes no assumptions about what *you* do when it isn't looking.

An Undo History can keep track of changes...but if the user makes a change outside the program (deleting a file, for instance), the process will blow up.
============
I am not talking about deleting files or anything else "outside the program". I am talking about unsplitting or moving edit points or deleting something on a track or event etc

John
dibbkd wrote on 3/21/2006, 3:07 PM
That would be a pretty nice feature for Vegas, or any other program for that matter to have.

You know it's not just Vegas, but I can't think of a single program where you can undo anything after you've exited the application.

Maybe Microsoft will start doing this in it's MS-Office and then everyone else will follow...

:)
ibliss wrote on 3/21/2006, 3:30 PM
cubase sx and nuendo have this feature i think. and soundforge lets you save the undo history (in V8, i think)
GenJerDan wrote on 3/22/2006, 5:36 AM
I am not talking about deleting files or anything else "outside the program". I am talking about unsplitting or moving edit points or deleting something on a track or event etc

Yes, but what will happen if you DO delete a clip from the hard drive while the Vegas "History" thinks it's still available (even though Vegas would ask you about it when next you started the program)?

If you step thru the History then, it would either a) give you some sort of a "cannot continue" alert, b) crash, or c) "undo" some change that were never made, possibly screwing something else up.

And how big/long should the history be? Windows will let you write a 2gb file, if you want. :-)

So sure, they could error-trap and do all sorts of things to take care of every possibility. But it's not trivial, and I doubt if it would be worth the effort.



craftech wrote on 3/22/2006, 6:46 AM
Yes, but what will happen if you DO delete a clip from the hard drive while the Vegas "History" thinks it's still available (even though Vegas would ask you about it when next you started the program)?
==========
I can't remember EVER doing that since Vegas 2.0.
==========
And how big/long should the history be? Windows will let you write a 2gb file, if you want. :-)
=========
The History doesn't take up but a fraction of space. It is in KB. The History should be available until the end of the editing process no matter how many times you save the Veg file if you choose it as an option from the Preferences menu. Then the software should be able to immediately restore the editing to any point on it. Even with limitations to such a feature it would save hours of work. Hours!

John
FrigidNDEditing wrote on 3/22/2006, 8:02 AM
it's a great idea - but I bet it would just totally suck up system resources while it's trying to undo that one thing and then redo everything else in the workflow after that.

I like the idea - but I'd think it would almost have to act like a built in script or something that looks at all the things in the undo history and then once you undo that one thing it just re-applies all the things that you've done.

course I know nothing about programming and therefore am probably entirely wrong - but who knows - maybe I'm not :)

Dave
GenJerDan wrote on 3/22/2006, 9:16 AM
Nope. You're entirely right. A program doesn't know diddly about "what you're doing". All it knows is keystrokes.

If you go back to Point C and change the keystrokes that occurred there, it has no choice but to redo all the keystrokes you did after that point. Even if (as it might be in this instance) all you did was adjust how blue a clip was, it's still going to go through and redo everything else that came after...whether it needs it or not and whether it makes sense or not.
Mahesh wrote on 3/23/2006, 12:30 AM
Before Vegas, I used editor called Video Machine by Fast. The code was written in late 1980's. It still works on my Win98 machine.

It has cofigurable history feature. The history / undo is saved with the time line. It also saves the preferences in a text file.

Great feature.
Steve Mann wrote on 3/23/2006, 10:49 PM
Well, you can *almost* do this with Excalibur. Ed calls the function "emergency save", but I use it often to save a timestamped veg file. I can go back to the veg file from any point in my process.