Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe After Effects CS5.5 Timecode Issue

  • CS5.5 Timecode Issue

    Posted by Patrick Woodard on August 9, 2011 at 6:23 pm

    When I render files using After Effects CS 5.5 with timecode support I get a resulting file with inaccurate timecode. My source material is Arri Alexa ProRes Files & Canon EOS Camera Files, both 23.98. When imported into After Effects they show up with correct timecode and frame rate. Once files are rendered out of After Effects and imported into Final Cut Pro or opened by QuickTime Pro they show up as 30fps and the time code is shifted. However if I import the rendered files back into After Effects they show up correctly in the browser.




    Patrick Woodard

    Phil Brooks replied 14 years, 10 months ago 2 Members · 3 Replies
  • 3 Replies
  • Phil Brooks

    September 13, 2011 at 6:19 pm

    I am having the same issue. Source footage is Canon 5D h.264.

    I am also conforming the 29.97 clips to 23.98. (Both by just dropping the 29.97 into a 29.98 comp, and also using the interpret ftg dialog)

    Files appear correct upon re-import into after effects, but QT and FCP and Resolve show the wrong TC.

    Strangely, both QT and FCP playback at the correct 23.98 fps, but the frame count goes through 29 frames.

  • Patrick Woodard

    September 13, 2011 at 6:30 pm

    I got word that Adobe is aware of this and will be fixed in the next update.

    Patrick Woodard

    http://www.patrickwoodard.me

  • Phil Brooks

    September 13, 2011 at 6:41 pm

    I have it set to “Timecode – > Use Media Source”. However, the link you provided says “Important: Changing the time display format does not alter the frame rate of your assets or output—it changes only how frames are numbered for display in After Effects.” So I’m not sure where the issue is happening.

    If Adobe is in fact aware as Dave says, let’s hope they solve this asap. Nothing more frustrating that a great new (overdue) feature that doesn’t work as expected.

    I’ll update if I find a workaround in the meantime.

    Thanks everyone.

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