Many thanks, I find them very useful.
I may try to do a summary but there are a lot of moving parts to this. First, the vectorscope is using Jzczhz, and secondly I am not sure if it is handling values in a way that the other scopes were or maybe still are. Because the data goes form working profile to display profile to histogram profile you need to set your display profile = to your working and histogram profile to be sure the data is not clipped when it is mapped in the smaller display profile. This should be branched so that working goes strait to histogram which is where the picker data comes from and not through display and I think this is being looked at but I think it is still an issue. In any case using the vector scope in conjunction with picker values to make calibration adjustments might need care. I was hoping to evaluate the 6 primary color in the spyderchecker24 with the vector scope and look at them before and after colorchecker calibration in CC module and then after making targeted changes to each using the rgb colorbalance module masked for each patch. Initially I just rotated each so the sample of the patch aligned to the color locus on the hue ring. This is similar to what you see people do in Davinci with a hue vs hue curve. The colors did not look quite right. So instead I changed the picker to HSL and used the instances of rgb CB for each patch mostly with hue rotation but also with global sat ,chroma and luma to dial in the HSL values as close as I could to those given by Datacolor. This looked the best to eye when I compared it to the actual color chart but I have no idea if it could be used on other images. This was all done without filmic turned on…turning it on seems to shift things a bit depending on the color preservation mode…In any case I am not sure about the actual relationship of the picker values to what is displayed in the vector scope. Maybe I will try to organize all this fiddling around and post if it proves to have any merit…
2 Likes
Thank you! Very nice presets.
Thank you!!
This doesn’t seem to to work in 4.2. The presets are grayed out in the module. Probably because the color science for the module got upgraded (at 4.0?)? Has anybody updated the presets to work with later versions of dt?
Thank you for the share
4.2.0 works fine for me. Use the presets very often.
I installed them in the past but they work well in 4.2 for me.
I’ve the same problem.
In the *.dtpresets file I find: </op_params><op_version>4</op_version>
In my own *.dtpresets file I find: </op_params><op_version>5</op_version>
I figured this was just to make sure old edits work in new versions. Is it a bug in darktable (4.2)?
Yes:
- Install dt 3.8 on another machine
- Install the presets
- Update to 4.2
- Export the presets
- Import them in 4.2 on my main machine
I would make them available here, but I am not the author.
I am on darktable 4.2 (archlinux). After import the presets were grayed out. I restarted darktable and the presets work fine.
I use Darktable 4.2.0 and these presets work for me, but only after restarting DT.
Yes I can confirm that.
(Why didn’t I think of that sooner 
. Ok, I’m just not a typical Windows user.)
I will share updated presets, but I am currently away from home, please wait a few days
4 Likes
Thank you @MarcoNex I use your presets all the time since you published them for the first time.
Can you give a short explanation on why you excluded and separated the lower cromaticity levels into the preset 9? Is there a special use case for that?
Kind regards
Roland
Well, I took inspiration from Color Editor in Capture One, which is the SW I used before DT.
As you can see by default when you pick a color, the low chromaticity areas are excluded.
Moreover, I had color grading in mind, that is basically shifting colors and more often than not you want neutral hues to remain neutral.
But feel free to change that, it’s pretty easy.
1 Like