Re: Processing timeranges with unusual precision.

Time::MSF?

Oh, and also, how does this interact with drop-frame formats, or are they no longer used?

Warning: Unless otherwise stated, code is untested. Do not use without understanding. Code is posted in the hopes it is useful, but without warranty. All copyrights are relinquished into the public domain unless otherwise stated. I am not an angel. I am capable of error, and err on a fairly regular basis. If I made a mistake, please let me know (such as by replying to this node).

Comment on Re: Processing timeranges with unusual precision.

Replies are listed 'Best First'.
Re: Re: Processing timeranges with unusual precision. by submersible_toaster (Chaplain) on Jan 13, 2003 at 00:50 UTC
As far a dropframe formats go I believe that dropframe TC is a display property only - to cope with the fact that NTSC is not truely 30fps but 29.97. So the TC is accuratly counting H:M:S at 30fps , whilst dropframe gives the realtime equiv. it's explained better linked above. Update: Another gotcha about EDL format is that TIMTOWT specify dropframe mode.. but that should be the responsibility of a parser , hmm, creating work for someone now , aren't I? (rhet.) I can't believe it's not psellchecked	[reply]

Replies are listed 'Best First'.

Re: Re: Processing timeranges with unusual precision.
by submersible_toaster (Chaplain) on Jan 13, 2003 at 00:50 UTC

As far a dropframe formats go I believe that dropframe TC is a display property only - to cope with the fact that NTSC is not truely 30fps but 29.97. So the TC is accuratly counting H:M:S at 30fps , whilst dropframe gives the realtime equiv. it's explained better linked above.

Update: Another gotcha about EDL format is that TIMTOWT specify dropframe mode.. but that should be the responsibility of a parser , hmm, creating work for someone now , aren't I? (rhet.)

I can't believe it's not psellchecked

[reply]