.m2t timeline positions not same V6 vs. V7

Jay-Hancock wrote on 9/14/2006, 8:55 PM
I put a .m2t on a new timeline in V6 and put the same clip on a new timeline in V7. I moved the cursor to a point where I could line it up right on the edge of a waveform (where someone is speaking particular words). Vegas 7 shows the cursor as being 7 frames ahead of where it was in the Vegas 6 timeline. What would cause this difference? A few details:

.m2t clip total length 22 minutes.
HDV 1080 60i
Quantize to frames is on
project settings identical in both V6 & V7.

This clip was rendered in Vegas 6. But I made new projects for both (empty, just dropped an .m2t on it). For sure I will make any changes to it in Vegas 6 not Vegas 7. New projects I can do in V7, though.

Comments

fldave wrote on 9/15/2006, 4:34 AM
Maybe v7 builds the peaks differently. If V6 built the peak file, and v7 didn't regenerate a new one, it could be off? Remember, the peak file is located in the directory where the video clip is.

Make a note of where the particular frame is in V6, close the veg, delete the peak file, then reopen your V7 project and let V7 recreate it.
Jay-Hancock wrote on 9/15/2006, 7:51 AM
The peak is a visual element.. If it was wrong then I assume that it wouldn't line up with the actual audio. But it lined up perfectly. The start of the waveform coincided with the start of a word from the speaker. But the timeline was different by 7 frames. Strange...
Steve Mann wrote on 9/15/2006, 5:58 PM
So, you're NOT saying that the audio and video timelines are off by 7-frames? They are still in sync?
Jay-Hancock wrote on 9/18/2006, 6:01 PM
(Sorry for delayed response). Yes, that's exactly what I am saying. In both V6 and V7,audio and video are in sync. But a particular frame somewhere on the timeline was in a different position in V7 compared to where it was in V6. It was different by 7 frames. I had mentioned waveforms because that was the point of reference I used to be sure I was placing the cursor on the same scene in both V6 and V7.