Hi.

You've already explained that clipping in raw data was difficult to detect (has different forms), and that clipping values may even depend on the color channel.

Imagine a theoretical picture, with, after pre_mul or cam_mul applied, has:
red clipping to 60000.
green clipping to 40000 (I consider g and g2 to have the same behavior).
blue not clipping, climbing up to 50000.

How does dcraw_process() -no_auto_bright=1- stretch this result to 65535?

I guess it can't stretch each channel independently, since this would mess the white balance.

Hi,

Apologies if I missed something but is there an API-function to determine the file-type of the raw-file opened (and unpacked) with LibRaw?

Specifically, I would like to know if the file represented by the unpacked C++ LibRaw-class is a DNG-file. I can obviously check the filename extension but I'm assuming LibRaw does some internal matching of file types. Is that exposed through the API somewhere?

Many thanks!

I own an old Nikon D100 camera and I use both Ufraw and Luminance HDR in order to get simple or HDR photos depending on content. Since Ufraw uses the old dcraw library, it produces a better result while dealing with bright areas. That is funny as they say libraw should be better. I used Darktable as a control app and it produces the same result.

On some files libraw_colordata_t::data_maximum is larger than libraw_colordata_t::maximum. Is this considered a bug or a normal situation? Doc says that maximum is a theoretical maximum value for a camera.

Hello,

Our project currently uses dcraw. We are having several issues and recently came across LibRaw.

Could you explain how we could transition to LibRaw while using the command line?

This will be running on an ARM distro of linux.

The app is actually running on a Raspberry PI within a dockerized node app. We are looking to grab the thumbnail, and then process the raw image with an applied color profile.

Any guidance in how to set this up would be greatly appreciated.

Thank you!