[Octave-bug-tracker] [bug #37689] imread strange result

[Andrew Hout]

Follow-up Comment #6, bug #37689 (project octave):

I would not say converting the data type of the input image to something else,
especially something that is not valid for any image format I know of, should
be the default behavior.
If the file you read in is encoded in uint8 it should stay uint8 unless the
user specifies otherwise.

If you end up joining two images together, one that is "logical" and one that
is not, and save the result you end up with a corrupted image because of the
incompatible data types.
That is the problem I ran into with this behavior and working around it
becomes very annoying when you have to check if every image has been converted
to a "logical" data type and then correct that.

Automatic grayscale conversion (MxNx3 to MxNx1) has similar issues but is not
as baffling as conversion to "logical" since the data at least is still in
"unit8".

    _______________________________________________________

Reply to this item at:

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

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