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.

I’m still not sure I fully understand what LibRaw even is.

Is this something that executes in command line, or is it just a compatibility add-on for applications that already work with RAW files?

My goal is to simply convert RAW files from a Sony A7 II to something that is natively supported in Mac OS X Leopard 10.5 while still using Leopard.

I know I could do this in another OS but the point is that this is a hub for my workflow for years and I don’t want to lose Aperture support or change my tools just because I got a later camera.

Hardware is Intel x86-64

The configure scrupt is hanging during showing „Checking cross compiling…“. After this line nothing is happening anymore.

What could be the root cause for this ?

Clemens

Hi!

While using libraw.dll together with unprocessed_raw.exe to decode various RAW file formats to simple to read PGM files for experimentation with my program
I found this strange thing with only Sony ARW files. That even for the input files that are meant to be 12bit (RAW pixel values somewhere in the range of 0-4095) I get output files with RAW pixel values somewhere in the range of 0-16383 (corresponding to 14bit).

Looking at the histograms confirms that "empty spaces" are added.

Hi everyone,

I was using libraw 0.19.2 in my application for reading raw images. Once I decided to upgrade to 0.20.2 version image import obviously slowed down.
I would like to know if there is any specific reason for that, or maybe some new functionality has been added for importing that I miss for new version.

Just to note that in my app, both 19.2 and 20.2 were running the same code. Output data is the same but t_20.2 = t_19.2 * 2.

Please find code example bellow.