[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #41584] .bmp / .png display error for saturate
From: |
anonymous |
Subject: |
[Octave-bug-tracker] [bug #41584] .bmp / .png display error for saturated RGB image. |
Date: |
Thu, 13 Feb 2014 22:36:46 +0000 |
User-agent: |
Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/32.0.1700.107 Safari/537.36 |
URL:
<http://savannah.gnu.org/bugs/?41584>
Summary: .bmp / .png display error for saturated RGB image.
Project: GNU Octave
Submitted by: None
Submitted on: Thu 13 Feb 2014 10:36:44 PM UTC
Category: Octave Function
Severity: 3 - Normal
Priority: 5 - Normal
Item Group: Inaccurate Result
Status: None
Assigned to: None
Originator Name: Greg Jeffery
Originator Email: address@hidden
Open/Closed: Open
Discussion Lock: Any
Release: 3.8.0
Operating System: Microsoft Windows
_______________________________________________________
Details:
iminfo/imread for any fully saturated RGB image will return logical type
instead of uint8 if the pixel values are saturated. Same problem in 3.6.4,
probably 3.4.3 as well. To test this, create a solid red image, with all
pixels = 0xff, green=blue=0. Save as a .bmp or a .png. Try to display it;
Octave throws errors. It doesn't matter if .bmp, .png.
If the same image is saved as .jpg, though, Octave is happy, and it displays
properly.
Drop the value to 0xfe, image reports and displays properly.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?41584>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [Octave-bug-tracker] [bug #41584] .bmp / .png display error for saturated RGB image.,
anonymous <=