Selective Tone / Highlights too "broad"

[Willy1]

“Looks heavily over-sharpened, like an auto-HDR image from an iPhone (as an iPhone 11 Pro owner, I’m very familiar with iPhone photo files).”
Exact, that is what I had always in mind but couldn’t place. Btw, I didn’t it sharpen, it is C1 standardly.
Kind regards,
Willy

[John-M (Melbourne, Australia - Win10)]

@Willy1

I use Adobe RGB and yours is in sRGB, so compare is not easy.

That shouldn’t be a problem - as PL’s workspace is AdobeRGB, regardless … and choice of Adobe RGB or sRGB applies only to the exported result … Right, @platypus ?

John M

[OXiDant (Peter)]

i think that the warningcolors are set to preferred colorspace.(otherwise you casefuly tune down just inside AdobeRGB (to get rid to the warning colors) and then compres again (but now automated) with export to sRGB. (sounds logic but i have to check not sure)
PL’s maximum workspace is AdobeRGB at this moment that is for sure.

[Willy1]

No, John, that is not the case. My display is callibrated Adobe RGB, the export is Adobe RGB. This image looks fine in the PL viewer 37%, but when expands to 100% it becomes sRGB, like the output. ??? Curious!

Willy

[IanS]

While I have previously agreed with the advantage of U-Point selections over C1 masks the addition of the Magic Brush & Eraser changes everything, particularly as they are working within a far more sophisticated local adjustment UI.

The Magic Brush & Eraser effectively do what the U-Points do except better. Hopefully, DXO can integrate the advantages of C1’s Magic Brush & Eraser to give enhanced U-Point performance to the benefit of all users. That’s why competition is good for the industry.

[platypus (Canon & Mac (Intel and M1))]

@John-M

PL’s workspace is AdobeRGB, regardless … and choice of Adobe RGB or sRGB applies only to the exported result … Right, @platypus ?

…this is what DxO has to say about how PhotoLab handles colour spaces:

DXO on calibrated screen EIZO

Hi @mujabad. Happy new year and sorry for not answering during the holidays. If the input image is a RAW image, independently of the color space you selected in your camera, the raw input colors are neither in AdobeRGB nor in sRGB, but in the native color space of the sensor of your camera. In that case, PhotoLab converts the sensor colors to AdobeRGB and uses that as working color space. This cannot be configured. During export, you can choose between “as shot” (which converts to the color sp…

[George]

And when viewing with the right software it’s converted to the monitor’s color space.

@Willy1

No, John, that is not the case. My display is callibrated Adobe RGB, the export is Adobe RGB. This image looks fine in the PL viewer 37%, but when expands to 100% it becomes sRGB, like the output. ??? Curious!

Does that happen when passing the 70%?

George

[Willy1]

George, when expanded to 50% the color stays, but at 70% it becomes sRGB. The output in Fast Stone Image viewer is sRGB (on a callibrated Adobe RGB screen).

Willy

[George]

No, I don’t think it’s RGB, it’s the behaviour of PL. Rely on the 100%, above 70%.
How can you tell what color space is used? What you see is the monitor’s color space.

George

[Willy1]

My monitor Eizo is a Adobe RGB callibrated monitor. Nothing wrong with it. What is wrong is the dopfile of the above corrected RAW image by Joanna. She has something ‘been up to’ with it.

[George]

Her dop file is based on your first image, a JPG.
The problem is not your monitor and not that color space is changing while viewing. If you see the difference when passing the 70% boarder it’s just PL.

By the way, I don’t see any color changing on my monitor. Just sharpness.

George

[Willy1]

The first image is based on RAW file X0A8304CR2 + dop file sc. the corrections of Joanna. This first image is sRGB. See above.
When I take this dop file and join it with my RAW file in PL then the outcome is also sRGB. I cannot change it. Do I something wrong?

Willy

[George]

you can’t move the dopfile to another image.

george

[Wolfgang ([ Win10, PL+VP+FP, Nik6 (+3) ])]

Hi Willy,
I played with your raw-file and adjusted brightness and contrast with DxO SmartLighting Spot Weighted
VC1 → _X0A8304.CR2.dop (18,7 KB), but don’t see any colour changes within PL5 while zooming.

note – I didn’t use Selective Tone / Highlights

---

Then I exported VC1 as jpg in Original, AdobeRGB and sRGB colour space.

• Only the last one is reported as sRGB and the traffic sign along the road at the right hand side appears with somewhat dimmed red, when compared to the other two.
  [ Eizo CG2730 + FastPictureViewer set to AdobeRGB]

• When screen and viewer are both set to sRGB, I can’t see that difference.

---

By comparison, in the unaltered raw-file (M) that red looks darker
(the same with Faststone Image Viewer).

Wolfgang

[Willy1]

It is the same but duplicated RAW file Joanna used. I have yet the same corrections one after another applied to the original RAW file and the result is an image in correct Adobe RGB.

George thank you for your help.

Willy

[Willy1]

This is my result (Adobe RGB). Thanks all.

Willy

[m9k]

So; in Photolab Highlight slider in Selective Tone tool also affects midtones. I don’t get it and I never will. I think one of developers screwed those sliders and now he does not want to repair them. Whatever.

In LR and Capture One Highlights slider only affects highlights.
They say: don’t use Selective Tone sliders; use Local adjustments in Photolab.
The problem is … in Local Adjustments highlights slider behaves the same way – it also affects midtones.

[George]

Belgium? Overweg 159

George

[Willy1]

George, je zou wel een Belg kunnen zijn, haha! Die zijn overigens wel aardig hoor.
NL Arnhem-Zevenaar-(Emmerich). Overweg de Methen km 104.7.
Groet,
Willy

[George]

Ik ken dat bord alleen als waarschuwing voor drempels in de weg. Ik zie alleen een spoorwegovergang.

George