I followed the instructions on downloading a specific commit of rawspeed from DarkTable and I applied the 4 patches (actually, patch 01. is not needed as it is already in the rawspeed source code).

I was able to compile RawSpeed 3 successfully.

But when I enabled RawSpeed 3 support in the Makefile.dist of LibRaw and make the correct reference to the RawSpeed3 directory, LibRaw would compile but with the following linker errors:

Hi Alex:

In the Structure "libraw_colordata_t: Color Information", there are two arrays:-
float rgb_cam[3][4], described as "Camera to sRGB conversion matrix", and
float cmatrix[3][4], described as "Camera color data read from RAW file (if any)".

Could you advise me on the various properties contained within these arrays, or which source file(s) describes these arrays?

Thanks

Steve

While working with the C API, I found some behaviour that I think is probably user error (my error) but might be a bug, and if it is my error, I would like to know how to fix it.

Looking at the documentation, after calling libraw_unpack() I expect the libraw_rawdata_t structure to be populated with the raw data.

This is partially what is happening, libraw_rawdata_t.raw_image[] is populated with the raw bayer data, the data in the structure appears to be correct, and I can successfully demosaic it into a proper image.

Windows platform libraw bring in dng sdk has no effect or can't open dng file

I compiled dngsdk under Windows as described in dngsdk.txt and tested dng_validate and it works fine
But when I bring the entire dng sdk header file and static library into libraw to compile and set the `USE_DNGSDK ` preprocessing macro, it compiles fine but when I open the dng file with libraw, it tells me that it can't be opened for unsupported file formats. So I would like to ask if I am missing something?

Hi,

I found a strange problem after analyzing the histograms on images right after debayering (16-bit data so 65536 bins per channel). We use PhaseOne cameras at work and we are interested to get images with a minimum of processing done (debayering, 16-bit per channel, linear response, nothing else). I tried different debayering algorithm using the user_qual but the same problem can be observed. I also created the distribution of the last digit of the pixel values. You can see clearly that there is a unbalance between even and odd numbers. See the attached screenshots.