LibRaw technical support

Stable LibRaw versions: technical support, errors, API questions

order of operations (matrix, white balance etc)

Hello

I'm experimenting with converting raw (Fuji RAF) files and im struggling a little bit to understand the order of how operations are done.

My expectation would be:

dcraw_emu -4 -r 1 1 1 1 -o 0 (raw) -> Camera2rgb matrix -> white balance mult -> srgb = good picture!

However, this results in an overly saturated image with blue colours going into negative values

so I tried a few other combos:

Forums: 

libraw wide char format support on MSYS2

Dear all,
I'm developing a software that uses libraw. This software is multi-platform and is able to run on GNU/Linux, OS X, FreeBSD and Windows through MSYS2.
Indeed, libraw is available on MSYS2 and that makes things easy. However there's a small issue that is kind of annoying: I cannot use the function

libraw_open_wfile

as I would like to do. For example with libtiff i use TIFFOpenW.

Indeed, in libraw.h this line:

Forums: 

LibRaw 0.19 Crashing DigiKam6 on macOS

Hi,
I have an issue with LibRaw 0.19 on macOS. I'm using DigiKam 6beta which now includes LibRaw 0.19 and this is crashing while scanning RAW (NEF) images from a Nikon D5300 12bit.
This is not happening with LibRaw 0.18.11 in an earlier build of DigiKam6beta

How can I help to track this bug down and get it fixed?

kind regards
Benjamin

Forums: 

Libraw 0.19 crashes on macOS if used in a background thread

Hi,

I use Libraw since some months in my app GraphicConverter 10 as optional RAW import.

I updated from the 0.18.x to version 0.19.
But the new version does crash if used in a background thread.

The crash occurs during initialization of the object:
LibRaw RawProcessor;

I attached a screenshot from the debugger.

Any help is appreciated.

Thorsten

Forums: 

libraw_memmgr crash with 0.19.0?

I've been using 0.18.7 fine for months, so today, I decided to try 0.19.0 Release.

Environment is macOS X Sierra, Xcode 8.2.1.

I've successfully compiled the code into a library object file and linked successfully with my macOS app (GUI app).

But when I create a new instance of LibRaw (LibRaw *rawProcessor = new LibRaw;), I got a crash on the following line in libraw_alloc.h:

libraw_memmgr(unsigned ee) : extra_bytes(ee)

What gives?

Forums: 

libraw.so needed

Hi,

I was installing rawtoaces utility on Centos 7 and was facing an issue. I installed the latest LibRaw-0.19.0.tar.gz, and it seems to be giving me an error saying libraw.so is needed. I can't find libraw.so in /usr/lib64/. Could you kindly let me know a workaround? Thanks in advance. PFA the error screenshot.

Forums: 

Error with Olympus .orf?

Loading an Olympus .orf file (this one: https://img.photographyblog.com/reviews/olympus_tg_5/sample_images/olymp...), the...

iProcessor.imgdata.other.desc

...field was set to a long string of many "O" characters; this seems unlikely, and I am not seeing those in a binary search of the file. Perhaps the field was not set (or cleared) on decode?

--Ben

Forums: 

Is the library built by LibRaw.sln thread-safe?

I wanna build LibRaw using LibRaw.sln provided in the downloaded source package, instead of the steps using nmake described here: https://www.libraw.org/docs/Install-LibRaw-eng.html. That webpage claims that "Only the thread-safe library is built under Win32", which implies that the output libraw.dll is thread-safe. So my question is: is the library built by LibRaw.sln still thread-safe?

My environment and settings:
- Windows 10 version 1803, 64bit
- Visual Studio 2015 Update 3
- Release x64 build

Forums: 

Pages

Subscribe to RSS - LibRaw technical support