[Octave-bug-tracker] [bug #30715] imread fails to read uint16 tif image

[John Swensen]

Follow-up Comment #15, bug #30715 (project octave):

Is there a reason Octave switched from ImageMagick to GraphicsMagick?  Was it
because of some of the speedups for GraphicsMagick?  If we are simply using
the *Magick for image reading and writing and not for image transformations, I
don't think any of the GraphicsMagick speedups are pertinent.  

I looked at the configure script for ImageMagick and verified the default
QuantumDepth for ImageMagick is 16.  I also compiled and ran gm_ver against
ImageMagick on Ubuntu 10.04 and verified the QuantumDepth is actually 16. 

Then, I did a quick modification of Octave's configure.ac to use ImageMagick
includes and libraries and Octave compiled with no modifications necessary. 
It reads your subset.tif image perfectly fine.

All this being said, I think imread and imwrite need a lot of work to be ML
compatible.  This mostly involves a lot of modifications to allow options for
the various file formats and better inference of output file properties (e.g.
bit depth, etc) based on the variable type passed in.  Currently the only
option that is handled is the quality option for JPG images.  I have a paper
due Wed Sept 22, but plan on working on this soon after it is submitted.

JWE, you can assign this bug to me (if you want) and I will make a monolithic
patchset that includes a switch back to ImageMagick and the additional ML
compatibility mods.  If anyone else has started on this already, let me know
so we don't duplicate effort.





    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?30715>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/