Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe After Effects Smooth Credit Roll in 23.976 from After Effects to Final Cut 7

  • Smooth Credit Roll in 23.976 from After Effects to Final Cut 7

    Posted by Matt Babcock on October 7, 2014 at 12:46 am

    Hi Everyone,

    I’m having some problems making a smooth credit roll in after effects for a 23.976 fcp7 project and can’t make them smooth for the life of me. I’m using an equation(posted below) to convert my movement to whole pixel amounts and it works just fine in 1080i29.97. I’m also viewing these through a kona lhi to an FSI monitor.

    After talking with AJA my understanding is that the issue is 720p23.98 is an acquisition only format so final cut can’t actually play it back, it’s really playing back 720p59.94. I tried creating a 720p59.94 credit roll it and it plays back perfectly in 59.94 sequences but when placed in my 720p59.94 sequence unsurprisingly it goes all jittery again.

    I’m hoping someone out there has run into this before and has a good solution! My only idea at the moment is the convert the final output to 59.94 and then add the credits on since I understand correctly that is essentially what Final Cut is doing when it playsback 23.976 anyways.

    Equation I’m currently using but I’ve tried the rate+timeToFrames(time one) and the big funky one with lots of if than statements.

    t = time;
    fr = t/thisComp.frameDuration;
    x = value [0];
    s = -4; //Speed in pixels per frame

    [x, fr*s]

    Matt Babcock replied 11 years, 7 months ago 51,308 Members · 2 Replies
  • 2 Replies
  • Matt Babcock

    October 7, 2014 at 1:39 am

    Hi Dave,

    Thanks for responding so fast! But I think we are having a slight misunderstanding. The point I was trying to convey from AJA is exactly what you said, the card does voodoo to playback 23.98 at 59.94 on a broadcast monitor since 720p23.98 can’t be played back to broadcast gear natively. The voodoo that the AJA card does to play back 720p23.98 at 59.94 is actually what creates the jitter that is plaguing me.

    (Also I should have been more clear that I expected placing the 59.94 roll in a 23.98 wouldn’t look good, I was just hoping against hope that the card would realize that section was 59.94 and magically not insert pulldown work even though I understand it doesn’t work that way. 12 hour days will do strange things to your psyche)

    Just to make sure that the 720p23.98 is the culprit not just the 23.98 part of it I did a 23.98 comparison between 720 and 1080 and you wouldn’t believe they came from the same AE project. The 1080 23.98 isn’t quite as pretty as the 1080i but perfectly usable unlike my 720 credits. Also as part of my testing I’ve exported the 720p23.98 at as low of a rate of 2 pixels per frame and that still jitters like you wouldn’t believe on the broadcast monitor but plays back smoothly in canvas window.

    But you’re right I should post in AE Expressions forum and see if anyone knows how to alter the expression in a way that would help prep the AE sequence for the playback conversion from 23.98 to 59.94 but my suspicion is that it simply isn’t possible.

  • Matt Babcock

    October 8, 2014 at 12:38 am

    The reason why 1080 looks better than 720 is purely a playback issue. Since 720p23.98 isn’t a broadcast format, gear like AJA has to insert pulldown on the fly and play it back at 720p59.94 to play it on a broadcast monitor. It’s the inserted cadence that makes it look so awful and produces the jittery movement that was plaguing me.

    To step around this problem we’ve decided to create two masters, one for broadcast and one for web. The broadcast master will be uprez’d to 1080 23.98 and then married to 1080 credits. Since the web version doesn’t need to pass through any broadcast gear we can stay in the native 720p23.98 without any problems.

    If you’d like to talk about it more and have me send you some sample clips we could take this off thread and chat some more. This was a particularly annoying edge case that I hope to never encounter again.

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