Not enough, even one frame before is too much because this ends in trial&error.

Marco

No. the numpad-zero method doesn't help, but this feature was added to Vegas to address this need. They just didn't understand the request.

Rob

I don't agree at this point. I find the "Numpad-Zero-function" well implemented for what it is meant for. It is for checking just done cuts which needs both some pre-roll time as well as some post-roll time. This is how almost any pro-editing system works (if used this way) and I appreciate much how it works in Vegas. Without any pre-roll this function would be completely useless for what it is meant for.
But we now speak about something completely different.

Marco

Actually, I'm pretty sure that Numpad-zero function was added to address this because it appeared out of the blue after I made a series of product suggestions for it to SCS (or maybe it was Sonic Foundry at the time). And what I was suggesting was the sort of play-ahead/behind preview I've been describing.

Although I can't really say for sure that I instigated this, I remember that it came about close on the heels of my little campaign and there wasn't anyone asking for anything more like what we ended up with, at least not publicly.

If you're finding a use for it, that's great, but I really think that's an accidental application.

Rob

And what's so bad about trial and error? If it gets you what you want....

My workflow is to position the playhead where I think it should be and use the space bar to initiate playback. Hit the spacebar twice to repeat. If I'm not satisfied, move the playhead one frame and repeat the process. It usually takes only a few seconds to zero in on the desired cut point.

That works if you haven't changed the spacebar behavior to Play/Pause in prefs. Good point, though, because in Vegas' default mode the cursor would always come back to the start point when you use the spacebar to play.

Rob

<< And what's so bad about trial and error?

Sometimes it's fine but sometimes there is just no time for trial & error. This may sound strange because we talk about a second of time but I think many editors know what bearing one second here and one second there means. In the end this can determine wether an editors job is considered to be done well or badly.

I ask otherway round: Why being satisfied with trial & error if we have such great workflow tools like scripting which can prevent us from trial & error? I'm not going to complain but to improve.

Marco

One second here, one second there, and before you know it you're talking a whole minute!

Hehe, but you don't know they call us the "flash&lightnin-editors" ... :D

Marco

It might be a minute wasted out of every 20 but I think it gets frustrating for people, especially when they've seen better. And when something is frustrating those extra seconds are really resented.

Rob

Just another idea - maybe as a workaround, maybe as a base for scripting:

What about drawing a loop-region from the current cursor-position up to the next few frames (5 or 7 seem to be fine for spoken words), switching to loop playback and while playbacking moving the loop region!?
O.k. - the single steps if manually taken are annoying, but at least this works and maybe with some scripting magic ... ;)

Marco