[EMAIL PROTECTED] wrote:
wand->image->depth
The image depth is problematic because do you want the depth the image
file reports or the actual depth which may differ.
Ideally, I would like both. I would like the bit depth as it is on the
file on disk (to report to the user, calculate memory consumption
properly and/or keep it in memory -compressed- at that bitdepth after
imagemagick has read it).
And I would also like the bit-depth that would be faster to transfer
from imagemagick's memory to my own program's memory (ie. what would
give me just a memcpy, not an iterator copy). I'm also assuming here
that Imagemagick is smart not to keep 8-bit images at full quantum depth
(which is 32-bits in my case) when it reads them.
At the very least, I want to distinguish when the file as stored on disk
is <8bits (packed yuv, for example), 8bits, 12bits, 16bits, half or float.
--
Gonzalo Garramuño
[EMAIL PROTECTED]
AMD4400 - ASUS48N-E
GeForce7300GT
Xubuntu Gutsy
_______________________________________________
Magick-users mailing list
[email protected]
http://studio.imagemagick.org/mailman/listinfo/magick-users
