Cr2 bit depth pimped? uint16 values restricted to 255
Posted: Fri Dec 13, 2013 6:53 pm
Hello Everyone!
I am working with RAW images from a Canon EOS Rebel XSi (also EOS 450D). The images of this camera are taken with a bit depth of 14 Bits, and stored into 16 Bits as usual. If I convert my pics to .Tiff images, I get my 16-Bit precision and everything is fine with my pics. If I try to load my raw Cr2 data into matlab with bfopen, I obtain uint16 variables without any error message, but they are all scaled from 0 to 255. It seems to me that there is some sort bug in the funcion, but we were not able to fix it so far.
Did anyone have this problem or knows how to help?
Thanks in advance.
Red, green and blue are my matrices with the values going from 0 to 255.
I am working with RAW images from a Canon EOS Rebel XSi (also EOS 450D). The images of this camera are taken with a bit depth of 14 Bits, and stored into 16 Bits as usual. If I convert my pics to .Tiff images, I get my 16-Bit precision and everything is fine with my pics. If I try to load my raw Cr2 data into matlab with bfopen, I obtain uint16 variables without any error message, but they are all scaled from 0 to 255. It seems to me that there is some sort bug in the funcion, but we were not able to fix it so far.
Did anyone have this problem or knows how to help?
Thanks in advance.
- Code: Select all
result = bfopen(path_of_file);
red = result{1}{1,1};
green = result{1}{2,1};
blue = result{1}{3,1};
Red, green and blue are my matrices with the values going from 0 to 255.