Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Animation Codec – to keyframe or not to keyframe

  • Animation Codec – to keyframe or not to keyframe

    Posted by Michael Black fcp on May 11, 2007 at 5:49 pm

    So we’re creating some HD media content via after effects and FCP. Our process now is to work in After Effects, export a quicktime using the animation codec, which we then have to convert to an MPEG-2 with very specific settings (25 Mbps). So we’ve noticed that exporting an animation codec QT with the keyframe setting set to ‘automatic’ we’ve noticed a roughly 4 minute piece will be about 30 GB. However, we’ve found that exporting with keyframes set to every 24 frames, the file sizes are drastically different with an indistinguishable difference in the quality of the image.

    My question is: why is there a difference in these when using 100% quality in a supposedly uncompressed codec?

    The follow-up question is: is it worth using the keyframed codec to get the smaller file sizes? (We’re talking lots and lots of large files here) Or should we use the larger file sizes to ensure the greatest quality?

    Rafael Amador replied 18 years, 12 months ago 2 Members · 1 Reply
  • 1 Reply
  • Rafael Amador

    May 12, 2007 at 12:00 pm

    [Michael Black FCP] “My question is: why is there a difference in these when using 100% quality in a supposedly uncompressed codec?”
    Animation is a “lossless codec” when you set certain parameters, but as you can see you can adjustthe compression. Then, I guess, become “lossy”. If you set “Keyframe every 24 frames”, that mean that one in every 24 frames is an original one, the other 23 have some compression. If you set “keyframe every frame” all the frames have the full orinal information.
    Anyway if you go to DVD I would recommend you to export in a YCrCb codec: 8/10b Unc.
    Cheers,
    rafael

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