Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incorrect 'camera_whitebalance' matrix #251

Open
StudioPetrikas opened this issue Dec 9, 2024 · 0 comments
Open

Incorrect 'camera_whitebalance' matrix #251

StudioPetrikas opened this issue Dec 9, 2024 · 0 comments

Comments

@StudioPetrikas
Copy link

Hello and thank you once again for your excellent work.

Issue:

camera_whitebalance returns [0, 1, 0], when As Shot White XY is used in the EXIF (instead of a more common As Shot Neutral)

Usually, when the WB is presented in a different manner, camera_whitebalance returns [0, 0, 0]

However, when processing is done with use_camera_wb = True the output image is balanced to "As Shot" properly, which mean that libraw or rawpy does calculate it OK somewhere, somehow.

Extra info:

I am trying to implement a different highlight-recovery method than the ones provided by libraw. Which means I need to work on un-scaled, un-balanced, un-matrix'ed values, which, after recovery, I have to re-scale, re-balance and re-matrix.

rawpy provides enough information from 90% of the files I've tested. Except for the ones that have White Balance provided as 'As Shot White XY'.

In the end it means that I'm not able to 'camera-balance' the files myself, since I only get access to daylight_whitebalance and color_matrix which can only get me to D65.

If you need a test-file, please let me know, I'll ask for permission to share it.

Thank you very much in advance. If you need any additional information please let me know.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant