-
PNGIO library error–render failure
Greetings all,
I am rendering out frames of animation which will be played back in an immersive dome projection system. The frames are 2048×2048, 30 fps. I am rendering to .png files, no compression. I have used AE for many years, and have done this exact same task many times.Now, for some reason, I am getting this error when I try to render:
After Effects: AEGP Plugin PNGIO Support: PNGIO library error: IDAT: CRC error (5027:: 12)
…at which point the rendering fails. The error is not consistent over the entire project (about six minutes); some sections will render just fine, and some will fail. Also, some fail instantly, while some will render 2-10 frames and then fail. Finally, some sections will report the error, but when the OK button on the failure box is clicked, the section renders anyway!
My best guess at this point is that the source files (.png files) contain some sort of error or corruption that AE doesn’t like. However, I’ve used the very same files in the past with no issues. The one significant difference between this project and past ones is that this one is much longer, with many more layers of frame sequences and *a lot* more effects channels.
Has anybody had any experience with this error, and if so, can you offer any guidance? Thanks very much for any info,
Eric Knisley
Renaissance Computing Institute
UNC-Chapel Hill -
12 Replies
-
if you have render multiple frames simultanesouly on, PNG’s fail, they are not thread safe. turn off multiproc or use TIFF or PSD instead.
-
or instead, if you have quicktime pro, import the sequence and do a save as.
Problem solve 🙂
-
We had the same problem on a project and we finaly found the solution. I’m posting this today because I was searching myself the solution and didn’t found nothing on the web.
The problem is: we had a pre-rendered PNG sequence in our AE project, with some broken file (NOT MISSING). It’s a 2000 frames background playing in loop. We found that some image was rendered (for unknow reason) like this…
You can see the strange lines at the bottom. It’s very hard to see when you’re looking at a big sequence in windows and no image is missing. The PNGIO error come up in AE only when you are on that image, in the project. That’s how we found which exact frame was broken.
Also, we are rendering on a renderfarm. Maybe the PNG sequence had error because of this…
We re-rendered the broken PNG, restarted the render, and now it’s fine!
I hope that help!
-
I had the same problem. Turns out a few of my .png images were corrupt from a bad copy paste. Replaced the few bad .png’s and now it works fine.
-
Excellent discovery.
Thank you!
F
-
I have the same problem too. I resaved some broken files in photoshop and problem was solved!
-
I had the same problem. It turned out there was 7 frames out of my 200 PNG’s that were corruptly exported from my motion tracking program. I saved 7 working png’s with the same naming convention and After effects accepted my png sequence… lukily the 7 bad frames were at the beginning and didn’t ruin the shot
-
I get this error if I have ‘Embed Color Profile’ checked on the ‘Color Management’ panel for the PNG output format.
Unchecking this makes them render out fine.
…Max
thanks and my best regards…max
Head of Post Production
STUDIO LIDDELL -
I’m getting the same 5027::12 error in AE trying to see a C4D file with Cineware. I’m getting it once (after hanging for 30 sec. each time) for every instance of Cineware in my AE project.
Is this number just a general port failure number? If so, how do I start to track down the incompatibility?
-
[Greg C Neumayer] “I’m getting the same 5027::12 error in AE trying to see a C4D file with Cineware”
You might want to make a new thread so people can see your post a bit better. Having an issue with Cineware vs. PNG importing stuff will trigger very different people. You also might consider making a new post on the Adobe forums as well.
– The Great Szalam
(The \’Great\’ stands for \’Not So Great, in fact, Extremely Humble\’)No trees were harmed in the creation of this message, but several thousand electrons were mildly inconvenienced.
Reply to this Discussion! Login or Sign Up