You can only visualize, not select it as target of your adjustment. You will in reality have to affect too much colors outside of your target. It’s not like in clut - one click to select what to affect and (more importantly) then one to select what not to affect (to easily limit the effect).
9 posts were split to a new topic: version 4.8: Max width for side panels
I believe that is usually a bit better. If you slide the nodes and then tweak the guided filter. it’s fairly precise. In CLUT picking a single color may be fine but pushing that will lead to artifact pretty quickly
Not in my experience, it’s a lot of tweaking and results are not acceptable…
I agree there are multiple controls and I tried a few times but I don’t yet fully know how to reel them in… with that curve based adjustment even in color zones you used to be able to bring it in tight for a fairly narrow range… I wouldn’t say I can yet manage that in the color eq as I guess that function fall on that guided filter but I am sure someone with some better understanding of the filter can hopefully demonstrate it…
9 posts were split to a new topic: White balance change: As Shot to Reference
Anyone else having problem with the Flathub package? I get:
Error: While pulling app/org.darktable.Darktable/x86_64/stable from remote flathub: opcode close: Corrupted file object; checksum expected='32a1a3776bb1fbf9b903cdc0c364a89d9caf368e0fa3b1297088dad464324be3' actual='bc15f3b624d65290716ab81daaabffb3d69954927d624e6758eb7c2ecbc681c9'
I filed an issue.
And got this reply:
update worked fine here. Nothing we can do anyway.
Would be very interested to hear if Flathub worked for anyone else or if it failed. Checksum fail. Could it be that I edited cameras.xml for current Flathub version (4.6) in /var/?
I installed it here on my mint 21.3 system, using flathub, no problem. Upon launch it updated the schema and I was all set.
1 Like
does it make sense to discuss a bunch of different issues in detail in thread of a post announcing a new release?
3 Likes
Yeah I split out a bunch of posts to new threads.
3 Likes
I know that the 4.8 docs are not out yet, but could someone point me to any temporary or in-progress doc on using the Color Equalizer module? Thanks.
I don’t think it has even been started yet.
I am currently writing the description of the use of color equalizer. This will take a little longer than I thought, as I have a lot to do at work at the moment.
But if there are any questions, I will be happy to help.
7 Likes
Thank you, @paperdigits and @s7habo .
I look at that scope pattern with what are apparently repeating diagonal stripes of hues and I really have no idea what it represents. And I have looked at the presets, but I still don’t have any idea what thoughts went into creating them.
Use your mouse and drag nodes up or down. That will shift the color (the hue, saturation, or brightness). A hue adjustment in a node at blue will make a blue shift closer to purple or to yellow.
Try it and then hit reset.
1 Like
I think the interface is quite similar to the old color zones.
For example, on the hue tab, you can shift a green towards blue or yellow. Line in the middle is the original hue, above and below it are the hues you can shift it to. Compare:
You can selectively change saturation similarly how the chroma adjustment worked in color zones: raise the control to increase, lower to reduce:
Finally, you can adjust brightness like lightness - raise to brighten, lower to darken:
4 Likes
You can click to reveal sliders in the UI in addition if that works… might be good for recipe or presets as you can dial-in numbers
1 Like
I’ll join in the appreciation of all the work done by the developers and those that contribute with documentation etc.
I really feel privileged to be able to use such a fantastic tool as dt.
Thanks to all!
1 Like
Hello. I probably missed something but could someone explain why 4.8. drops support for Monterey. I have of course read about the new policy since version 4.4. but Monterey is still officially maintained by Apple. So I don’t get it. Thank you.
