LibRaw technical support

Stable LibRaw versions: technical support, errors, API questions

Building libraw in debug mode on Mac

Submitted by dsi on

Hi,
I am not clear on how to build libraw in debug mode when using the configure script. I tried using CXXFLAGS=-g. But I noticed the .dSYM files were created in the libs directory with or without this.

The configure script itself has a -debug option but it appears to be related to debugging configure (atleast based on the comments) and not generating debug symbols.

Appreciate any help on this.

Dinesh

Forums: 

Where is RAW Image data stored and datatype

Submitted by SteveR on

I am working with another developer in creating a revised version of a popular astronomical application for analysing starlight.
Many users of the software use a variety of DSLR cameras to capture their scientific star images.
The key requirement, other than being able to handle a wide range of DSLR cameras, is that the data from the camera sensor MUST NOT have ANY processing done. We must only get the unaltered signal from each pixel without any processing of any kind (except what some DSLR cameras do themselves :)). Our software handles all processing of the RAW data.

Forums: 

New camera support

Submitted by The Narrowband ... on

Hello, my first post here. I have a new camera. It is an OM1 from OM systems. Just came out like a month ago and looks like its a big seller too. I am wondering if I can provide the developers here with any helpful info or files needed to get the RAW files from this camera supported by LibRaw. Especially since some of the software I use for astrophotography uses LibRaw.

Forums: 

image scaled to 65535 even with no_auto_bright

Submitted by zac on

I have two dng files taken with an iPhone under same setting and when opened from adobe's photoshop one image is saturated when the other clearly isn't. However when in libraw both images have maximum intensities at 65535.

Here's what I did in libraw. Is there something I did wrong?

1. open_file()
2. set params with no_auto_bright=1 and no_auto_scale=1
3. unpack()
4. dcraw_process()
5. get image with dcraw_make_mem_image()

Forums: 

Problems building libraw.dll

Submitted by jsachs on

In the absence of an updated libraw.dll in your recent releases on Github, I tried to recompile the sources to create it here. I was eventually able to set everything up and run nmake on Makefile.msvc and it appeared to run to completion, but the resulting libraw.dll is apparently 32-bit and not 64-bit as required. Your instructions do not explain how to modify Makefile.msvc to produce 64-bit dll and lib files.

Forums: 

cam_xyz array differs from exiv2 output on Sony A7C

Submitted by trougnouf on

Hello all,

I found that the cam_xyz array returned by libraw doesn't match the one I got in exiv2 after going through Adobe DNG converter. I don't know which one is right. (The two match on my older D3300 camera).

I've uploaded a sample image on https://drive.google.com/drive/folders/1tBty_PqV_3LzDBytnj7d5dbH_C66Vu3d...

The cam_xyz array can be obtained from libraw as follow:

(in python)

Forums: 

Kodak kodak_radc_load_raw function

Submitted by paulexchandler on

This function has a rather curious construct in it. There is a variable "int c" and there is:

         for (r=0; r <= !c; r++)

I believe many (most?) C compilers these days are going to result in an integer value of -1. So this for loop iterates once or zero times.

This is enclosed in a "FORC3" construct, which iterates c from 0 to 2.

Forums: 

Pages

Subscribe to RSS - LibRaw technical support