Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Forums Apple Final Cut Pro Legacy 29.97 Dropframe Issue !!! Need ADVICE ASAP

  • 29.97 Dropframe Issue !!! Need ADVICE ASAP

  • James Kim

    August 22, 2012 at 4:31 pm

    Hi There,

    I have a sequence in FCP that was edited in 29.97 NON Drop Frame and we need to prep it for broadcast delivery. I moved my sequence into a DROP frame sequence and got a very different timecode.

    The TRT is 30 min but when comparing the DROP Frame and NON DROP frame sequences I get these times:

    Non Drop frame: 29:38:07

    Drop Frame: 30:00:00

    Just making sure that there isn’t a serious issue with the Timecode between the 2 sequences and if so, how do I fix it?

    There is 8 minutes exactly of Commercial time built into the sequence.

    IF anyone can explain this issue to me that would be fantastic. This is our first episode of the first season so its a huge learning curve and I appreciate any and all help.

    Thank you in advance!

  • Shane Ross

    August 22, 2012 at 6:15 pm

    Well, the issue is that non-drop frame timecode isn’t real time accurate, while drop frame is. The reasons how and why can be found here:

    https://en.wikipedia.org/wiki/SMPTE_timecode

    Go to the part called DROP FRAME TIME CODE.

    Now…the big issue is that you edited your project and got it to time using non-drop frame code…and that was wrong. It won’t be accurate at all. You should have edited in a drop frame timecode sequence. So what you need to do now is…since your sequence is now drop frame, you need to finesse the cut so that it matches the timings needed in order to meet the spec of the broadcaster. This will have to be done manually, there is no one-button solution to make this just work automatically.

    This is one reason that you need to hire people who have broadcast editing experience. Sure, you can have people edit who don’t, but SOMEONE there needs to have broadcast editing experience, so they catch the small mistakes like this, that can lead to big issues, before they happen. A Post super, lead editor…assistant editor who knows. Someone. Broadcast editing requires a lot of specific tech knowledge.

    Shane
    Little Frog Post
    Read my blog, Little Frog in High Def

  • James Kim

    August 22, 2012 at 6:37 pm

    Thanks Shane, I really appreciate your input.

    It was a mistake for sure, I’m working on fixing that. SO our Broadcast Specs require that the TRT be 30:00:00, if its at 30:00:00 now, wouldn’t it be OK?

    Can you explain what I’d have to go in and FIX?

    Thanks Shane

  • Shane Ross

    August 22, 2012 at 6:54 pm

    It needs to be 30:00;00…DROP FRAME. Not non-drop. YOu yourself said it…you are short: Non Drop frame: 29:38:07. You need to add time.

    What you do is add time. You already have the footage in a drop frame sequence, right? Then you need to finesse the cut to make it go to 30:00;00 Drop Frame.

    Shane
    Little Frog Post
    Read my blog, Little Frog in High Def

  • James Kim

    August 22, 2012 at 7:17 pm

    Ok great, so I copied over the segments that were in a NDF sequence, timed it up in a DF Sequence, and now its TRT 30:00:00 DF

    Was it OK to just copy over the Segments from NDF to DF?

    Sorry If these questions seem basic, Your input is appreciated

  • Shane Ross

    August 22, 2012 at 7:19 pm

    Yes, that’s fine. That works fine.

    Shane
    Little Frog Post
    Read my blog, Little Frog in High Def

  • James Kim

    August 22, 2012 at 7:22 pm

    Great, thanks Shane, appreciate it.

  • jerry wise

    August 22, 2012 at 7:47 pm

    you can also get a good stopwatch and while QCing the show time it from start to end.

  • Shane Ross

    August 22, 2012 at 7:49 pm

    [jerry wise] “you can also get a good stopwatch and while QCing the show time it from start to end.”

    That’s hardly precise. Reaction times to press start and stop will mean you can be up to a second off.

    Shane
    Little Frog Post
    Read my blog, Little Frog in High Def

  • Joseph Owens

    August 22, 2012 at 9:19 pm

    [Shane Ross] “It needs to be 30:00;00…DROP FRAME. Not non-drop. YOu yourself said it…you are short: Non Drop frame: 29:38:07.”

    These numbers don’t add up. There is no way that 30:00;00 (drop) is 29:38:07 (nondrop). 22 sec 22 frames? I don’t think so, or you have some typos in the original message.

    30:00:00 non drop is 54,000 frames, which in Drop is 30:01;24.
    If you are looking to achieve 30:00;00 Drop, your target in NonDrop is 53,946 frames, or 29:58:06.

    jPo

    “I always pass on free advice — its never of any use to me” Oscar Wilde.

Viewing 1 - 10 of 15 posts

Log in to reply.

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy