After Effects AEGP plugin PNGio support PNGio library error known incorrect sRGB profile (5027:12)

[Dennis van Gulik]

I'm trying to export a png-sequence for Lottie and whenever I press render I get this message. 

I've tried every fix I could find, I re-exported the original png-sequence, I exported as a JPEG-Sequence, tried renaming them, tried saving them from another app, but nothing works.

What does work is when I export the PNG sequence from the render queue and then turning on the option of embedding the color profile, then it renders fine.

The thing is, Bodymovin, the Lotty plugin, does that automatically, without being able to change any settings (that's how they compress the png's/jpg's before adding them to the json).

I never had this problem before, with any PNG sequence at any moment, with Lottie. It happened now after I've updated every Adobe app.

[Dennis van Gulik · Accepted solution]

I fixed it.

You can edit the general color profile output from your File -> Project Settings and than the tab "color". I switched from sRGB to Apple RGB and my Lottie Animation exported as it should. I haven't checked the colors yet, but if they suck I can always try another color profile. 

Anyway, for now this works.

[danieljbetts]

Thank you so much for this. Been pulling my hair out all afternoon 🙏 

[instantpierre]

Worked! Thanks for posting this, it's been so painful trying to figure this out. 

[persondudeguy]

> sRGB to Apple RGB 

My colors are noticeably different when I switch to Apple RGB so this is not solved for me. 

[Dennis van Gulik]

Hi persondudeguy, I know. You could try other profiles to check which one works better for you. You don't have to select Apple RGB per se, you could use another one. But it is not a permanent solution either, it's just so you could start After Effects at first. When that works you can troubleshoot where the problem is. I just left mine at Apple RGB and didn't think about further.

Anyway, just try another color profile my guy, maybe another one works better for you.

[persondudeguy]

I was exporting renders for a couple days and the gamma was wrong and i could figure out what I was doing wrong and then i realized I'd changed the project color management just to be able to output PNG. Hours of confusion and lost time because of d this big. So frustrating.

[fnordware]

Yeah, hit this bug in AE 22.2.1. It's gone by 22.4. You can get around it by not embedding your ICC profile.

Apparently the libpng folks don't like some very widely distributed Adobe profiles. Adobe themselves must have updated their libpng without turning off this check.

[Art by Aymeric]

I'm on 22.6 and can confirm the bug is still there. I went through every single colour profile, none worked.

Working on PC, C4D image sequences exported at 16bit. So annoying. In over 10 years never seen this error, now its rampant. 

[fnordware]

Are you getting this error when reading PNGs from C4D? The original bug referred to PNGs written out of AE.

[Mark25159040zoyk]

Found a solution that worked for me: used Media Encoder to re-render the .png sequence to a .png sequence with different name and folder. For me it was 3dsMax and Vray render, so probably some frame that was saved wrong or something happened during that save...

[William31565619h03h]

3DMax for me also - just was updaing a file from last year in AE 22.6.5 on PC, will move my project with newer version of AE (2024) and see if that error is still there.  Original old files didn't give me any error codes, new added renders from MAX are springing up with new PNG sequence render updates. Will respond on teh AE 2022 to AE2024 migration.