Hi,
I have a question regarding these two images:
https://drive.google.com/file/d/1FZDh3jiw-85sJy3qJUh-xL4E5fA1mEfV/view?u...
https://drive.google.com/file/d/1GWI7D2sY2VcZrlFASAzkSklQl7vJ0qYn/view?u...
These are Sony YCbCr images, shot at the same camera white balance. I see they have
imgdata.color.as_shot_wb_applied = 33 (LIBRAW_ASWB_APPLIED | LIBRAW_ASWB_SONY)
I would like to develop these files identically (for panoramic stitching)
out.no_auto_bright = 1; // -W
out.use_camera_wb = 1; // -w
I've also verified that out_cam and scale_mul are identical for both. So I think they are converted identically.
But they come out with different colors after dcraw_process(). I've opened them in RawDigger and see the same issue: one of the images is a bit warmer than the other.
From what I understand, the WB has been premultiplied by the camera, so this would be outside LibRaw's control. But the strange thing is: Adobe Camera Raw does develop them with identical tint as expected.
So I wonder, could it be that the camera is premultiplying with different wb, perhaps the measured scene AWB, instead of the chosen fixed WB preset? Any help is welcome.
Thanks
Joost
What exact RawDigger version
What exact RawDigger version you use for your testing (Windows: Menu - Help - About; Mac - Menu - RawDigger - About)
-- Alex Tutubalin @LibRaw LLC
I'm using the latest
I'm using the latest RawDigger, 1.4.9 Release Build 821 (ARM64).
Here are 2 screenshots from Adobe camera raw, showing identical colors when using 'As Shot':
https://drive.google.com/file/d/1GhtJUCtIGRBP4FbReq2Jdk5vvPpoKy8X/view?u...
https://drive.google.com/file/d/1skhE7-up6nEWymxM9JShH10mO4ucm3ZL/view?u...
Could you please check with
Could you please check with RawDigger 1.4.10 beta: https://www.rawdigger.com/news/rawdigger-1-4-10-beta
-- Alex Tutubalin @LibRaw LLC
Ah yes, the problem is fixed!
Ah yes, the problem is fixed!
Will this be fixed in LibRaw? I guess I'll have to wait for the next public snapshot?
Thanks
Joost
Not sure it will be available
Not sure it will be available in the next snapshot, sorry.
-- Alex Tutubalin @LibRaw LLC