-
Compressor 3 Reading Incorrect Timecode from Quicktime and Sequence
I am attempting to encode a SD DVD from 1080p 23.98 in FCP with burned in timecode. I have exported a Quicktime Movie from FCP, imported it into Compressor, added the correct filters, but when Compressor reads the timecode from the file it is incorrect. I am on a 2 x 3ghz Quad Core Intel Xeon Mac Pro system.
When I play the file in Quicktime in Quicktime Pro it reads it correctly. The timecode embedded in the QT file and in the FCP sequence starts at 00:59:55:00, but when brought into Compressor it reads: 00:59:50:10. Strange.
I thought it could be a bug in that system so I tried it on two other systems:
1. Powerbook G4 1.5 ghz
2. MacBook Pro Core Duo
Strange thing is that the Powerbook G4 worked perfectly and the MacBook Pro did the same thing that the Quad Core Mac Pro did, including giving the same exact INCORRECT timecode starting at 00:59:50:10. In each case I used the same file with the exact same settings in Compressor.Has anyone else experienced this? I don’t know why it would work fine on my G4 Powerbook, but not on the other systems. Any help would be appreciated.
Thanks.
-
2 Replies
-
You forgot number 3:
3) For some reason, QT timecode doesn’t understand 24p.
Or that’s the only sense I can make of it anyway.
Jeremy
-
I’ve had this happen to me before (and was just able to repeat it) and I know a few others have posted here as well on the topic. I think Jeremy has it exactly right. I’d go further and say it looks like it’s a 23.98 v 24 thing. Compressor is essentially treating your footage as drop frame, which Final Cut doesn’t even support. If you get the 24 non-drop equivalent of 59:55;00, you get 59:50:12 (on my TC calculator widget, anyway), which is too close to your number for it to be a coincidence.
I just tried my old trick of using Cinema Tools on the exported clip to conform it to 23.98. Compressor recognized the timecode perfectly this time. A word of warning, though: last time I advised someone to conform to 23.98 on this message board, they said they experienced a handful of glitchy frames, so you should check your output carefully if you try that.
– David
Reply to this Discussion! Login or Sign Up