Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro 23.976 footage is interpreting as Drop-frame TC

  • 23.976 footage is interpreting as Drop-frame TC

    Posted by Michael Duff on February 3, 2020 at 11:21 pm

    Hi,
    I’m importing some 23.976 footage (sent from Media Composer) but Premiere is reading it as drop-frame timecode and therefore all the timecode is off. I can’t find anywhere to set it to just be 23.976 …. any idea what is going on?
    THanks

    Michael Duff –
    Bearcage Productions, Australia
    http://www.bearcage.com.au

    John Shyloski replied 5 years, 8 months ago 4 Members · 12 Replies
  • 12 Replies
  • Shane Ross

    February 4, 2020 at 1:34 am

    Since 23.98 cannot be drop frame by any stretch of technology (only non-drop), this is puzzling. Are you in a 29.97 sequence?

    Or do you mean you want 23.98 to be drop frame timecode? Just making sure you said what you mean to say..

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

  • Michael Duff

    February 4, 2020 at 7:49 am

    Thanks for the reply.

    The footage is 23.976 from Media Composer and has TC burnt in. Importing into PP and interpreting at 23.976. In the source monitor the timecode does not match what is burnt in and the timecode is show semi-colons (;).

    The burnt in TC is definitely correct in Media Composer but for some reason it seems it isn’t interpreting correctly in premiere or something ..?

    Michael Duff –
    Bearcage Productions, Australia
    http://www.bearcage.com.au

  • Michael Duff

    February 4, 2020 at 10:52 am

    Also, when I open the files in Quicktime the TC is correct and matches the burnt in TC from Media Composer. But as soon as it comes into PP it is incorrectly interpreted. See screenshot:



    Michael Duff –
    Bearcage Productions, Australia
    http://www.bearcage.com.au

  • Shane Ross

    February 4, 2020 at 4:14 pm

    Sorry, your screenshot didn’t come over.

    Look at the burned in code…what number does it go up to? Are any frame numbers skipped? Is it timecode from the source footage? Or is it sequence timecode?

    And why are you “interpreting” the footage? Isn’t that what is done to make slow motion? Interpret 60fps to 30 or 24, and it’ll play all the frames, but slower? So if the footage is 29.97…and is drop frame…if you interpret it as 23.98, it’ll play slightly slower. I might be completely misunderstanding what you are saying here.

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

  • Michael Duff

    February 4, 2020 at 9:08 pm

    Thanks – hopefully the screenshot links below are working now.

    The TC is source timecode and each clip has been exported from Media Composer with this TC written into the file. The TC is also burnt in as reference on the screen. The TC in Media Composer and when I open the clips in Quicktime match between the file TC and the burnt in.

    But, when I import into Premiere the TC does not match up. The start TC does not match up and for some reason Premiere is showing dropframe timecode (; instead of :).

    I’m not interpreting the footage as anything other than what it is. I was only saying that it is being interpreted into Premiere as it should be. Footage was shot at 23.976, exported from Media Composer at 23.976, and is importing to Premiere at 23.976. But this weird thing is happening where Premiere is reading the TC incorrectly – for some reason as dropframe – and therefor all the timecodes are out.

    Does that make sense?

    screenshot2020-02-03at8.54.00pm.jpg

    Michael Duff –
    Bearcage Productions, Australia
    http://www.bearcage.com.au

  • Shane Ross

    February 4, 2020 at 10:23 pm

    Ah, ok, I see that now. It does make sense.

    But why are you INTERPRETING the footage? If it’s 23.98, and your sequence is 23.98…why are you even doing that? What happens if you DON’T interpret the footage?

    Why the HECK is it showing it as drop frame? So odd…

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

  • Michael Duff

    February 5, 2020 at 10:41 am

    I’m not actually changing the interpreting of the footage. I mean, all footage is interpreted by Premiere when you import it as whatever it is meant to be. I’m not re-interpreting it. I just opened that window to show that the interpretation was correct …. 23.976

    But yeah … something wacky. I have upgraded to Catalina a couple weeks back and someone said that could be bugging it out?

    Michael Duff –
    Bearcage Productions, Australia
    http://www.bearcage.com.au

  • Doug Metz

    February 7, 2020 at 11:13 pm

    What is your sequence frame rate?

    Doug Metz

    Dalton Agency

  • Michael Duff

    February 10, 2020 at 11:18 am

    23.976 …

    but as shown above if it is even showing drop frame TC on the source footage window not just the sequence

    Michael Duff –
    Bearcage Productions, Australia
    http://www.bearcage.com.au

  • Michael Duff

    February 10, 2020 at 12:56 pm

    Just tried in Davinci and the TC is being read correctly. Tried on another Premiere computer with the same problem. So seems like some weird bug in these files that Premiere doesn’t like but MC and Davinci are fine with

    Michael Duff –
    Bearcage Productions, Australia
    http://www.bearcage.com.au

Page 1 of 2

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