I get the following warning message in the Blender 2.70.5 console when opening a .blend file created with a previous version of the application:
“libpng warning: iCCP: known incorrect sRGB profile”
Generally, files created with Blender 2.62 up to 2.70a open without returning the above warning with version 2.69 (official) and 2.70a (official).
Does anybody else got this warnings on such case (opening in 2.70.5 files created with previous versions)? Is it going to affect the rendering process or quality? Any idea by what the warning might be caused and why?
My current environment is as follows:
CPU i7 720Q, 8GB RAM, GeForce GTS 360M 1G VRAM, Win7 Pro 64bit
Blender is ALWAYS installed from the packed .zip distribution into its own dedicated directory. Currently running latest b.b.o Blender 2.70.5 Win 64bit hash: b707b07 dated 09/06/2014.
After further investigation I found that the iCCP color profile for many if not all the image files I have in PNG format is: sRGB IEC61966-2.1
Possibly this isn’t affecting rendering or else in Blender but I would like to get rid of this warnings. Any suggestion on how to “batch” correct hundreds of PNGs?
Any assistance or clue will be very much appreciated. Thank you
Well, apparently nobody else ever got this same warning message or know if this is simply an un-harmful warning.
If it doesn’t cause any problem at rendering time, and since it never popped up with previous versions of Blender as I stated above, it might be appropriate to let the user know to not worry about and simply remove the iCCP color profile from all the images or ignore it. I will consider to open a ticket in the bug tracker.
Hello, I am getting this error constantly from debug mode. In fact blender crashes every time I open and close user preferences in 2.71, making it unusable.
What is causing this? I’m on windows 8.1 (x64), nvidia graphics.
I have this same warning on my console using blender 2.7.1.
If i export a render as a .png, i can only use a few of the filters on photoshop (all the rest will not let me click on them) .
Whereas if i export a render as a .Jpeg,.Targa,.BMP etc, I can use all of the filters available on photoshop.
Clearly this error has actual negative effects on an exported .png image, and as of yet i have found no way of correcting this. Any one out there have a solution?
From what’s writtenhere “mogrify *.png” will strip what could be interpreted as a part of incorrect color profile from pngs in folder. This is part of http://www.imagemagick.org/ software.
blender crashes every time I open and close user preferences in 2.71
seems unrelated to this; rumors are video driver update or a new Blender version install might help.
Correct me then - Blender downloads do not include this library (yes, in the link i posted it was mentioned in the context of libpng 1.6+, current is libpng 1.6.16) yet during the build libpng header(?) information should be included for Blender to support png at all. So that the functions are contained in Blender executable likely.
I haven’t updated for a while OS on neither WinXP nor Linux pcs where i’m using latest available blender builds from builder.blender.org and haven’t seen any of such libpg/png related/caused errors - i should have had seen them, i use terminal&pngs quite often?
Should this mean that upgrade of OS is the cause, not Blender executable being built against certain version of libpng itself?
Just to mention - latest Ubuntu, The Vivid Vervet e.g, still uses libpng 1.2.51.
Then again there wouldn’t be any Photoshop on Linux; Gimp/Krita seem to not have issues.
If i build imagemagick on a fresh Ubuntu myself using libpng provided by distro (1.2.51), will it correctly deal with this issue?
it is do to the current libpng 1.6 being used by the operating system
think of it as the issue with gcc
not all OLD gcc3 or 4.1 code will build with gcc4.9
( do to SECURITY changes)
the same issue is with libpng16
IT wan fixed to improve operating system and program SECURITY
old versions of libpng malformed a line of code in the png image
and it was then NOT looked for
the new version LOOKS for that line of code
and if wrong will error
and the line WILL be wrong
so to fix this
resave png images using libpng16
that fixes the images
If i build imagemagick on a fresh Ubuntu myself using libpng provided by distro (1.2.51), will it correctly deal with this issue?
NO
the compatibility png12 is there as a PATCH
you can have both 12 and 16 installed ( i do this on opensuse13.2)
BUT!!! and this IS IMPORTANT!!!
set "alternatives!!! " to 12 or 16
this sets the OS default
i would leave it as 16 and use gcc to point to 12 IF needed and rebuild that code ( or deb from the src deb)