[Kdenlive-devel] Cutting List Specification Version 0.04

[Jason Wood]

On Saturday 16 Nov 2002 6:45 pm, Christian Berger wrote:
> > On Saturday 16 November 2002 05:57 pm, Christian Berger wrote:
> > > But NTSC doesn't have an integer fps. NTSC has 29.9something.
> >
> > It's 29.97... well close enough to 30.
>
> OK, an hour of video with 29.97 fps has 107892 frames, a video with 30 fps
> has 108000 frames that's 108 frames difference, or about 3.6 seconds.
> This is far less acceptable than an error of a single frame caused by
> rounding errors.

I am starting to lose track of this discussion - I don't see what this has to 
do with either specifying files as frames, or specifying them as 
milliseconds.

Surely, if you specify times in seconds and partial seconds (e..g. 30.5212322 
seconds, to take it to a reasonable extreme) then the framerate does not 
matter - in one case you multiply by 30 to get the frame that you are working 
on (once rounded, frame 916), the other you multiply by 29.97 to get the 
frame you are working on (frame 915)... 

And since we all seem agreed that time should be specified in 
seconds/milliseconds rather than seconds/frames...  ???

Cheers,
Jason

-- 
Jason Wood
Homepage : www.uchian.pwp.blueyonder.co.uk