LibRaw technical support

Stable LibRaw versions: technical support, errors, API questions

Libraw 0.19 crashes on macOS if used in a background thread

Submitted by lemkesoft on

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?

Submitted by Kuro on

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

Submitted by spatre on

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?

Submitted by fyngyrz on

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?

Submitted by zzzhhh on

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: 

using example, image data not understood

Submitted by fyngyrz on

Reading a CR2 canon file from a Canon 6D MK1, known good. Using the example code on the "https://www.libraw.org/docs/API-overview.html" page; the max value out of any RGBG sample is about 5600. Scaling the data up ((data/5600.0)*65535) to a full 16bit sample results in what looks like fairly even tempered noise, not anything like the image data that is actually in the file.

I want to read out the RGB values of the image, and this doesn't seem to do that:

Forums: 

Using LibRaw.sln to build to support FujiFilm GFX 50S

Submitted by johnbuuck on

I am using LibRaw.sln to build LibRaw but can't figure out what I need to change in order to support the new FujiFilm GFX 50S camera. I tried adding the Preprocessor define LIBRAW_OPENMP but that did not work - I get " Cannot unpack C:\CameraFilesTests\IN\Canon\MM8717_170913_08471.RAF: Input/output error"

Forums: 

Pages

Subscribe to RSS - LibRaw technical support