Hi Alex,

Thanks for your reply.

This is the first time I have built the LibRaw library and I directly built it from the 201910 snapshot. I don't think I have a outdated libraw.so issue.

-- Siddaharth Suman

Hello,

Is it planned to port more recent version of libraw library to Android?

Thanks

If you use ./configure script to build libraw, use --disable-lcms to disable lcms auto-detection.

Alternatively you can use make -f Makefile.dist, LCMS section is disabled (commented out) by default.

unpack_thumb() provides largest available thumbnail/preview/whatever-it-called.

Haha oh man, thanks for the answer!

I'm stupid, I just wanted it to be done and didn't look right at my garbage.
I fixed the code and the Whitebalance probleme disapeared.

But unfortunaly I ran into another problem.
The red colors seems to be shifted, so brown colors appears bluish.
Also blue seems to become orange.

Here is the correct image as jpg Converted from Photoshop
http://neuland.wtf/img/correct.jpg
and the source Raw file:
http://neuland.wtf/img/srcraw.CR3

I tried to play with the settings in Rawprocessor->imgdata.params, but couldn't figure it out.
My code looks now something like this (not production code):

int LoadRaw(char *charBuffer, int size)
{
	RawProcessor->open_file(charBuffer);
 
	// Result if enabled : http://neuland.wtf/img/camera_wb.jpeg
	RawProcessor->imgdata.params.use_camera_wb = 0;
 
	// Result if enabled: http://neuland.wtf/img/auto_wb.jpeg
  	RawProcessor->imgdata.params.use_auto_wb = 1;
 
  	RawProcessor->unpack();
  	RawProcessor->dcraw_process();
}

It is hard to discuss such kind of problem without having raw file sample on hands.

LibRaw is not able to write raw files.

Thank you for your reply!

I thought that at least there should be some specs about the DNG file format. The SDK is great!
This might help me a bit.

But the thing I really need is NEF editing. If anyone has any hints please tell :-)
I found rawpy which uses libraw and reads NEF files. Loads the undemosaiced raw data.
Only thing missing now is a way to overwrite the file.

Follow-up:
After looking at how the code fails in my app, it appears that:

this method is returning an object, but the `data_size` property is 0 (zero).
I guess it is possible that the call to dcraw_process also failed.
I'm going to go back to the debugger and ensure valid data is being presented - I will update when I have confirmed one way or the other.

If, on top of this, you also need accurate color reproduction, an alternative approach would be to construct a DNG from your raw bytestream, e.g. in 2 steps:
1) see e.g. rawtopgm from netpbm tools, or use ImageMagick/GraphicsMagick raw 'GRAY' format to convert to a widely known and simple PGM
2) use http://a1ex.magiclantern.fm/bleeding-edge/pgm2dng.c (adjust metadata accordingly in the source or using e.g. exiftool afterwards); see also https://github.com/fastvideo/pgm2dng

However, you'd need some (not so trivial) sensor characterization work to be able to fill the DNG metadata (basically build your own DCP). LibRaw would need this information anyway even if you went with the open_bayer() route and want more accurate color reproduction. The upside of the DNG route is that you can use many more processors/libraries in the future.

if your image is 'raw dump' (so just bytes from sensor), LibRaw::open_bayer is for you.

It is not well documented, use samples/openbayer_sample.cpp and Changelog.txt as a reference