FCP and QT timecode discrepancy

[Jeremy Garchow]

Totally awesome for posting this.

I will let you know what I find.

Jeremy

[Jeremy Garchow]

Okay, I think you have found a Quicktime bug with 23.98 material. If you change the sequence to 1080i 29.97, everything matches up. If you change the sequence to 720p23.98, it’s the same exact amount of frames off. Since everything is matching back up in Final Cut, this must be some sort of Quicktime reporting error (which Quicktime itself does a pretty lousy job of reporting/displaying important stuff like frame rate anyway). The data appears to be tracking correctly back to Final Cut and Final Cut also reports back correctly. Somewhere in Quicktime something is not connecting to the correct data.

I would submit a report back the Final Cut feedback link and yell at Apple.

Let’s hope they listen.

Jeremy

[Robert Longwell]

Thanks for confirming. I knew I wasn’t crazy (aside from the usual stuff).

I’m definitely telling Apple.

Robert Longwell

[Robert Longwell]

Just a little more info…

This seems to only be an issue for 720p60 and 1080p23.98 sequences. 480i and 1080i are not affected. I did not test any other formats.

Robert Longwell

[Jeremy Garchow]

720p24 didn’t work for me. Didn’t try 720p60.

[Julio C maldonado]

i have the same problem that u have rightnow…and im dealing with it…for weeks. so can u tell me how to export it and get the same numbers in Quick time…i’ll aprecciate it. Thank u.

JC

[Adriel Brunson]

I did find that it was a problem with drop-frame and non-drop.
FCP was set one way, the subtitle app was set the opposite. It takes about 5 minutes for the difference to be enough to be a problem but you’ll be off about 2 seconds with a 30 minute program.

I thought I’d checked this before – maybe I had. I’ve updated all the apps several times since this started. At any rate, (no pun intended) this problem disappears with subtitles when everything is exactly the same regarding drop vs non-drop.

-a-

[Robert Longwell]

There is no fix.

I was on the phone with Apple QT engineers explaining the situation, I think they get it but didn’t offer any fixes or resolutions.

Robert Longwell