We're Hiring!

uint16 values restricted to uint8

Historical discussions about the Bio-Formats library. Please look for and ask new questions at https://forum.image.sc/tags/bio-formats
Please note:
Historical discussions about the Bio-Formats library. Please look for and ask new questions at https://forum.image.sc/tags/bio-formats

If you are having trouble with image files, there is information about reporting bugs in the Bio-Formats documentation. Please send us the data and let us know what version of Bio-Formats you are using. For issues with your code, please provide a link to a public repository, ideally GitHub.

uint16 values restricted to uint8

Postby noff » Wed Jan 15, 2014 10:41 am

Hi Everyone,
I am referring to the previous topic
http://www.openmicroscopy.org/community/viewtopic.php?f=13&t=7368
for a which a ticket has already been opened.
https://trac.openmicroscopy.org.uk/ome/ticket/11847

I checked the explanation given in the ticket, but I discovered that this is not the problem in our case:
The camera is a Canon EOS Rebel XSi (also EOS 450D in europe). In the specs of the camera there's an indicated datatype (bit depth) of 14 for the color of the raw files (not for jpeg, these are saved with 8), plus other 2 probably for the white balancing as it was said in the ticket. While opening the raw pics with other viewers we also get values much higher than 255 for the color, as we expect. We think that the values are just scaled to 255 somewhere in bfopen, also because this is the only software with which we got smaller values. The strange thing is that bfopen also returns uint16 as a variable type, the only thing is that they are all perfectly scaled to 255.

Has anyone an idea of what might be happening here, or did someone have this problem before?
greetings,
nico
Last edited by noff on Thu Feb 06, 2014 9:30 am, edited 1 time in total.
noff
 
Posts: 5
Joined: Fri Dec 13, 2013 5:53 pm

Re: uint16 values restricted to uint8

Postby mlinkert » Fri Jan 17, 2014 9:56 pm

Hi Nico,

Thank you for the additional information - we will update the ticket description accordingly. Our initial understanding of the problem was that the pixel values were correct but the pixel type was not, so it's helpful to know that the issue is actually with the pixel values.

Regards,
-Melissa
User avatar
mlinkert
Team Member
 
Posts: 353
Joined: Fri May 29, 2009 2:12 pm
Location: Southwest Wisconsin

Re: uint16 values restricted to uint8

Postby noff » Tue Feb 04, 2014 11:53 am

Hi Melissa!

Are you referring to the ticket in the other topic?
And yes, the pixel are there, with the right depth (16), it's only when opened with BFopen that the pixel depth is scaled to 8 (from 16).
Greetings,
N
noff
 
Posts: 5
Joined: Fri Dec 13, 2013 5:53 pm


Return to User Discussion [Legacy]

Who is online

Users browsing this forum: No registered users and 1 guest