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

WB Canon EOS D30 (Raw files) #7366

Closed
PeterWem opened this issue Dec 19, 2020 · 10 comments
Closed

WB Canon EOS D30 (Raw files) #7366

PeterWem opened this issue Dec 19, 2020 · 10 comments
Assignees
Labels
scope: camera support adding WB and raw support for new cameras

Comments

@PeterWem
Copy link
Contributor

I tried to generate the WB with extract_wb_from_images.sh. Channel multipliers were not included this time. Is it possible to extract them from the raw files at all?
D30.zip

@johnny-bit
Copy link
Member

Wow, that's nice old piece of DSLR :)

Unfortunately in RAWs you pasted... Well, while there MIGHT be wb data, it certainly is not in a format that's recognizable. All I can see is eg that file CRW_6972.CRW has "daylight" white balance, but in no tags is there recognizable WB coeffs data. Maybe there's something in Canon Color Info 2 tag, but it has waaay too much datapoints.

So ultimately IMO there's no way to generate WB profiles from raws using extract_wb* scripts... however... you can always import all images into darktable and then read coeffs in wb using "as shot" (if you manually specify preset WB as shot will have that wb coeffs) and then created wb presets by hand.

@PeterWem
Copy link
Contributor Author

With dcraw -v I got the following for all files:

multipliers 2.093285 1.000000 1.055975 1.000000

That is the same as in darktable (camera - neutral). Works great for daylight.

@johnny-bit
Copy link
Member

This is problematic bacause the CRW_6972.CRW is "Daylight" and CRW_6973.CRW is "Cloudy". darktable correctly identifies multipliers in "as shot" mode for those files.

If you wish I can produce "handmade" wb presets for that camera then, but I'd need you to shoot color target for me then. So - similar setup as the files you've sent, just shoot color target please :)

@PeterWem
Copy link
Contributor Author

Thanks! Should I buy X-Rite Color Checker Passport 2 or from Wolf Faust?

@johnny-bit
Copy link
Member

any Datacolor SpyderCHECKR family or X-Rite Color Checker family is fine.

If you don't have one and plan to use one I recommend Datacolor Spyder ones - i have SpyderCHECKR 24 and plan to get 48 one (passport). X-Rite ones here are like 2x the cost of Datacolor ones ;)

But don't get one just for this shot - if you don't have color checker and just want to use it one time to get EOS D30 WB it's better if you simply do a shot of anything non-moving so i can check if multipliers are ok ;) or just rent color checker for 1 day (it's like $2 here, or even free if you shoot the checker with your own equipment inside the rent shop studio)

@PeterWem
Copy link
Contributor Author

A spydercheckr it will be.

@johnny-bit johnny-bit self-assigned this Dec 21, 2020
@johnny-bit johnny-bit added the scope: camera support adding WB and raw support for new cameras label Dec 21, 2020
@PeterWem
Copy link
Contributor Author

Does this work?
D30-Spydercheckr.zip

@johnny-bit
Copy link
Member

First glance looks OK. I'll try to see whether I can get anything out of there.

@PeterWem
Copy link
Contributor Author

PeterWem commented Dec 26, 2020

It seems LibRaw corrected wrong white balance from D30 this year. I will check tonight if I can find it again.
Edit: No luck with LibRaw.

@LebedevRI LebedevRI self-assigned this Dec 26, 2020
@LebedevRI
Copy link
Member

As far as i can tell, rawspeed is currently always reading the auto wb temperature, not the selected temperature.
So i won't look into that any further

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
scope: camera support adding WB and raw support for new cameras
Projects
Status: Resolved
Development

No branches or pull requests

3 participants