http://forum.videohelp.com/viewtopic.php?t=323450
So it wasn't the codecs, it wasn't vegas, it was the script.Guiboche wrote:"23.976" as a framerate, is not calculated as such.
Framerate is based on a fraction. The fraction is a number that has been divided.
So, 29.97fps, isn't that, but: 30000/1001 = 29.97
Same with 23.976, but, there are 2 ways and 2 fractions commonly used:
2997/125 = 23.976
or
24000/1001 = 23.976
I can never truly get any clear answers as to why this framerate discrepancy exists, but regardless of which method the editor uses, your source MUST use the same method or you will have framerate rounding and audio sync issues (and yes, if it reads framerate as 23.9760, there could be problems).
Onto another similar issue, Like BJ_M mentioned, some things may be wrong in 6.0 that were fixed in 7.0. I imported a veg project file that was created in 6.0 into vegas 7.0 and I noticed a frame that was off. I don't know what is up there..?? In vegas 6.0, in the timeline, frame 615 is using frame 126,200 in the original source and when I look at the same project in vegas 7.0, the timeline frame 615 is showing frame 126,201 instead of 126,200 for some reason. I think it may mean vegas 6.0 or 7.0 is screwed up with handling the original source or the veg file just doesn't work the same in both versions. They are both showing frames that is accurate to the original source footage(checked in vdub to make sure) in the vegas timelines, just the placement is different for some reason. Maybe it just means I must use one or the other editor because each one looks at .veg files differently. Not sure, though that would be one thing I'd like to figure out.
