Page 1 of 1

PSD transparency issue with locked (invisible) layers

Posted: 2013-04-24T07:43:51-07:00
by tomk
Hi,

there seems to be a problem with detecting the transparency when converting PSD files which have a locked background layer set to invisible.
If you unlock the Layer in Photoshop (by duplicating & removing the locked layer) the transparency is detected correct.
This seems to be a regression, as it was working in a previous version of ImageMagick.


Not working File: http://magick-problems.s3.amazonaws.com ... locked.psd
Working file: http://magick-problems.s3.amazonaws.com ... locked.psd

Current ImageMagick Version (not working)

Code: Select all

~ $ convert --version
Version: ImageMagick 6.8.0-10 2013-04-22 Q16 http://www.imagemagick.org
Copyright: Copyright (C) 1999-2013 ImageMagick Studio LLC
Features:  OpenCL   

~ $ convert example-locked.psd[0] -format "width=%w height=%h transparent=%A colorspace=%[colorspace]" info:
width=1024 height=768 transparent=False colorspace=sRGB

~ $ convert example-unlocked.psd[0] -format "width=%w height=%h transparent=%A colorspace=%[colorspace]" info:
width=1024 height=768 transparent=True colorspace=sRGB
Older ImageMagick Version (working)

Code: Select all

~ $ /usr/bin/convert --version
Version: ImageMagick 6.5.7-8 2010-12-02 Q16 http://www.imagemagick.org
Copyright: Copyright (C) 1999-2009 ImageMagick Studio LLC
Features: OpenMP 

~ $ /usr/bin/convert example-locked.psd[0] -format "width=%w height=%h transparent=%A colorspace=%[colorspace]" info:
width=1024 height=768 transparent=True colorspace=RGB

~ $ /usr/bin/convert example-unlocked.psd[0] -format "width=%w height=%h transparent=%A colorspace=%[colorspace]" info:
width=1024 height=768 transparent=True colorspace=RGB


Just for clarity: This means the image loses the transparency when converting:

Code: Select all

~ $ convert example-locked.psd[0] out.png
~ $ convert out.png  -format "width=%w height=%h transparent=%A colorspace=%[colorspace]" info:
width=1024 height=768 transparent=False colorspace=sRGB

Is this a known issue or is this the expected behavior?

Best regards,
Thomas