DxO has moved the “Vibrancy” and “Saturation” feature from the general color pallet to the “HSL” feature. In my personal oppinion it was an advantage to have “Vibrancy” and “Saturation” as separte features at the color pallet.
What do you think? Should we complain via support ticket and wish to bring it back to the “color” pallet?
“Vibrancy” was always a part of my personal pallet which contains only features I need. With PL8 I had to implement the entire HSL pallet into the personal pallet which is overkill and consumes space on the screen.
2 Likes
This change has been vigorously opposed but DxO refuse to even acknowledge the major issues it causes.
I have voted as I still hope for the return to its rightful place in the main palette.
3 Likes
I’m in the “vigorously opposed” camp too … and have added my vote.
3 Likes
You can also click & hold the global channel (icon) to temporarily disable it…
or
Create a ‘global local adjustment layer’ and only apply vibrancy/saturation there if this separation is critical for you workflow.
True - but that’s not the point, Ian.
With this change to the UI it’s no longer possible to evaluate the impact of any individual colour channel without “contamination” from the global/white channel.
For example (using the click-&-hold method);
- I can evaluate the impact of Vib & Sat settings (via the global/white channel)
- I can evaluate the impact of changes to any of the individual colour channels ALONG WITH the impact of Vib & Sat settings.
- BUT, I cannot avoid contamination of Vib & Sat settings when evaluating the impact of changes to any of the individual colour channels
3 Likes