RexA,';How would the software be able to know those "nopes" are not useful?'

We rewind tape, play it fwd. Some of the footage is not useful. But the point is, we can rewind and play back. Can't do that in Vegas.

FF3D has "stepback" and "return" feature. It doesn't undo anything, but lets you look at the bigger picture spacially. Boy, that really helps!

Browsers have a back and fwd button, most of those pages are "nopes". Pretty simple implementation compared to Vegas needs, I know, but it does provide a clear description of the re-wind-to-examine feature.

I can't undo a Vegas track click. Hmmm, what was the previous track/tracks I had selected? Vegas don't know, and that accidental click effectively un-selected my work. Rats. I'd like to step back and see what was selected so I could select it again. My short-term memory isn't worth a dime on eBay, and I couldn't find it to ship anyway.

Finally, now that dual/quad cores are becoming the new norm, and Vegas already can work 4 threads, why not let a user assign one thread to one core for the sole purpose of accomplishing this task? That's not much different than putting a camera over your shoulders and rewinding *that* tape. I'd have the render function shut off the "logger", turn it back on when render stops (thus allowing the render to use all threads). I'd have the "logger" snap data status every half-second, stream that data to a spot in ram, buffer that out to a disk. I'd limit the rewind to whatever disk space the user allots (like the trash bin sizing).

Vegas does a great job of recovering to an exact point of editing if the machine goes to lunch before you do. It's just not frequent enough.

Remember, Vegas stores change points in the .veg - we're asking to also store the relationships behind the active status of "keys" and cursors for that .veg - and let us replay that in a "Postview" screen, if not on the timeline itself.