-
QT Timecode Export Ultra Emergancy
-
this is a pretty cold thread, but just wanted to post this here:
“After Effects writes startTimecode and altTimecode values into XMP metadata. You can view these values in the Start Timecode and Alternate Timecode fields in the Dynamic Media schema in the Metadata panel.”
Under Window>Metadata>Dynamic Media, there’s an Alternate Timecode field that I’m pretty sure would have solved this problem.
Many months too late to the party, i guess.
r
-
It seems like this topic has faded away a bit…but I’m having a similar issue – and ANY help would be greatly appreciated.
My 23.976 ProRes 422 renders out of After Effects CS5 seem to have 29.97 Timecode tracks embedded in them. When bringing these into Final Cut Pro, they do not playback correctly – since there is this discrepancy. When I delete the Timecode track with Quicktime Player, they seem to be fine now.
The Metadata panel in AE CS5 indicates that the ORIGINAL footage has an Alternate Timecode Time Format of “23976Timecode”. When I bring my RENDER back into AE CS5, the Metadata panel indicates that it has a Alternate Timecode Time Format of “2997Timecode”.
I can find NO place in After Effects where I can alter this – it seems like there is a default XMP Metadata flag set somewhere, but I don’t know where.
I’m working with 23.976 ProRes 422 footage, importing into AE CS5, creating a 23.976 comp, and then rendering back to a ProRes 422 23.976 quicktime.
Any help would be GREATLY appreciated.
Thanks.
vfxjokir@gmail.com -
I know you posted this months ago Josh, but I have the exact same problem. I had another thread about this in the Final Cut forum, but I think it is an AE problem. Its not that my clips don’t play back right, just that the timecode doesn’t match. I did tests with 29.97 and everything is fine, its just 23.98. Premiere sees the AE render just fine, but FCP doesn’t. I posted a bug report to adobe a few times, but I know its ignored as a friend of mine got his hands on CS 5.5 and the problem is still there.
-
I know you posted this months ago Josh, but I have the exact same problem. I had another thread about this in the Final Cut forum, but I think it is an AE problem. Its not that my clips don’t play back right, just that the timecode doesn’t match. I did tests with 29.97 and everything is fine, its just 23.98. Premiere sees the AE render just fine, but FCP doesn’t. I posted a bug report to adobe a few times, but I know its ignored as a friend of mine got his hands on CS 5.5 and the problem is still there.
-
IME, AE CS5.5 Renders Wrong TC Regardless of Comp Settings!!!! (30fps when comp is 24fps and with the wrong start time. Even if you enter correct start time in comp settings, it’s still the wrong frame rate TC when rendered). A huge problem for offline and manual round-trip work flows. Below is a painful but simple working solution. Maybe I can help save someone the headaches I went through to come up with this. COME ON ALREADY ADOBE!!!
In QT7 Pro = Open Original Clip and Read Start and End TC. Click on TC display at bottom left to select proper display mode.
In FCP Import and Select New Clip in Browser.
Modify Menu = Timecode
Enter start TC read from step 1.
Choose proper frame rate.
Choose proper Drop Frame setting. Columns separated by a : = Non-Drop (01:00:00:00), ; = Drop (01;00;00;00).
Click ok.
Verify start and end TC of AE render match original clip.
Anyone else have a better solution? Please chime in!
-
After more time, I think this actually may be a FCP7 / QT issue. I thought it was an AE issue, but then I realized that both Premiere Pro/ After Effects/ and FCPX saw the timecode right.
So it might just be a different way of annotating timecode, but I’m not sure.
-
Well I’ve got proxy movies rendered out of MB Grinder with burn in that is identical to what FCP7 and QT Pro 7 read and write, but AE and PPro CS5.5 fudge that up royally. I wouldn’t doubt that FCP X is reading the TC tag wrong as well.
-
As far as I can tell, this is what you have to do. This is not an issue in CS3 or CS4, but it certainly is an issue in CS5.
Clearly an After Effects bug.
As for batch fixing this – I’m looking for a tool for that – Sebsky tools does not seem to be functioning with the latest versions of QT.
Reply to this Discussion! Login or Sign Up