1) This is 'linear DNG' (demosaiced) with 12 bit data
| | 3) BitsPerSample = 12 12 12

So, expected 'real max' value is 4095. In reality it is 4136, that's why LibRaw's decoder warns about data corruption (data value is outside manifested limit)

2) unprocessed_raw sample supports only bayer (not demosaiced) files right now, so you may need to write some code
After LibRaw::open_file() and LibRaw::unpack(), the (unprocessed) data is accessble via
-imgdata.rawdata.color3_image as an array of 3-component pixels
or
- imgdata.rawdata.color4_image as an array of 4-component pixels (for 3-color DNG, 4th component will be always zero)

Only one pointer is not NULL, check before use.
Historically, Adobe DNG SDK fills colr3_image array, but libraw internal decoder(s) use color4_array

When yo set use_camera_wb, LibRaw uses camera reported WB coefficients.
If not, 'daylight WB' coeffs are calculated from built-in color profile, this coeff may differ.

To avoid (most of) clipping due to auto bright, one may set auto_bright_thr to very low value (e.g. 0.0)

When I set use_camera_wb and use_auto_wb both to zero, I get a yellow cast on the image. When I set use_camera_wb to 1 and take the same photo with camera WB set to daylight it there is no yellow cast. (Camera is Sony A7R4, but I get similar results from Olympus Pen-F). I can email you sample images if you don't believe me.

Is anything else that could affect WB?

Here is the code I am using to read and process the image:

// create an image processor

LibRaw iProcessor;

// open the file and read the metadata

err = iProcessor.open_file(pathname);
if(err != 0)
return(TRUE);

// set to 16-bit output

iProcessor.imgdata.params.output_bps = 16;
iProcessor.imgdata.params.no_auto_bright = 1;
iProcessor.imgdata.params.use_camera_wb = 0;
iProcessor.imgdata.params.use_auto_wb = 0;

// metadata is accessible through data fields of the class

nx = iProcessor.imgdata.sizes.width;
ny = iProcessor.imgdata.sizes.height;

// unpack the image

err = iProcessor.unpack();
if(err != 0)
goto error;

// process the image

err = iProcessor.dcraw_process();
if(err != 0)
goto error;

Line 16405 in ./configure provided with 0.20.2 (downloaded from this site) is empty.
Around this line are libjasper checks.

Also, there are no 'ZLIB,zlib' strings in provided configure script.

Have you re-generated ./configure (using, for example, autoreconf)?

thanks a lot!! I will be checking it ;)

ok, but we use libraw in https://bitbucket.org/agriggio/art/wiki/Home that's why I am asking so ART can develop CRAW files ;)

Hello,

Seems it's supported since last release, I could not try since I work in linux heheh

Changelog
RawDigger 1.4.2 (2020-09-24)
Camera support:

Canon EOS R5, R6

Can I help somehow? providing samples or similar? let me know thanks

OK, thank you.

White level (data maximum) is not as easy as it should be.

LibRaw provides (estimated) data maximum in imgdata.color.maximum. This value is
- either hardcoded (this is derived from dcraw.c)
- or last item of linearization curve
- or determined using camera bit count

For many formats/vendors/settings it is correct, for others it is overestimated (for example, Panasonic low ISO w/ full-well limited sensor, also Canon's intermediate ISOs)

Also, there is imgdata.color.linear_max[]. If filled (nonzero) this value(s) represents vendor suggested white point parsed from metadata. This value is usually way too low (there are a lot of pixels above this threshold), but it is (yes) suggested by vendor.

Also, there are vendor-specific values in parsed metadata fields (e.g. canon.NormalWhiteLevel/canon.SpecularWhiteLevel)

Alex,
Apologies for jumping the gun and reporting the issue in 0.20.0 as a bug. I just saw that my tests had failed and assumed a regression. But I agree that 0.20.0 behaviour is better.

I will upgrade to 0.20.2 for the updated raw-identify behaviour.

Regards,
Dinesh