Strange halo edge caused by Colour Calibration module

Hi all,

I was noticing a harsh white halo edge to my images, and after turning modules off and on, I discovered the Colour Calibration module is the culprit. Which surprised me.

I dearly want to keep using the CC module, so, what can I do?

Attachments show a magnified view where the edge disappears after turning off CC. Final attachment shows no sign of the edge using Sony Edit.

Att1: CC turned on with my custom Macbeth card calibration, shows halo edge

===

Att2: CC turned off, halo edge is gone

===

Att3: CC turned back on but set to ā€œas shot in cameraā€, halo edge returns

===

Att4: image opened in Sony Edit software, no halo edge

thanks

PS although the file used in DT is a DNG conversion from ARW, and the Sony Edit file is ARW, this is not related: I went back and opened the ARW in DT and the halo edge is exactly the same.

I’m not sure if the halo is really gone after deactivating CC. It just seems hardly visible since the surrounding sky is more white than blue. I think sharpen, d&s, tone-eq and local contrast are more the typical suspects.

But if you want usefull answers, share the raw and your xmp.

2 Likes

Sorry, but as far as I can see, the edge is still there, even after turning off colour calibration. It’s just much harder to see against the pale blue of the sky, compared to the version with CC.

I suspect the ā€œsharpenā€ module to be the culprit, looking at the history stack.

2 Likes

I vote tone eq or contrast eq… try bumping up the edge slider a little. Not on my PC will edit later with the name . Almost positive this will fix it… or use a different norm for the mask. I like RGB sum or geometric mean.

Doesn’t this just change the way the brightness of the image is calculated and has no impact on any effect of the tone-eq? Given of course you set the mask compensation correctly. I think diffusion, smoothing and feathering may be more relevant in this case. They are probably set near to zero.

I am no expert. I usually use the defaults but Boris often uses the geometric mean and rgb sum seems to give a more contrasted results… I am with you when I see a halo in the tone eq usually a small bump in the feathering works nicely and if not enough then setting diffusion to around 3 or so also helps…those are the main two that I use in addtion to the compensation when using the tool…

Here is the raw ARW and xmp.
https://drive.google.com/file/d/16dgz8Mi6ODE_8V5tcwBwGvsGGY4G6taW/view?usp=share_link
https://drive.google.com/file/d/1Ns33DvVkauHzK-IjD_tA8n59c4b4q9Ni/view?usp=share_link

Turning off sharpen, d&s, tone eq and local contrast doesn’t help.

It is completely absent from the Sony Edit image. Another Sony Edit sample attached with more saturation, to show it is not ā€˜hiding’ in the light sky of my first Sony Edit sample.

Yes I see what you are saying: my custom colour Macbeth calibration remaps the sky to much more blue, but doesn’t remap the edge so much, so it is a colour change that forms the edge.

However, I am also noticing Exposure is contributing: if I leave Color Calibration on, but drop exposure, the edge disappears. And yet no channels are clipping along the edge.

I can make the edge disappear within Exposure by changing the blend mode from Normal to Harmonic. Does that help to explain the true cause?

Explaining it is all well and good, but what I don’t like is that I simply do a correct colour calibration, adjust exposure reasonably without causing clipping, apply default Local Contrast and Sharpening (it is definitely NOT sharpening halo)… and I get this unattractive artefact. IMHO that shouldn’t happen.

cheers

Maybe filmic rgb is involved? Does it go away if you turn the module off entirely, or switch the preserve chrominance option to a different setting or disable it?

1 Like

I can’t really tell yet what is introducing that stuff, but it seems to be boosted by sharpening and mainly by filmic max rgb setting.

I can reduce it by setting filmic to luminance Y, lowering the sky in tone eq and use d&s for sharpening instead of sharpen.

00_A7R8492.ARW.xmp (9.8 KB)

Maybe it’s some sort of chromatic aberrations, that the other software just can correct better? :man_shrugging:

2 Likes

I think so …if you look at your color calibration which you are also using as a channel mixer a small amount more or setting blue channel in red output to zero removes the halo… its just a confluence of settings along that edge…

I’m sure tweaking one or two of the other sliders might also modify this…but then even with the change I suggest you might not have the sky colour you want…

@paolod @apostel338 @priort …you seem to be onto something, ā€œit’s just a confluence of settingsā€, particularly Preserve Chrominance in filmic rgb.

It does bug me a bit, because those are the default settings. And I don’t really want to lose the colour correction I have made with a Macbeth chart. (Having said that, I had better check what filmic rgb was set to when I made my colour correction presets – it was probably off!)

many thanks for help so far,

Also the highlights brilliance setting creates the haloed edge which can be reduced by reducing only that so there are a few small spots here and there that aggravate that edge…

1 Like

Since filmic rgb is downstream of color calibration in the pipeline, I don’t think it would have any effect at all on the correction presets that were made in color calibration.

I noticed that you left filmic on the defaults…that can be an issue for highlights and things like this… you should at least try the auto settings they are pretty good for the most part something as simple as a bit more white relative can often impact things a lot…

Yes. But using exposure and then some contrast setting to get the brightness right leads to the same result.

The chromatic aberrations module doesn’t seem to handle them. But raw chromatic aberrations does quite a good job here.

grafik

grafik

2 Likes

Wow. I didn’t even know that was a thing. Good spotting.

Do you see any reason not to turn that on for my default import style?

Well… the unfunny thing is, it introduces CA in other areas… :man_facepalming:

I would probably prefer my first workaround.

1 Like

I did this edit and then added the channel mixer settings used by TN …no issues with halo so I think it really is not even just this setting and the initial case several small contributions…including a couple you pointed out…

Adjusting filmic and following a pretty standard edit…then adding the channel mixer with the OP settings…

_A7R8492_03.ARW.xmp (12.8 KB)

PS there were typical CA and I found switching the module to use red as the tracker was the best…I agree it did not work at all on the halo but I don’t think it would

For me there wasn’t one thing but several that made that little contrasted edge worse… and with a different edit the same channel mixer settings in CC module have no problem so its not that but a few things…

1 Like

Be aware that this creates a new border around the tree.