Comps from After Effects being recognized as wrong frame rate?

[Josh Weiss]

The interesting thing is this. Both FCP and Quicktime see the frame rate as 23.98. If you drag the clips into a blank sequence it will make it a 23.98 sequence. However both FCP and QT see the timecode as 30. Therefore, the second goes to 29 before changing over. Any thoughts?

[Josh Weiss]

Yep, just killed all prefs, tested, same issue. Its not unique to my computer though. Tried on my assistant’s machine and another editors, all have the same issue, with different media rendered out of AE.

[Walter Soyka]

[Josh Weiss] “The interesting thing is this. Both FCP and Quicktime see the frame rate as 23.98. If you drag the clips into a blank sequence it will make it a 23.98 sequence. However both FCP and QT see the timecode as 30. Therefore, the second goes to 29 before changing over. Any thoughts?”

This is a reproducible bug, and I’ve just filed a report on it. After Effects is outputting a timecode track in the rendered Quicktime movie in the wrong timebase. If it’s bothering you, too, here’s the feature request / bug report URL:

https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform

To work around this, select your incorrect clip in FCP’s browser, then click Modify > Timecode… Change the rate to 24. When you click OK, FCP will replace the timecode track in the original Quicktime media on disk. This is one of the few operations in Final Cut that actually alters the source media.

Walter Soyka
Principal & Designer at Keen Live
Motion Graphics, Widescreen Events, Presentation Design, and Consulting
RenderBreak Blog – What I’m thinking when my workstation’s thinking
Creative Cow Forum Host: Live & Stage Events

[Walter Soyka]

[Dave LaRonde] “Should this be 24, or should it be 23.98 or 23.976? Just curious.”

Dave, you know me — I take those decimal points very seriously!

We’re talking about the timebase (how the timecode clock counts), not the frame rate, so it should be 24.

To help clarify the distinction, the difference in NTSC between the timebase (30) and frame rate (29.97) is what leads to the DF/NDF timecode insanity.

Walter Soyka
Principal & Designer at Keen Live
Motion Graphics, Widescreen Events, Presentation Design, and Consulting
RenderBreak Blog – What I’m thinking when my workstation’s thinking
Creative Cow Forum Host: Live & Stage Events

[Josh Weiss]

Thanks walter, I just wanted to confirm I wasn’t crazy

[Walter Soyka]

[Josh Weiss] “Thanks walter, I just wanted to confirm I wasn’t crazy”

Happy to help!

Please fill out the bug report I linked to, to help Adobe confirm that I’m not crazy, either. I think that this is a very serious bug that can cause serious confusion in multi-application workflows, and Adobe should know how many people it’s affecting.

Walter Soyka
Principal & Designer at Keen Live
Motion Graphics, Widescreen Events, Presentation Design, and Consulting
RenderBreak Blog – What I’m thinking when my workstation’s thinking
Creative Cow Forum Host: Live & Stage Events

[Josh Weiss]

Submitted already