« Return to Thread: imread in Octave 3.2.0 on Windows doesn't work for uint16 tiff

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

by Benjamin Lindner :: Rate this Message:

Reply to Author | View in Thread

Benjamin Lindner wrote:

> Koen Vermeer wrote:
>> On Wed, 2009-06-17 at 22:01 +0200, Benjamin Lindner wrote:
>>> Koen Vermeer wrote:
>>>> Forgot to mention: I installed GraphicsMagick-1.3.5-Q16-windows-dll on
>>>> this machine.
>>> Hmm, the version bindled with the 3.2.0 installer is 1.3.3-Q8.
>>> I can not tell for sure but I wouldn't be surprised if mixing Q8 and Q16
>>> will result in problems.
>> I needed to install my own GraphicsMagick version to fix the magic.mgk
>> problem, but I can try your upcoming 3.2.0-1 to see if that one works
>> better. I am a bit worried though: I thought that the Q8 version doesn't
>> support 16 bit images. Does that mean that with your packaged Octave, I
>> won't be able to work with 16 bit images? If so, would I be able to
>> replace the bundled version with a Q16 one? Or would I be able to
>> convince you to bundle the Q16 version?
>
> 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?
>
> benjamin
>

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.

benjamin

------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing
server and web deployment.
http://p.sf.net/sfu/businessobjects
_______________________________________________
Octave-dev mailing list
Octave-dev@...
https://lists.sourceforge.net/lists/listinfo/octave-dev

 « Return to Thread: imread in Octave 3.2.0 on Windows doesn't work for uint16 tiff