Re: imread in Octave 3.2.0 on Windows doesn't work for uint16 tiff

> On Wed, 2009-06-17 at 22:36 +0200, Benjamin Lindner wrote:
>> Benjamin Lindner wrote:
>>> What do you mean by a "16bit" image?
>>> According to graphicsmagick doc Q8 means that 8bits are used per color
>>> component. Does this not fit your needs?
>> addendum: I see the same behaviour you mention with the to-be-uploaded
>> r2 installer.
>> If this is because Q8 cannot handle it, then it should be a Q16 version
>> I guess.
>
> The data I work with (medical images) are frequently grayscale, 16 bit
> images (or a single 16 bit channel). I guess that in other scientific
> applications, 16 bit images are also used. I'm not sure what the
> downside of using the 16 bit version is.
>
> Just a snippet from the README in the download folder of GraphicsMagick:
>
> -x-x-
> If the file has "Q8" in the name, then it is compiled to support 24/32
> bit pixels. If the file has "Q16" in the name, then it is compiled to
> support 48/64 bit pixels. Most users will find that the "Q8" builds to be
> sufficient for their needs. They execute faster than the "Q16" builds and
> take less memory. Users who are using CMS color profiles, or are
> processing scientific/medical images will likely want to use a "Q16"
> build. Binaries are built using Microsoft Visual Studio .net
> Professional, 2002 edition, (VC++ 7.0).
> -x-x-
>
> I guess they agree with my need for 16 bits :-)
>
> Thanks for the support!
>