Stenis
(Sten-Åke Sändh (Sony, Win 11, PL 6, CO 16, PM Plus 6, XnView))
41
Well I will give two example her Wolfgang. Which is made with the Global Hue Color Wheel and which is made with the new Hue Mask-tool?
In my eyes absolutely all Hue Masking in Photolab is local. The only difference really between the Hue Mask and the old Global Color Wheel is that the first is displaying the mask and the second is not. The thing that makes the Hue Mask more of a local tool is that it is possible to delete the part of the mask you don´t want shall affect your image with the Hue Mask and the Local Eraser.
For me this is more of a semantic question really since as you can see both these tools are masking almost the same areas when I use the color picker in both cases to pick the yellow nuance on one of the shading clothes above the main business street in Nicosia Cyprus.
In order to make the “mask” visible in the Global Color Wheel I have added some green to make that invisible mask visible so we can compare them.
Make your move Wolfgang and all the rest, feel free to participate you too. Give me your answers and motivate your pick!
I´m glad DXO finally gave us a tool that is far more precise than the Color Wheel has been and that creates a mask that is open for adjustments. I just can´t understand though why they kept the Local Color Wheel, do you? I think the Local Color Wheel is just one more of these rests in the interface of “structural growth” problem. Hope they get rid of that in the next version
That is not quite true. At least in Windows one can click onto the color selection of the global Color Wheel, while holding down the Ctrl key. The selected color range stays visible and the rest is presented in B&W.
If you will, the Hue Mask “replaces” the missing picker in the local HSL tool. But you still need this local HSL tool, when changing Saturation and Vibrancy (unfortunately placed here) or Luminance and Uniformity related to these 8 different color range “presets”.
If it’s an ideal solution, I don’t think so, but that’s what we have now.
Just make the most of it.
Stenis
(Sten-Åke Sändh (Sony, Win 11, PL 6, CO 16, PM Plus 6, XnView))
43
Wolfgang, when I looked at that video I reacted over the big differences between the Mac and Windows interfaces. Some of that interfaces controls are just not there in the Windows-version. The Mac-version looks better from what I have seen.
Stenis
(Sten-Åke Sändh (Sony, Win 11, PL 6, CO 16, PM Plus 6, XnView))
44
Both uses a picker and both picks a color with that. I see no difference there at all and I´m pretty sure that if this function would have been implemented in the old Control Point inteface it would have got the same Control Point interface as the others in order to work consistently with the old interface that from the beginning did not have the layer interface as it has now. Now we delete the layers instead for looking after control points.
That solution in the Global Color Wheel is a poor substitute compared to how the Hue Mask is working where the mask is activated by default. That interface makes it possible for adjustments while you need to point to and click and hold on the color wheel selection which prevents you from doing anything else. With the Hue Picker it is far more useful. Why not doing like in Capture One where it is just to hit the “M”-key for toggling the mask on and off. This is a really poor solution in my eyes.
Stenis
(Sten-Åke Sändh (Sony, Win 11, PL 6, CO 16, PM Plus 6, XnView))
45
That is just an example of how stupid that design is. They could have added those sliders direct under the Hue Mask Options - but they didn´t. They just should to have got rid of the Local Color Wheel becuse now we see a redundancy that is just confusing. I´m preddy sure that Local Color Wheel will be gone in the next major upgrade. Remember who told you that Wolfgang
As you see the rest of the Local Color Wheels controls are already there aren´t they? We will also need the outher part of the Control Wheel where we can change the picked color to something else than it is.
Yes - that was a significant blunder in my opinion … Done, I reckon, just to rationalise/simplify some internal code - but, to the detriment of usability.
@Stenis – Instead of continuing to argue, experiment to find what is useful to you, and if you don’t like (need) a tool, don’t use it (just like with software).
If you look at other software than Lightroom and Photolab, you’d see it’s quite the opposite and makes everything easier. By default, all tools are global, but give you the option to be applied locally using masks. It simplifies the user interface, but is more powerful.
Maybe instead of removing, combining would be the better word. Either way, you’d have only one interface for both global and local adjustments, instead of two.
3 Likes
Stenis
(Sten-Åke Sändh (Sony, Win 11, PL 6, CO 16, PM Plus 6, XnView))
56
I guess you are old enough to remember what happened with some Windows application interfaces already in the nineties. At that time we often had to push three buttons at the same time to execute a command. That made Microsoft inplement the then new ribbon-system.
Intuitive none cluttered interfaces without a lot of overlapping are just more effective than the opposite. From time to time software companies decides to make a fresh start and if not before then they use to get rid of all that old junk nobody uses anymore. Even Optics Pro / Photolab has gone through such a transition before and it seems to be time for a new face lift again because that local Color Wheel is really obsolete.
Itoo have been using IMatch for some 15 years. Best DAM I’ve seen. Tremendous user configurations. DxO can never catch up on their DAM. Best thing though, is that the 2 software integrate well
Aubrey
I was not able to fix it in x2s with adjusted setting. It is at the edge of the lens, but deepprime result is fine without visible banding in the result.
Otherwise loupe is very helpful, luminance curve in the tone curve is a dramatic improvement, when you need to fix shadow highlights - this should be integrated years ago.
There was a similar case lately when shadows were pushed up heavily. Probably you used SelTones Blacks and/or SmartLighting for shadow recovery. Both add strong edge microcontrast, which combined with XD2s may lead to posterization. This happens only in extreme cases. DP leaves some noise behind, so the microcontrast does not produce posterization (that badly). To fix the problem, use the ToneCurve for very deep shadow recovery. See Visible Posterization in PL8, in Bokeh Areas (there’s a ToneCurve preset there which you may adapt to your case) and Selective tone versus Tone curve .
To put it short: probably it’s not an issue with XD2s but with microcontrast in Blacks and SmartLighting. XD2s just makes it possible.
thx, i will try to fix it this way.
my point is that the old deepprime does not show this banding. they could adjust xd2s in a way there is no such banding :-D.
iso 4000 on uncompressed raw from a7iii - i do not thing it is pushed so much.
update: you are right, i have smart lightning on slight. disabling it removed the banding from the night sky.
