Call for white balance finetuning samples

Panasonic DMC-GX7
darktable-whitebalance-20200404.tar.bz2 (782 Bytes)

Thanks!
Do you need more Panasonic? Let me know.

1 Like

Hey @thokster! Welcome to pixls.us community!

No need, that’s fine for now :slight_smile: Panasonic cameras now confirmed to work flawlessly!

Now I just need more Samsung/Olympus and others samples :slight_smile:

1 Like

I have three different Oly’s:
Olympus-EM1-Mark1.txt (3.5 KB) Olympus_E-PL6.txt (3.5 KB) Olympus-TG5.txt (3.5 KB)

1 Like

Thanks @wiegemalt !

It seems that your "Olympus-EM1-Mark1.txt file is an archive containing Olympus_E-PL5.txt and Olympus-TG5.txt files.

I’ve fixed some bits thanks to this and now Olympus is confirmed to fully working!

Needs more Samsung/others :slight_smile:

1 Like

Samsung NX1
darktable-whitebalance-20200405.tar.bz2 (535 Bytes)

1 Like

Thanks @torebu

It seems like Samsung has reverse situation than Fuji - meaning produces proper WB data but does not indicate finetuning.

Can you DM me those RAW files so I can check them locally? And tell me what exact WB preset you’ve used, because it seems like camera is insisting it was “Manual”

On fuji xt20, here is what I have related to wb doing the diff (with exiftool 11.93):

< White Balance Fine Tune         : Red +0, Blue -180
---
> White Balance Fine Tune         : Red +0, Blue -160

and

< WB GRB Levels Auto              : 302 563 547
---
> WB GRB Levels Auto              : 302 559 552
1 Like

fixed it.

1 Like

Thanks @rawfiner and @wiegemalt

It’s now confirmed for me - Fuji doesn’t put wb fineadjusted coefficients in exif file :confused: can you send me 3 raws with same image content, same wb preset but fineadjustment as in post #1? (-9, -8, 0)? I want to see if decoded raws are different or “as shot” wb differs…

@wiegemalt - thanks! Olympus is now confirmed to working fully :slight_smile:
Currently in darktable Olympus cameras you have have following WB presets levels:
EM-1 Mark1: Only non-finetuned, not including Kelvin presets
E-PL1: Interpolated finetuned
TG-5: doesn’t have white balance presets

Would you like to do shots with finetuning and contribute them to darktable?

Finally:
Thank you all for the samples!
All your work and samples were taken into account when doing PR 4575 and darktable’s new camera support wiki page and especially the one asking for white balance presets

I just added those Camera support and White balance presets links to the r/darktable FAQ file on reddit.

1 Like

Sure, what exactly do you need additionally?

1 Like

@johnny-bit:

Full Nikon D750 Fluorescent set is PM-ed to you.

1 Like

@johnny-bit:

As promised, here is the outcome of the requested test for

Olympus OMD EM5 MKII (used “cloudy” to fine-tune)
darktable-whitebalance-20200407.tar.bz2 (671 Bytes)

Cheers
Axel

1 Like

Full D7000 set PMed to you.

1 Like

And, as promised, here comes the complete set for the Olympus EM-5 MKII

darktable-whitebalance-20200414.tar.gz (5,0 KB)

1 Like

Hi everyone.

Sorry to bump up this thread.

But just get my new camera and try to help opensource software, so trying to do this white balance by following White balance presets · darktable-org/darktable Wiki · GitHub and this thread.

But I’m still confuse…my camera is a Fuji, so the fine tune is like this image

So should I go from horizontal line (R: -9: B: 0 to R:9 B: 0) diagonal up (R:- 9, B :-9 to R: 9 B: 9) diagonal down (R:-9, B: 9 to R: 9 B: -9) or the whole square (200 shots…!!!)

Hi,

Unfortunately fuji does not produce usable finetuning info. Your only option is to just create presets without finetuning. If you did finetuning here’s the message you’d receive from extract_wb tool:

Warning: Fuji does not seem to produce any sensible data for finetuning! If all finetuned values are identical, use one with no finetuning (0)

This is explained in White balance presets · darktable-org/darktable Wiki · GitHub article, but thanks to various manufacturers variably vary interface it’s not as straightforward as it should be…

So in case of fuji, if they ever decide to actually put finetuning info in exif data, the correct axis is: vertical horizontally centered.

As you can see o top in vertical it’s blue and bottom on vertical is warm-ish yellow-orange. That’s amber-blue axis.

Horizontal line is from green to weirdo pink in your example and it’s the one we don’t want (magenta-green)

Well…it doesn´t I try with a bunch of files (event with the wrong selection of finetune, I was doing horizontal change) it produce a tar.gz with files .txt.

Are you sure ? Because the problem (maybe it’s because my english suck) but if I go vertically, center horizontally I will go from (R:0 : B: -9 to R:0 B:9) and for me R stand for «red» (close to Amber) and B stand for «blue».

So can you just confirm it’s really what you need (R:0 B:-9 to R:0 B:9) without any change on R.

The tool producing .tar.gz files is extract_wb_from_images.sh, this just extracts exif data to txt files so you can send it as a package to darktable devs who’ll ran extract_wb.py on them… It’s as simple as possible and makes no detection of fuji fun times. It’s extract_wb.py that does the heavy lifting and complaining about fuji not having normal data :slight_smile:

Yeah, I’m pretty sure. I wrote the thing :stuck_out_tongue:
And I can bet that there won’t be proper finetuning data in exif output from fuji files, but I’d be happy to be mistaken :slight_smile:

Hi @johnny-bit .

So you’re right, fuji doesn’t change anything. I just try both fine tune and lazy. And yes in the fine tune no data.

I will try the lazy mode

Z

1 Like