My apologies re. "seems" - I did not intend to cast doubt on your reply. Thank you very much for all the helpful information, and for checking these installation instructions on your own RPi - that is greatly appreciated! I am looking forward to using LibRaw.

Thank you for the helpful information! So it seems LibRaw can be installed on an RPi - this is great!

Just to clarify, in the case where both options are available (apt install or compiling), is there a reason why I would choose one over the other (e.g. will the compiling option give me a newer version)?

Additionally, re. compiling, I found these instructions on rawpy's website (a package I'm hoping to use), which look similar to the instructions you provided above, but there are some differences - will either set of instructions work?

git clone https://github.com/LibRaw/LibRaw.git libraw
git clone https://github.com/LibRaw/LibRaw-cmake.git libraw-cmake
cd libraw
git checkout 0.20.0
cp -R ../libraw-cmake/* .
cmake .
sudo make install

Thank you for your help.
Than I there is another issue related to the Java wrapper - Sorry for that. The output_color=0 was already commented out therefore was never active (leading slashes).

I have now removed the options and use the lib with the default options. After JDK18 I have to generate the sources from the header file again and will see if that helps.

Nevertheless under windows I had troubles with ljpeg-8d which is not compiling. For now I have removed libjpeg from all builds because it is not so important for the users.

I do not see color change due to user_qual=0 (output_tiff=0, half_size=0 are the default value).

BTW, you set output_color=0 too. This turns off camera color to sRGB (or other known colorspace) conversion and will result in washed colors.

I try's the sample applications and you are right that all is working.

The problem is that the sample applications are not setting any params. As soon as you add my param list the output colors are also washed out.

I am using the following params to speed up decoding of x-trans files (For Canon/Nikon it doesn't matter). Without those parameters the encoding is much slower. But if I set only one parameter the color are washed out independently which parameter I set:
use_camera_wb$set(params$slice, 0);
use_auto_wb$set(params$slice, 0);
output_tiff$set(params$slice, 0);
half_size$set(params$slice, 0);
user_qual$set(params$slice, 0);

EOS R5 (released in 2020) and R3 (released in 2021) are different cameras.

R3 will be supported in the next public version (snapshot or beta/release, whatever come first)

This patch: https://github.com/LibRaw/LibRaw/commit/b31fa58eea272c4ba67ccdbd527f329a...

Exposes adjust_maximum_thr to the C-API

Hi Alex,

with dcraw_emu using -M -o 0 -c 0 -j -W -q 1 -4 -T as arguments, both TIFF images converted from CR3 now look equally bright, and the two TIFF images converted from the corresponding DNG files also look equally bright. However, the TIFF images converted from CR3 and DNG differ in brightness. Is this by design?

I'm now trying to figure out how to use it programmatically. The parameter adjust_maximum_thr seems not to be accessible from the libraw_set_... API. I'm using C# with InteropServices. I think I can write such method and amend it to libraw; or better maybe you should consider the addition of this method (something like libraw_set_maximum_threshold).

I already used in my program:

```
libraw_set_no_auto_bright(handler, 1);
libraw_set_bright(handler, 1.0f);

```
so I expected no automatic brightness adjustment anyway.

Thanks, LelliD

We never publish files that are sent to us without explicit permission.

Please use any file sharing service (e.g. WeTransfer/free option) and send the link to info@libraw.org

We do not provide precompiled snapshot versions. Please contact vendor of your software to re-compile it with newer libraw.

Yes (if you do not use earlier github snapshots)

As a result, you use very untested (and not supported) code path :)