Zarxrax wrote:Ok, now if the timecode effects things like that, then what does the frames/samples setting do? Cause you aren't selecting a timebase with it.
If you select that option, Premiere will calculate edit positions using video frames or audio samples, not by using timecodes. I think that's what Premiere will do, anyway; I know Cinelerra can operate on that principle, and I'm assuming that it works in a similar fashion.
You're probably going to be asking "so why the hell do we have timebases anyway?" I can't really answer this as I don't work in broadcast video, but I'm willing to bet that the reason has to do with broadcast video standards, such as NTSC and PAL, where duration is not considered in terms of individual frames but in hours:minutes:seconds:frames. That last component is where things start to get finicky, because of interlacing and all that fun stuff.
NTSC, for example, defines 60000/1001 fields/second as the "frames" component, which is 30000/1001 frames/second. If you try to record, say, exactly 30 minutes of material from an NTSC source, you'll have actually recorded 30 minutes and 1.001 frames of material. (I think.) Therefore you always work with integer numbers for frame-count; hence, Premiere includes these timebases to facilitate production of such video.
Watch me be totally wrong. At least it sounds like I know WTF I'm talking about.
This is a block of text that can be added to posts you make. There is a 512 character limit.