Benches Displays

6

Compressor displays wrong timecode for 23…

apple Verified

Imported from the Apple Support Forums via the Wayback Machine 🔗

This is something I just noticed because I'm forced to convert a bunch of 1080p Pro Res material (captured from HDV tapes) for an Avid editor.

If I open a Pro Res clip in FCP, it reads a start timecode of 00:29:55:21 NDF. If I drop the SAME clip into compressor it shows a start TC of 00:37:22:09 NDF. This is BEFORE any kind of process. It's simply reading the wrong TC from the clip. On the first clip digitized from the first tape the TC discrepancy is smaller, but still there (TC 00:00:03:27 in FCP, 00:00:04:21 in Compressor).

This problem seems to only exist with 23.98 material as I tossed a 29.97 SD clip in compressor and it read the TC correctly.

At first I thought it had something to do with the way I captured the HDV material. I used the Pro Res realtime conversion which doesn't allow you to log and capture, but rather captures the whole tape using a start/stop detect. However, when trying to troubleshoot the problem, I dropped in some P2 23.98 material from a different project captured using Log and Transfer. The TC discrepancy existed with that footage as well.

Does anyone know what's going on with this? I'm baffled.

Andy

6 replies

Sign in or join Beachball Help to reply.

  1. 0

    Julian Giardinelli

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I just recently discovered the same problem.

    I had 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. Like you, 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.

    Julian

  2. 0

    Andy Neil

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I confirmed this on a separate machine.

    23.98 NDF material displays incorrect TC in Compressor

    59.94 720p material displays incorrect TC in Compressor

    29.97 1080i60 material displays correct TC in Compressor

    29.97 NTSC material displays correct TC in Compressor

    It seems as though Compressor can't handle psf format material and the discrepancy is not uniform so simple math can't be used as a workaround. Anyone else see this?

    OS X 10.4.11, FCS 2, Compressor 3.0.2

    Andy

  3. 0

    Julian Giardinelli

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I just recently discovered the same problem.

    I had 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. Like you, 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.

    Julian

  4. 0

    Andy Neil

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Julian Giardinelli wrote:

    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.

    Can you explain how you do this? I've not used QTPro in this manner before but it sounds like a useful workaround in this circumstance.

    Andy

  5. 0

    lodestarfilms

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Hey guys, I have EXACTLY the same problem. Found another thread here with a workaround through cinematools:

    http://forums.creativecow.net/thread/8/965829

    I also found another workaround - instead of going through compressor, use batch export in fcp and choose a prores setting. this way the timecode stays the same and you can relink your footage without any problems. problem is that batch export is slow, ties up fcp and you have less control to customize your clip settings. but overall it works.

    This is clearly a problem with compressor. When checked in QT pro the timecode of a clip is displayed identical to the fcp timecode. compressor interprets the timecode of the source clip differently as one can see in the preview window.

    MAJOR BUG in my opinion.

  6. 0

    Motumbo Bénédict

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    We've also seen the issue across multiple systems, with different hardware configuration. The problem appears with the .3 series of FCS/Compressor. The last version of software that reads timecode from 23.98NDF clips properly is 3.0.2. Later release present the issue. The problem is not codec specific, but rather seems to be related to QT clips at 23.98NDF generated by FC.

    _This is a major 'showstopper' issue and I hope Apple Compressor crew will propose a fix soon._

    I sent this to Apple support a while back, and again recently once I found 6.0.5 is not working:

    Rep steps:

    Step 1. Launch Final Cut Studio 2.0.5

    Step 2. Create a New Project (File > New Project)

    Step 3. Create a New Sequence with the following settings:

    Frame Size: 1920x1080 - HDTV 1080i

    Field Dominance: None

    Editing TimeBase: 23.98

    Quicktime Video Settings

    Compressor: Apple ProRes 422 (HQ)

    Quality: 100%

    Advanced Options (Compression Settings): Frames Per Seconds: Custom/23.976

    Sequence Start TimeCode: 01:00:00:00 NDF

    Step 4. Insert 15 seconds of Bars and Tones (HD 1080i) at 01:00:00:00 in the sequence.

    Step 5. Export the sequence as a self-contained Quicktime Movie.

    Select the sequence in the bin. (File > Export > Quicktime Movie.)

    Save as 'exported
    at2398.mov' on the Desktop.

    Setting to Current Settings

    Include Audio and Video

    Markers: None

    Do not check Recompress All Frames

    Check Make Movie self-contained.

    Step 6. Launch Compressor 3.0.5.

    Step 7. Create a New Batch (File > New Batch)

    Step 8. Create a New Job with File (Job > New Job with File.) Select the 'exported
    at2398.mov' file

    Step 9. Click on the file in the batch area and look in the preview window. The source clip timecode indicates 00:59:56:10. It should read 01:00:00:00.

    Any converted clip will now have a timecode track beginning at 00:59:56:10. The 'Timecode Overlay' also displays this timecode.

    Still no reply from Apple tough.