I am new to LibRAW and I am wondering if the unpack() performance should be that slow. I am using LibRAW on a Windows 32-bit program and unpack()+dcraw_process() take around 20 seconds for a typical 6000x4000 image. I tried several RAW file formats: NEF, CR2, Sony, Olympus and all file load very slowly.
Then I took a look at FastRawViewer that is using LibRAW and (if I am right) do not display a JPEG preview, and it load the same RAW files in 1 second!
Alex, I've recently submitted the links to the problematic images.
For some reason, compressed images of 6768x4512 resolution fail with something like "unexpected end of file".
I'm using 201903 snapshot and having issues with certain DNG files in the RAW converting code we're using.
1) One of them has strong yellow colour cast.
It turns out, one of the elements in the embedded colour matrix array is being overridden due to other array being accessed incorrectly in identify() function dcraw_common.cpp, line 20728:
Raw photo decoder "dcraw" v9.28
by Dave Coffin, dcoffin a cybercom o net
Usage: dcraw [OPTION]... [FILE]...
-v Print verbose messages
-c Write image data to standard output
I'm using LibRaw to process RAW files on Windows. I'm using the March Snapshot built with Visual Studio 2017, 64-bit,
I'm having problems with EXIF orientation in several RAW files, mostly Canon CR2 files.
When the user enables the option to use the embedded preview in the CR2, my software uses the routines
unpack_thumb
dcraw_make_mem_thumb
to create an in-memory image and then I load that image into my image library for further processing. After loading the image my code checks the
I've got a two problems with the processing of an image from a Fuji X-T3.
1. It has a black border on the right hand side.
2. It takes about 40 seconds to process using: dcraw_emu -t 0 -4 -j -v -v "DSCF3954(X-Trans).RAF" which I think does three pass interpolation. By huge contrast Adobe Camera Raw 11.3 takes about two seconds even though the image is clearly interpolated (and quite well).
Recent comments