Hi there,
I cut a really nice video along the rythmn of a piece of music. To get the beats exactly, I disabled quantize to frames. This looked fine in preview, but after rendering and watching on the tv set, there was a lot of jerkyness. I have redone the whole project with quantize to frames enabled. The offset between the beats and the frame borders aren't significant and eventually the final render looked best on tv.
Regards,
Thomas
Quantizing to frames assures that all your video edits will have the frames in the source videos starting at frame boundries on the timeline. This can help prevent lots of problems such as jerkiness in renders (allthough it ain't supposed to matter; Vegas is suppose to be smart enough to deal with it). If you need to adjust A/V sync at sub-frame levels, turn off quantizing and then move the audio track, not the video track. Then turn quantizing back on.
Sub-frame edits are regularly used in audio editing, where events occur in the millisecond domain.
BTW, Interlace is one of the main reasons to *use* Quantize-to-frames... is is the mismatch of fields at edits that can cause jitters and jerks. Quantize helps ensure that each frame of video starts on field-one.
Marty, QTF should have no bearing on how interlaced footage is handled. It's impossible to slip interlaced footage half a frame (one field) and have Vegas get confused. If you're seeing jitter or other artifacts, I'd like to see the project.
///d@