PDA

View Full Version : Problem working with sequential PNG files

Troyan
07-27-2007, 02:48 AM
Hi there

Just updated to CS3 from 7 but have the same problem in both. We've rendered out several animation clips as sequential PNG files as they tend to be smaller than a Quicktime clip and easier to edit. Problem I run into is bringing the clips into AE and trying to edit with them or make a movie. I get an error at random times but can never finish working with any sequential PNG clips. The png's have been rendered out for HDV 1080 format with a 1.33:1 pixel aspect ratio. As I'm making a movie, I'll suddenly get the following error and AE will crash

Error (http://www.thedanse.com/cgtalk/AEerror.png)

Anyone have any insights? Obviously a problem with the PNG Input Output plugin, but the same thing happening in both 7 and CS3? Anything I can do to correct this?
berniebernie
07-27-2007, 09:10 AM
I've been working with huge sequences of HD PNG and TIFFS (not 1.33 px ratio though) with 7 and never ever had a problem with them.

Quicktime is another story....
Mylenium
07-27-2007, 09:19 AM
Obviously a problem with the PNG Input Output plugin, but the same thing happening in both 7 and CS3? Anything I can do to correct this?

Have you considered that Cinema 4D, or more appropriately Quicktime might be the bad guy here? PNG loading has been fixed in AE 7 and behaves just as well in CS 3, at least it does on my end. Only versions before had problems on the AE end. 16 bpc is still not supported, though. Your error points to premature end-of-file which would occur on writing the file, not when loading it. Check the offending files in an reliable external viewer like XnView, not QT or whatever. You can also easily batch-convert your files from there to restore them.

Mylenium
graymachine
07-27-2007, 02:56 PM
The first thing I do when I have sequence problems is to display the files in a list view with the file size and look for a size that is "out of place"... like

800k
800k
800k
2k <===== BAD!
800k
800k


Then re-render that frame from the 3D app.
ajcgi
07-30-2007, 06:32 PM
I had shed loads of png errors recently until I finally ditched version 6 and jumped up to 7. It's really convenient to work with them so I was irritated finding corrupted pngs all over my last project. It really slowed me down so hopefully V7 will solve my png hiccups.
It was doing the same to my softimage .pic files too.
That particular error though is only on unfinished files.
Troyan
07-30-2007, 07:42 PM
Sorry about not updating, but the culprit was indeed a bad png file. Replacing the one frame fixes the entire problem. There seems to be one bad frame in just about every batch of sequential frames causing this problem, hence why I'm seeing the problem in a lot of clips. Thanks for the input guys!
CGTalk Moderation
07-30-2007, 07:42 PM
This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.