-
Error reading/rendering Apple Pro Res HQ files
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.98 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. I have a feeling that me trying to play them at a slower frame rate is what is causing the problem.
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 prefer Rob Bottin to Rick Baker
-
4 Replies
-
I did mean 29.97, and I’m interpreting the footage at 23.976.
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.
I prefer Rob Bottin to Rick Baker
-
I am on the same machine with final cut 7.0.2
after effects 9.0.2
I prefer Rob Bottin to Rick Baker
-
Yes, I think my only choice is to not go with the apple pro res HQ. I was doing this as an archival/master format that I could handle on my home studio setup.
I’m plan on some extensive color manipulation later on to the footage and felt like the deeper (but still space economical) the file depth the better.
What do you recommend? I can easily take my clips into compressor and re-output them into a bigger more stable framed format.
You recommend pro res 422?
I could also go with a good old PNG uncompressed frame sequence for each clip.
thank you so much for the response! Where should I post about this problem with the codec? To warn others?
I prefer Rob Bottin to Rick Baker
-
I’m doing work like this:
https://www.vimeo.com/10036011
I prefer Rob Bottin to Rick Baker
Some contents or functionalities here are not available due to your cookie preferences!This happens because the functionality/content marked as “Vimeo framework” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.
Reply to this Discussion! Login or Sign Up