-
Error re-interpreting frame rates with Apple Pro Res codecs
I’m running into nonstop errors occuring during rendering and even scrubbing through movie files imported into an AE project. I’m on a mac, on AE CS4, on the snow leopard OS.
The files were rendered at 29.97 fps (apple pro Res HQ codec) out of a previous AE project, but I’m interpreting them at 23.976 fps after importing into a new AE project.
Does anyone else have this problem? Or are you able to recreate the situation and error?
The error: “Error (4) reading frame from file “/Volumes/FINAL FRONTIER/final frames and edit/scene 02 24p.mov”. (86 :: 2)”
I think I have discovered a problem with apple pro res HQ:
If you reinterpret 29.97 apple prores HQ footage as 23.976 (it should just play slower) but in after effects or even in final cut pro (where you can change the frame rate interpretation using cinema tools) an apple pro res file will sometimes just freak out and not play or display.
It must have something to do with the intermediate non-existent frames. The compression must specifically only be able to be decoded at the same framerate it was encoded in.
-
3 Replies
-
If using Cinema tools, this should work. Open the clip, hit conform and choose 23.98. Then import that in to AE and the frame rate should be 23.976.
ALso, make sure to render 23.976 out of AE and not 23.98.
Jeremy
-
I did exactly that (written in my post). It doesn’t make a movie that can play/scrubs every time (either in Final Cut or After Effects). There must be a flaw in the apple prores codec, or should I say, not a flaw… a limitation in it’s versatility.
I prefer Rob Bottin to Rick Baker
-
No, prores works in Cinema Tools. I would suspect your original media.
Once processed on Cinema Tools, you shouldn’t have to interpret in AE.
Open one of the originals in Cinema Tools. Click the Analysis tab. What does it say? You are aware that the audio gets resampled which might cause playback issues in FCP after conform?
Reply to this Discussion! Login or Sign Up