Vegas7 cuts off about 1/2 sec from beginning

riredale wrote on 10/16/2006, 1:01 PM
I take any m2t clip and put it on the timeline for both V6 and V7. First thing I notice is that the audio sync is about 1 frame off, with V7 lagging. Based on hand claps, I can't tell which is more accurate.

But then I notice something else. V7 cuts about 1 GOP (15 frames) off of a clip at the beginning when compared to V6 showing the exact same clip. No big deal to me.

But then I see that V7 also repeats the first three frames at the beginning of the clip. In other words, in order to eliminate any freeze glitch at the start of every clip I should trim 2 frames.

Does anybody else see this?

EDIT:

This is with 7a, by the way.

Comments

jonask wrote on 10/17/2006, 12:53 AM
I have seen that too. I have also seen two repeated frames at the end of every clip.

A similar problem was discussed in another thread about scene detection:
http://www.sonymediasoftware.com/forums/ShowMessage.asp?MessageID=489171&Replies=35
(But I believe that it is not an scene detection problem, but something more basic.)

As a short-term solution, I posted a script in that thread that trims multiple clips.
http://web.comhem.se/~u82707197/vegas/Trim_Captured_Clips_v1.0.zip

For a long-term solution, I would suggest everyone that has this problem to report it to Sony...

Riredale, what source to you have. I have a Sony HDR-HC3.
riredale wrote on 10/17/2006, 8:40 AM
I'm using m2t files created by an FX1. What makes me curious is that V6 and V7 produce different results with the very same m2t clip.

I had posted way back in April that on my first miniproject shot with this camera that there was a 4-frame audio muting at the beginning of every m2t clip on the Vegas6 timeline. At the time I had concluded that the issue was with the FX1; now I think it was probably V6. As noted, V7 cuts out the first GOP or therabouts of each clip, including the muted 4 frames. Still, given the 3-frame video freeze, I would want to apply your script to all the captured m2t clips on the timeline, or at least teach myself to never use the very beginning of a clip.

As I noted elsewhere, GearShifting betwee m2t clips and their DV equivalents made it clear that the DV clips created with an earlier version of GearShift and V6 had shifted audio when compared to the m2t originals, a completely unacceptable outcome. Since GearShift is just an elaborate script wrapped inside a functional interface (as far as I know), then the fault must have been with Vegas6. I've spent the better part of the past week recreating DV proxies for my current 220GB HDV project. Just finished yesterday, and the m2t/proxy switch is now completely clean and in-sync.