Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Incorrect timcode with 24p footage in Compressor

  • Incorrect timcode with 24p footage in Compressor

    Posted by Julian Giardinelli on January 21, 2009 at 7:38 pm

    Hello Cows (I mean this in the most flattering way),

    I’m stumped on this one and was wondering if you’ve encountered it before.

    I have a bunch of footage that was captured from HDCAM tape (1080p/23.976fps) as Uncompressed 10bit QT files. I transcoded them into ProRes using Compressor and did an offline cut using these ProRes files. Then I started my online cut by relinking to the 10bit clips and I discovered that the starting TC on the ProRes files was different from the 10bit originals. All the frames were there but the TC started at some randomly different number (When compared to what Quicktime and FCP display) Compressor mangled the TC during the transcoding! (I checked and there is no consistent “offset”) I am doing no frame rate changes, nor interlacing/de-interlacing in Compressor – just changing the codec from uncompressed 10bit to ProRes. In fact, I noticed that if I just drop one of my 10bit clips into Compressor, the inspector window immediately displays incorrect TC. An interesting thing is it seems to be consistent between final cut systems. Another editor I’m working with had the same issue with the same clips, with exactly the same incorrect TCs popping up. I did some tests in this seems to happen only with 23.976 footage. This seems like a huge bug to me.

    This is going to make matching back to the 10bit footage for online quite a pain. For now, my solution is to copy and paste TCs from the ProRes clips to the 10bit ones in QT Pro to make them both match. Then I can relink in FCP w/o issues.

    Anyone else have this problem?

    =============
    Julian Giardinelli
    ju****@*********ce.com

    ==================
    Julian Giardinelli
    Film & Video Editor
    ju****@*********ce.com

    Julian Giardinelli replied 17 years, 3 months ago 3 Members · 3 Replies
  • 3 Replies
  • Matt Riley

    January 21, 2009 at 8:45 pm

    Indeed, you are not alone.

    I’ve posted about this problem/bug here (somewhere on the Cow, anyway) and in Apple’s forums and have never found a solution outside of modifying the TC after the encode, which sucks.

    You can either do the QT Player method like you mentioned or you can use FCP to manually change the TC on a per-clip basis (it’s under the Modify menu).

    If anyone has a solution to this, I’d love to know about it.

    -Matt

  • Jeremy Garchow

    January 21, 2009 at 9:22 pm

    This does seeem to be a bug with Compressor and 23.976 timecode. I encourage you to file a feedback form at Apple and hopefully it will get fixed. You can also change the tc in FCP through the Modify > Timecode menu which might(?) be easier for you if you being in your 10bit material and your ProRes material. It’s still a pain in the ass.

    https://www.apple.com/feedback/finalcutpro.html

    Jeremy

  • Julian Giardinelli

    January 27, 2009 at 7:14 am

    I got a friend who works at Apple (even the FCP dept!) so I sent the bug report to him. He said he’d forward it directly to the right person. Cross our fingers…

    ==================
    Julian Giardinelli
    Film & Video Editor
    julian@pixelsplice.com

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