Quantize to frames

kairosmatt wrote on 10/13/2007, 9:42 PM
Hi all,
Sometimes when I make edits with 'quantize to frames' switched on, things don't line up on the proper frame. It happens most often when a change is made and things ripple a little bit. But it also happens just bringing a clip in from the trimmer-the end of the clip is half a frame long or short (maybe the trimmer doesn't quantize).

Before I render, I make sure and go through everything looking for that jagged blue line between cuts. If you have a bunch of them, sometimes you can turn ripple on, trim half a frame off one clip and everything else ripples back to being on the frame.

Anyone else notice this, and does it really matter?

Comments

AlistairLock wrote on 10/14/2007, 2:08 AM
"It happens most often when a change is made and things ripple a little bit."

Could it be that you have made a sound edit, which isn't necessarily quantized to the nearest frame? When you next move a clip, the sound edge will move to the nearest frame, but the video associated with it won't.

I'm working on a project that a friend has edited. I persuaded him of the joys of working in Vegas, so he has now bought Vegas 7. It's his first project edited in Vegas. The whole thing has been handed over to me on hard disk.

What I'm noticing is that nearly cut is not on a proper frame boundary, so you get a flicker of the preceding frame and the incoming one on nearly every cut.

(Kinda hijacking the thread though it is related) Is there a script that checks and shifts material that's not quantised? Otherwise it's a long job checking every cut. I don't think he edited the project using a monitor as he would have seen this flicker.
kairosmatt wrote on 10/14/2007, 10:32 AM
John Meyer posted a great script here:

http://download.yousendit.com/E5C9A943556F1419

It will re-quantize your frames, if something goes off. This download is good for 7 days, but he said that anyone can post if they have a permanent home for it.

Matt
AlistairLock wrote on 10/14/2007, 11:43 AM
Wow! That's great. I'll try that.

Thanks Matt, and John Meyer.

Alistair
fwtep wrote on 10/14/2007, 1:16 PM
It could be that your Ruler (Project Properties) doesn't match your settings for Video. For example, you may somehow have your project properties set at 29.97fps but your ruler set to something different.

Fred
farss wrote on 10/14/2007, 2:01 PM
That's quite likely and I can't think of any other way to get it wrong unless somethings messed up in Vegas itself.
QTF should force everything to be on frame boundaries including audio. The new snappiness introduced around V7 time can cause problems with getting small gaps etc that you didn't intend but they should always be whole frames in size.
Of course if you turn QTF off and do a ripple edit your whole T/L can get shifted off frame boundaries, done that at least once myself.

Bob.
kairosmatt wrote on 10/14/2007, 8:51 PM
Fred-Thanks, I never thought to check the ruler properties too. This was probably the culprit in my 23.97 projects. Also, I switched to non-drop to see what happens.

Bob-when and why do you turn off QTF?