Digital Nigel
Forum Pro
Which cameras are you using PL7 with?I bought PL7 and C1. PL7 is not so good.
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Which cameras are you using PL7 with?I bought PL7 and C1. PL7 is not so good.
Thanks for the luminance mask explanation. Looks like it could be useful. Can you save a luminance mask into your default style? or multiple luminance masks?You can adjust tones and many other things in any brightness range you like.I have pl7 now but not fp7. still on the fence for fp7. i'm interested to know how that can work as its something ive not seen yet.That's now fixed in PL7+FP7. You can be as selective as you like now using the new luminance mask. I'm still experimenting to find my preferred settings, but will probably include such custom tonal controls in my default preset. Then I can apply them as needed by adjusting their opacity.I also use capture one and dxo. I usually default to capture one as i find it easier and faster to work with. whilst i do have techniques to process high iso in capture one i'll sometimes decide to process it in dxo as that can work out easier. I actually do rate capture one noise reduction but when it comes to high iso, say over 3200, then dxo can be really impressive. I also prefer to process certain cameras over others in dxo.
I'm not a high masking user but when i need it i want it to be great and capture one makes it easier and better for me so dxo can still improve that.
dxo can certainly improve their non selective tone controls. only way to do that now is to bring out an alternative new tools to keep it backwards compatible.
For example, let's start with a simple linear gradient:
Simple linear gradient
Now let's use the Highlights tone control at its maximum setting (-100):
Highlights tone control -100
As you can see, this has reduced not just the highlights but the midrange and to a lesser extent, even the shadows. So let's use a luminance mask to only reduce the actual highlights:
Luminance mask to reduce highlights only
As you can see, this has produced a much more concentrated effect
If I compare them:
As can be seen, the Luminance mask can be used to limit the effect to any part of the range
Note that you could pick any other range(s).
It's pretty easy in PL to copy all or selected edit settings from one to other image(s). Just a couple of right clicks.In general capture one just has lots of little things that addup to make a nice overall workflow from start to finish. Some things may seem minor on its own but when you add it all up it can make a huge difference. I really like that capture one can import my images from sd card to my desired preset location and folders layout. its also nicer to cull images with. I like that i can change my short cut keys so i can use "-" for red color label, "+" for green color label or click on the colors from the interface. i also set star Rankings to the 1,2,3,4,5 keys. really simple in capture one but menu diving or finger twisting shortcut combos you cant change in dxo. Now onto the editing.In what way?dxo is a bit of a joke when it comes to non supported lenses.. why it cant just read the lens/camera metadata like other lenses and give some generic sharpening.
Curve tool often works better for tonal control than the selective tone controls and yet the curve tool is also really poor compared to capture one or any other raw convertor really.
dxo currently wants you to believe that its smart lighting fixes all your images but the reality is that it probably can do well on some images but kills others.. i turn it down and tweak manually the tools as needed.
Finally the main area for dxo to improve is workflow. copy and pasting setting in capture one is a breeze and dxo is a pain in the ass.
In capture one lets say you have 2 similar images, you process one and want to copy the settings to another. you can just select the image you want to copy settings from click on a copy button on the toolbar, click the 2nd image you want to copy to, then click the paste button on the tool bar and job done. 1 sec to copy and paste. You can also copy any individual settings like exposure, curves or whatever just as easy. Its a serious time saver without having to dip into menu.
PL also lets you create presets with whichever settings you want, which won't affect any other settings. Just use the preset editor.The other major workflow enhancement is that you can save a preset for any setting. Lets say you made a tone curve or hsl adjustment for a camera or situation. you can save it as a preset and use it direct from the tool palatte on any image. quick and easy. There are more complex ways of working with presets to. In dxo you have to go into a panel and select the ones you want to copy and paste everytime. Its a little frustrating, i never want to automatically copy my white balance and geometry to any other image for instance.
A very simple workflow enhancement for dxo would be changeable shortcuts and allow configuring buttons to be added to the top toolbar next to Red Eye and miniature effect etc... (id remove these for a start) why cant i add copy and past buttons there, why not the highlight warning indicator which i like easier access to. or color labels or undo/redo or select all etc. or a keyword preset dropdown box
how about full heic/hif support, this would kick capture one up the backside to implement it as well. speed up the image browser.
As many as you like. I plan to set up some. fairly extreme adjustments, then vary the opacity to control their strengths. And, of course, they can control not just exposure, but also things like CVP, saturation, micro contrast, etc.Thanks for the luminance mask explanation. Looks like it could be useful. Can you save a luminance mask into your default style? or multiple luminance masks?You can adjust tones and many other things in any brightness range you like.I have pl7 now but not fp7. still on the fence for fp7. i'm interested to know how that can work as its something ive not seen yet.That's now fixed in PL7+FP7. You can be as selective as you like now using the new luminance mask. I'm still experimenting to find my preferred settings, but will probably include such custom tonal controls in my default preset. Then I can apply them as needed by adjusting their opacity.I also use capture one and dxo. I usually default to capture one as i find it easier and faster to work with. whilst i do have techniques to process high iso in capture one i'll sometimes decide to process it in dxo as that can work out easier. I actually do rate capture one noise reduction but when it comes to high iso, say over 3200, then dxo can be really impressive. I also prefer to process certain cameras over others in dxo.
I'm not a high masking user but when i need it i want it to be great and capture one makes it easier and better for me so dxo can still improve that.
dxo can certainly improve their non selective tone controls. only way to do that now is to bring out an alternative new tools to keep it backwards compatible.
For example, let's start with a simple linear gradient:
Simple linear gradient
Now let's use the Highlights tone control at its maximum setting (-100):
Highlights tone control -100
As you can see, this has reduced not just the highlights but the midrange and to a lesser extent, even the shadows. So let's use a luminance mask to only reduce the actual highlights:
Luminance mask to reduce highlights only
As you can see, this has produced a much more concentrated effect
If I compare them:
As can be seen, the Luminance mask can be used to limit the effect to any part of the range
Note that you could pick any other range(s).
It's pretty easy in PL to copy all or selected edit settings from one to other image(s). Just a couple of right clicks.In general capture one just has lots of little things that addup to make a nice overall workflow from start to finish. Some things may seem minor on its own but when you add it all up it can make a huge difference. I really like that capture one can import my images from sd card to my desired preset location and folders layout. its also nicer to cull images with. I like that i can change my short cut keys so i can use "-" for red color label, "+" for green color label or click on the colors from the interface. i also set star Rankings to the 1,2,3,4,5 keys. really simple in capture one but menu diving or finger twisting shortcut combos you cant change in dxo. Now onto the editing.In what way?dxo is a bit of a joke when it comes to non supported lenses.. why it cant just read the lens/camera metadata like other lenses and give some generic sharpening.
Curve tool often works better for tonal control than the selective tone controls and yet the curve tool is also really poor compared to capture one or any other raw convertor really.
dxo currently wants you to believe that its smart lighting fixes all your images but the reality is that it probably can do well on some images but kills others.. i turn it down and tweak manually the tools as needed.
Finally the main area for dxo to improve is workflow. copy and pasting setting in capture one is a breeze and dxo is a pain in the ass.
In capture one lets say you have 2 similar images, you process one and want to copy the settings to another. you can just select the image you want to copy settings from click on a copy button on the toolbar, click the 2nd image you want to copy to, then click the paste button on the tool bar and job done. 1 sec to copy and paste. You can also copy any individual settings like exposure, curves or whatever just as easy. Its a serious time saver without having to dip into menu.
PL also lets you create presets with whichever settings you want, which won't affect any other settings. Just use the preset editor.The other major workflow enhancement is that you can save a preset for any setting. Lets say you made a tone curve or hsl adjustment for a camera or situation. you can save it as a preset and use it direct from the tool palatte on any image. quick and easy. There are more complex ways of working with presets to. In dxo you have to go into a panel and select the ones you want to copy and paste everytime. Its a little frustrating, i never want to automatically copy my white balance and geometry to any other image for instance.
A very simple workflow enhancement for dxo would be changeable shortcuts and allow configuring buttons to be added to the top toolbar next to Red Eye and miniature effect etc... (id remove these for a start) why cant i add copy and past buttons there, why not the highlight warning indicator which i like easier access to. or color labels or undo/redo or select all etc. or a keyword preset dropdown box
how about full heic/hif support, this would kick capture one up the backside to implement it as well. speed up the image browser.
Hi Nigel, just playing with a greyscale image that contains bands at 0 and 255. Just noticed that DXO Highlight slider does not have any effect on the 255 band. Is this why people think that highlight recovery in DXO isn't as good as other software?As many as you like. I plan to set up some. fairly extreme adjustments, then vary the opacity to control their strengths. And, of course, they can control not just exposure, but also things like CVP, saturation, micro contrast, etc.
ok great, might go for fp after all these years. currently processing a batch of old Olympus epm1 files and dxo really does help with this old camera.As many as you like. I plan to set up some. fairly extreme adjustments, then vary the opacity to control their strengths. And, of course, they can control not just exposure, but also things like CVP, saturation, micro contrast, etc.Thanks for the luminance mask explanation. Looks like it could be useful. Can you save a luminance mask into your default style? or multiple luminance masks?You can adjust tones and many other things in any brightness range you like.I have pl7 now but not fp7. still on the fence for fp7. i'm interested to know how that can work as its something ive not seen yet.That's now fixed in PL7+FP7. You can be as selective as you like now using the new luminance mask. I'm still experimenting to find my preferred settings, but will probably include such custom tonal controls in my default preset. Then I can apply them as needed by adjusting their opacity.I also use capture one and dxo. I usually default to capture one as i find it easier and faster to work with. whilst i do have techniques to process high iso in capture one i'll sometimes decide to process it in dxo as that can work out easier. I actually do rate capture one noise reduction but when it comes to high iso, say over 3200, then dxo can be really impressive. I also prefer to process certain cameras over others in dxo.
I'm not a high masking user but when i need it i want it to be great and capture one makes it easier and better for me so dxo can still improve that.
dxo can certainly improve their non selective tone controls. only way to do that now is to bring out an alternative new tools to keep it backwards compatible.
For example, let's start with a simple linear gradient:
Simple linear gradient
Now let's use the Highlights tone control at its maximum setting (-100):
Highlights tone control -100
As you can see, this has reduced not just the highlights but the midrange and to a lesser extent, even the shadows. So let's use a luminance mask to only reduce the actual highlights:
Luminance mask to reduce highlights only
As you can see, this has produced a much more concentrated effect
If I compare them:
As can be seen, the Luminance mask can be used to limit the effect to any part of the range
Note that you could pick any other range(s).
It's pretty easy in PL to copy all or selected edit settings from one to other image(s). Just a couple of right clicks.In general capture one just has lots of little things that addup to make a nice overall workflow from start to finish. Some things may seem minor on its own but when you add it all up it can make a huge difference. I really like that capture one can import my images from sd card to my desired preset location and folders layout. its also nicer to cull images with. I like that i can change my short cut keys so i can use "-" for red color label, "+" for green color label or click on the colors from the interface. i also set star Rankings to the 1,2,3,4,5 keys. really simple in capture one but menu diving or finger twisting shortcut combos you cant change in dxo. Now onto the editing.In what way?dxo is a bit of a joke when it comes to non supported lenses.. why it cant just read the lens/camera metadata like other lenses and give some generic sharpening.
Curve tool often works better for tonal control than the selective tone controls and yet the curve tool is also really poor compared to capture one or any other raw convertor really.
dxo currently wants you to believe that its smart lighting fixes all your images but the reality is that it probably can do well on some images but kills others.. i turn it down and tweak manually the tools as needed.
Finally the main area for dxo to improve is workflow. copy and pasting setting in capture one is a breeze and dxo is a pain in the ass.
In capture one lets say you have 2 similar images, you process one and want to copy the settings to another. you can just select the image you want to copy settings from click on a copy button on the toolbar, click the 2nd image you want to copy to, then click the paste button on the tool bar and job done. 1 sec to copy and paste. You can also copy any individual settings like exposure, curves or whatever just as easy. Its a serious time saver without having to dip into menu.
PL also lets you create presets with whichever settings you want, which won't affect any other settings. Just use the preset editor.The other major workflow enhancement is that you can save a preset for any setting. Lets say you made a tone curve or hsl adjustment for a camera or situation. you can save it as a preset and use it direct from the tool palatte on any image. quick and easy. There are more complex ways of working with presets to. In dxo you have to go into a panel and select the ones you want to copy and paste everytime. Its a little frustrating, i never want to automatically copy my white balance and geometry to any other image for instance.
A very simple workflow enhancement for dxo would be changeable shortcuts and allow configuring buttons to be added to the top toolbar next to Red Eye and miniature effect etc... (id remove these for a start) why cant i add copy and past buttons there, why not the highlight warning indicator which i like easier access to. or color labels or undo/redo or select all etc. or a keyword preset dropdown box
how about full heic/hif support, this would kick capture one up the backside to implement it as well. speed up the image browser.
It might be — it was a surprise to me, too. Also, I was equally surprised just how far down the scale is affected by the Highlights slider. I think my control is much closer to being a real highlights control.Hi Nigel, just playing with a greyscale image that contains bands at 0 and 255. Just noticed that DXO Highlight slider does not have any effect on the 255 band. Is this why people think that highlight recovery in DXO isn't as good as other software?As many as you like. I plan to set up some. fairly extreme adjustments, then vary the opacity to control their strengths. And, of course, they can control not just exposure, but also things like CVP, saturation, micro contrast, etc.
This would be an easy fix for DXO?It might be — it was a surprise to me, too. Also, I was equally surprised just how far down the scale is affected by the Highlights slider. I think my control is much closer to being a real highlights control.Hi Nigel, just playing with a greyscale image that contains bands at 0 and 255. Just noticed that DXO Highlight slider does not have any effect on the 255 band. Is this why people think that highlight recovery in DXO isn't as good as other software?As many as you like. I plan to set up some. fairly extreme adjustments, then vary the opacity to control their strengths. And, of course, they can control not just exposure, but also things like CVP, saturation, micro contrast, etc.
I'll make shadows and midtones versions tomorrow.
I don't think they would make an incompatible change to the current controls, plus they must have a reason for doing it the current way. I suspect it probably produces better looking images for typical users than more extreme versions.This would be an easy fix for DXO?It might be — it was a surprise to me, too. Also, I was equally surprised just how far down the scale is affected by the Highlights slider. I think my control is much closer to being a real highlights control.Hi Nigel, just playing with a greyscale image that contains bands at 0 and 255. Just noticed that DXO Highlight slider does not have any effect on the 255 band. Is this why people think that highlight recovery in DXO isn't as good as other software?As many as you like. I plan to set up some. fairly extreme adjustments, then vary the opacity to control their strengths. And, of course, they can control not just exposure, but also things like CVP, saturation, micro contrast, etc.
I'll make shadows and midtones versions tomorrow.
The Highlight control having no effect on a pixel value of 255 is a major failing and not what any normal user would expect. It also looks like the Blacks slider behaves in the same way ie it does nothing to a pixel level of 0.I don't think they would make an incompatible change to the current controls, plus they must have a reason for doing it the current way. I suspect it probably produces better looking images for typical users than more extreme versions.This would be an easy fix for DXO?It might be — it was a surprise to me, too. Also, I was equally surprised just how far down the scale is affected by the Highlights slider. I think my control is much closer to being a real highlights control.Hi Nigel, just playing with a greyscale image that contains bands at 0 and 255. Just noticed that DXO Highlight slider does not have any effect on the 255 band. Is this why people think that highlight recovery in DXO isn't as good as other software?As many as you like. I plan to set up some. fairly extreme adjustments, then vary the opacity to control their strengths. And, of course, they can control not just exposure, but also things like CVP, saturation, micro contrast, etc.
I'll make shadows and midtones versions tomorrow.
I think it moves the black point. But one surprise is that it has less effect on the deepest shadows than the shadows slider does!The Highlight control having no effect on a pixel value of 255 is a major failing and not what any normal user would expect. It also looks like the Blacks slider behaves in the same way ie it does nothing to a pixel level of 0.I don't think they would make an incompatible change to the current controls, plus they must have a reason for doing it the current way. I suspect it probably produces better looking images for typical users than more extreme versions.This would be an easy fix for DXO?It might be — it was a surprise to me, too. Also, I was equally surprised just how far down the scale is affected by the Highlights slider. I think my control is much closer to being a real highlights control.Hi Nigel, just playing with a greyscale image that contains bands at 0 and 255. Just noticed that DXO Highlight slider does not have any effect on the 255 band. Is this why people think that highlight recovery in DXO isn't as good as other software?As many as you like. I plan to set up some. fairly extreme adjustments, then vary the opacity to control their strengths. And, of course, they can control not just exposure, but also things like CVP, saturation, micro contrast, etc.
I'll make shadows and midtones versions tomorrow.
See my new thread:I think it explains all the comments on these forums about highlight recovery. Not effecting 255 just makes the transition between high highlights and any 255 values look even worse.
You can get the highlight clipping warning to turn off by reducing the Highlight Tonal Contrast slider but when you use the Selective Tone highlight slider it still doesn't effect the bar in the greyscale that was 255?????
Question is what does the Selective Tone slider do on a bar where RGB values are 255,254,254?
Time has meant that I haven't been able to test fully and unfortunately, I am away for the next few days so can't investigate this (hint).
I'm sure there must be a reason for it, perhaps to protect novice users from producing strangely flat images?To me this behaviour makes no sense, doesn't fit in with every other editing program. The only way you can bring down all the highlights is to use the curves tool, but this can't be used locally. Obviously you can use the exposure control to reduce everything and this can apply locally but it's reducing exposure and not just highlights. This just looks like an own goal by DXO for no apparent reason I can think?
I don't expect it to change the behaviour of the existing controls, as it would be an unwelcome, incompatible change that would affect millions of current images. But it might be possible to add a mode switch, between legacy/narrow mode, or a selectivity slider that defaults to the current behaviour, but allows users to make the controls more specific.Your idea of using a luma mask doesn't change the Selective Tone sliders behaviour but it does allow the Exposure control to reduce just the selected range of highlights.
At this moment in time my thoughts are "what a kludge".
DXO should fix the Selective Tone sliders or at least provide some explanation as to the reasoning behind the behaviour?
I feel you have made a quite important discovery of how PL's Highlight and other Selective tonal controls work. Have you considered to bring it up at feedback.dxo.com or report it as a bug?I think it moves the black point. But one surprise is that it has less effect on the deepest shadows than the shadows slider does!The Highlight control having no effect on a pixel value of 255 is a major failing and not what any normal user would expect. It also looks like the Blacks slider behaves in the same way ie it does nothing to a pixel level of 0.I don't think they would make an incompatible change to the current controls, plus they must have a reason for doing it the current way. I suspect it probably produces better looking images for typical users than more extreme versions.This would be an easy fix for DXO?It might be — it was a surprise to me, too. Also, I was equally surprised just how far down the scale is affected by the Highlights slider. I think my control is much closer to being a real highlights control.Hi Nigel, just playing with a greyscale image that contains bands at 0 and 255. Just noticed that DXO Highlight slider does not have any effect on the 255 band. Is this why people think that highlight recovery in DXO isn't as good as other software?As many as you like. I plan to set up some. fairly extreme adjustments, then vary the opacity to control their strengths. And, of course, they can control not just exposure, but also things like CVP, saturation, micro contrast, etc.
I'll make shadows and midtones versions tomorrow.
See my new thread:I think it explains all the comments on these forums about highlight recovery. Not effecting 255 just makes the transition between high highlights and any 255 values look even worse.
You can get the highlight clipping warning to turn off by reducing the Highlight Tonal Contrast slider but when you use the Selective Tone highlight slider it still doesn't effect the bar in the greyscale that was 255?????
Question is what does the Selective Tone slider do on a bar where RGB values are 255,254,254?
Time has meant that I haven't been able to test fully and unfortunately, I am away for the next few days so can't investigate this (hint).
https://www.dpreview.com/forums/post/67385020
I'm sure there must be a reason for it, perhaps to protect novice users from producing strangely flat images?To me this behaviour makes no sense, doesn't fit in with every other editing program. The only way you can bring down all the highlights is to use the curves tool, but this can't be used locally. Obviously you can use the exposure control to reduce everything and this can apply locally but it's reducing exposure and not just highlights. This just looks like an own goal by DXO for no apparent reason I can think?
I don't expect it to change the behaviour of the existing controls, as it would be an unwelcome, incompatible change that would affect millions of current images. But it might be possible to add a mode switch, between legacy/narrow mode, or a selectivity slider that defaults to the current behaviour, but allows users to make the controls more specific.Your idea of using a luma mask doesn't change the Selective Tone sliders behaviour but it does allow the Exposure control to reduce just the selected range of highlights.
At this moment in time my thoughts are "what a kludge".
DXO should fix the Selective Tone sliders or at least provide some explanation as to the reasoning behind the behaviour?
I don't think it's a bug — it was deliberately designed to work like that, and the smooth, gentle curves produce good looking images most of the time. What it doesn't let you do is to recover just the over-exposed highlights, but the luminance masks provide a flexible solution. I think the Shadows slider probably works in an acceptable way.I feel you have made a quite important discovery of how PL's Highlight and other Selective tonal controls work. Have you considered to bring it up at feedback.dxo.com or report it as a bug?I think it moves the black point. But one surprise is that it has less effect on the deepest shadows than the shadows slider does!The Highlight control having no effect on a pixel value of 255 is a major failing and not what any normal user would expect. It also looks like the Blacks slider behaves in the same way ie it does nothing to a pixel level of 0.I don't think they would make an incompatible change to the current controls, plus they must have a reason for doing it the current way. I suspect it probably produces better looking images for typical users than more extreme versions.This would be an easy fix for DXO?It might be — it was a surprise to me, too. Also, I was equally surprised just how far down the scale is affected by the Highlights slider. I think my control is much closer to being a real highlights control.Hi Nigel, just playing with a greyscale image that contains bands at 0 and 255. Just noticed that DXO Highlight slider does not have any effect on the 255 band. Is this why people think that highlight recovery in DXO isn't as good as other software?As many as you like. I plan to set up some. fairly extreme adjustments, then vary the opacity to control their strengths. And, of course, they can control not just exposure, but also things like CVP, saturation, micro contrast, etc.
I'll make shadows and midtones versions tomorrow.
See my new thread:I think it explains all the comments on these forums about highlight recovery. Not effecting 255 just makes the transition between high highlights and any 255 values look even worse.
You can get the highlight clipping warning to turn off by reducing the Highlight Tonal Contrast slider but when you use the Selective Tone highlight slider it still doesn't effect the bar in the greyscale that was 255?????
Question is what does the Selective Tone slider do on a bar where RGB values are 255,254,254?
Time has meant that I haven't been able to test fully and unfortunately, I am away for the next few days so can't investigate this (hint).
https://www.dpreview.com/forums/post/67385020
I'm sure there must be a reason for it, perhaps to protect novice users from producing strangely flat images?To me this behaviour makes no sense, doesn't fit in with every other editing program. The only way you can bring down all the highlights is to use the curves tool, but this can't be used locally. Obviously you can use the exposure control to reduce everything and this can apply locally but it's reducing exposure and not just highlights. This just looks like an own goal by DXO for no apparent reason I can think?
I don't expect it to change the behaviour of the existing controls, as it would be an unwelcome, incompatible change that would affect millions of current images. But it might be possible to add a mode switch, between legacy/narrow mode, or a selectivity slider that defaults to the current behaviour, but allows users to make the controls more specific.Your idea of using a luma mask doesn't change the Selective Tone sliders behaviour but it does allow the Exposure control to reduce just the selected range of highlights.
At this moment in time my thoughts are "what a kludge".
DXO should fix the Selective Tone sliders or at least provide some explanation as to the reasoning behind the behaviour?
OK, luckily, I got both PL7 and FP 7. I will try on some burnt out highlights....I don't think it's a bug — it was deliberately designed to work like that, and the smooth, gentle curves produce good looking images most of the time. What it doesn't let you do is to recover just the over-exposed highlights, but the luminance masks provide a flexible solution. I think the Shadows slider probably works in an acceptable way.I feel you have made a quite important discovery of how PL's Highlight and other Selective tonal controls work. Have you considered to bring it up at feedback.dxo.com or report it as a bug?I think it moves the black point. But one surprise is that it has less effect on the deepest shadows than the shadows slider does!The Highlight control having no effect on a pixel value of 255 is a major failing and not what any normal user would expect. It also looks like the Blacks slider behaves in the same way ie it does nothing to a pixel level of 0.I don't think they would make an incompatible change to the current controls, plus they must have a reason for doing it the current way. I suspect it probably produces better looking images for typical users than more extreme versions.This would be an easy fix for DXO?It might be — it was a surprise to me, too. Also, I was equally surprised just how far down the scale is affected by the Highlights slider. I think my control is much closer to being a real highlights control.Hi Nigel, just playing with a greyscale image that contains bands at 0 and 255. Just noticed that DXO Highlight slider does not have any effect on the 255 band. Is this why people think that highlight recovery in DXO isn't as good as other software?As many as you like. I plan to set up some. fairly extreme adjustments, then vary the opacity to control their strengths. And, of course, they can control not just exposure, but also things like CVP, saturation, micro contrast, etc.
I'll make shadows and midtones versions tomorrow.
See my new thread:I think it explains all the comments on these forums about highlight recovery. Not effecting 255 just makes the transition between high highlights and any 255 values look even worse.
You can get the highlight clipping warning to turn off by reducing the Highlight Tonal Contrast slider but when you use the Selective Tone highlight slider it still doesn't effect the bar in the greyscale that was 255?????
Question is what does the Selective Tone slider do on a bar where RGB values are 255,254,254?
Time has meant that I haven't been able to test fully and unfortunately, I am away for the next few days so can't investigate this (hint).
https://www.dpreview.com/forums/post/67385020
I'm sure there must be a reason for it, perhaps to protect novice users from producing strangely flat images?To me this behaviour makes no sense, doesn't fit in with every other editing program. The only way you can bring down all the highlights is to use the curves tool, but this can't be used locally. Obviously you can use the exposure control to reduce everything and this can apply locally but it's reducing exposure and not just highlights. This just looks like an own goal by DXO for no apparent reason I can think?
I don't expect it to change the behaviour of the existing controls, as it would be an unwelcome, incompatible change that would affect millions of current images. But it might be possible to add a mode switch, between legacy/narrow mode, or a selectivity slider that defaults to the current behaviour, but allows users to make the controls more specific.Your idea of using a luma mask doesn't change the Selective Tone sliders behaviour but it does allow the Exposure control to reduce just the selected range of highlights.
At this moment in time my thoughts are "what a kludge".
DXO should fix the Selective Tone sliders or at least provide some explanation as to the reasoning behind the behaviour?
I think DxO was well aware of how they're going to be used, hence its highly unusual decision to show the luminance mask button even if it's not enabled. Normally, PL only shows the FP and VP controls if you have access to them. It obviously hopes to sell a lot of copies of FP7!
I'm normally careful not to over-expose my shots, so I had to shoot some test shots specially to test out these controls.OK, luckily, I got both PL7 and FP 7. I will try on some burnt out highlights....I don't think it's a bug — it was deliberately designed to work like that, and the smooth, gentle curves produce good looking images most of the time. What it doesn't let you do is to recover just the over-exposed highlights, but the luminance masks provide a flexible solution. I think the Shadows slider probably works in an acceptable way.I feel you have made a quite important discovery of how PL's Highlight and other Selective tonal controls work. Have you considered to bring it up at feedback.dxo.com or report it as a bug?I think it moves the black point. But one surprise is that it has less effect on the deepest shadows than the shadows slider does!The Highlight control having no effect on a pixel value of 255 is a major failing and not what any normal user would expect. It also looks like the Blacks slider behaves in the same way ie it does nothing to a pixel level of 0.I don't think they would make an incompatible change to the current controls, plus they must have a reason for doing it the current way. I suspect it probably produces better looking images for typical users than more extreme versions.This would be an easy fix for DXO?It might be — it was a surprise to me, too. Also, I was equally surprised just how far down the scale is affected by the Highlights slider. I think my control is much closer to being a real highlights control.Hi Nigel, just playing with a greyscale image that contains bands at 0 and 255. Just noticed that DXO Highlight slider does not have any effect on the 255 band. Is this why people think that highlight recovery in DXO isn't as good as other software?As many as you like. I plan to set up some. fairly extreme adjustments, then vary the opacity to control their strengths. And, of course, they can control not just exposure, but also things like CVP, saturation, micro contrast, etc.
I'll make shadows and midtones versions tomorrow.
See my new thread:I think it explains all the comments on these forums about highlight recovery. Not effecting 255 just makes the transition between high highlights and any 255 values look even worse.
You can get the highlight clipping warning to turn off by reducing the Highlight Tonal Contrast slider but when you use the Selective Tone highlight slider it still doesn't effect the bar in the greyscale that was 255?????
Question is what does the Selective Tone slider do on a bar where RGB values are 255,254,254?
Time has meant that I haven't been able to test fully and unfortunately, I am away for the next few days so can't investigate this (hint).
https://www.dpreview.com/forums/post/67385020
I'm sure there must be a reason for it, perhaps to protect novice users from producing strangely flat images?To me this behaviour makes no sense, doesn't fit in with every other editing program. The only way you can bring down all the highlights is to use the curves tool, but this can't be used locally. Obviously you can use the exposure control to reduce everything and this can apply locally but it's reducing exposure and not just highlights. This just looks like an own goal by DXO for no apparent reason I can think?
I don't expect it to change the behaviour of the existing controls, as it would be an unwelcome, incompatible change that would affect millions of current images. But it might be possible to add a mode switch, between legacy/narrow mode, or a selectivity slider that defaults to the current behaviour, but allows users to make the controls more specific.Your idea of using a luma mask doesn't change the Selective Tone sliders behaviour but it does allow the Exposure control to reduce just the selected range of highlights.
At this moment in time my thoughts are "what a kludge".
DXO should fix the Selective Tone sliders or at least provide some explanation as to the reasoning behind the behaviour?
I think DxO was well aware of how they're going to be used, hence its highly unusual decision to show the luminance mask button even if it's not enabled. Normally, PL only shows the FP and VP controls if you have access to them. It obviously hopes to sell a lot of copies of FP7!![]()
Many thanks, I got the "Beyond Film Style Pack" for free.Eil Infante has a YouTube video demonstrating how an AI mask, saved in a style, can be applied to multiple completely different images.
The AI masking feature in C1 is a kind of amazing, all offline, without the crunching power of cloud server.
Nice bonus is the coupon code on his YouTube channel to get the "Beyond Film Style Pack!" for free.
https://www.captureone.com/en/products/styles/beyond-film-styles
I'm sure I will find quite a lot of them as I occasionally do bracketing for HDR processing.I'm normally careful not to over-expose my shots, so I had to shoot some test shots specially to test out these controls.OK, luckily, I got both PL7 and FP 7. I will try on some burnt out highlights....I don't think it's a bug — it was deliberately designed to work like that, and the smooth, gentle curves produce good looking images most of the time. What it doesn't let you do is to recover just the over-exposed highlights, but the luminance masks provide a flexible solution. I think the Shadows slider probably works in an acceptable way.I feel you have made a quite important discovery of how PL's Highlight and other Selective tonal controls work. Have you considered to bring it up at feedback.dxo.com or report it as a bug?I think it moves the black point. But one surprise is that it has less effect on the deepest shadows than the shadows slider does!The Highlight control having no effect on a pixel value of 255 is a major failing and not what any normal user would expect. It also looks like the Blacks slider behaves in the same way ie it does nothing to a pixel level of 0.I don't think they would make an incompatible change to the current controls, plus they must have a reason for doing it the current way. I suspect it probably produces better looking images for typical users than more extreme versions.This would be an easy fix for DXO?It might be — it was a surprise to me, too. Also, I was equally surprised just how far down the scale is affected by the Highlights slider. I think my control is much closer to being a real highlights control.Hi Nigel, just playing with a greyscale image that contains bands at 0 and 255. Just noticed that DXO Highlight slider does not have any effect on the 255 band. Is this why people think that highlight recovery in DXO isn't as good as other software?As many as you like. I plan to set up some. fairly extreme adjustments, then vary the opacity to control their strengths. And, of course, they can control not just exposure, but also things like CVP, saturation, micro contrast, etc.
I'll make shadows and midtones versions tomorrow.
See my new thread:I think it explains all the comments on these forums about highlight recovery. Not effecting 255 just makes the transition between high highlights and any 255 values look even worse.
You can get the highlight clipping warning to turn off by reducing the Highlight Tonal Contrast slider but when you use the Selective Tone highlight slider it still doesn't effect the bar in the greyscale that was 255?????
Question is what does the Selective Tone slider do on a bar where RGB values are 255,254,254?
Time has meant that I haven't been able to test fully and unfortunately, I am away for the next few days so can't investigate this (hint).
https://www.dpreview.com/forums/post/67385020
I'm sure there must be a reason for it, perhaps to protect novice users from producing strangely flat images?To me this behaviour makes no sense, doesn't fit in with every other editing program. The only way you can bring down all the highlights is to use the curves tool, but this can't be used locally. Obviously you can use the exposure control to reduce everything and this can apply locally but it's reducing exposure and not just highlights. This just looks like an own goal by DXO for no apparent reason I can think?
I don't expect it to change the behaviour of the existing controls, as it would be an unwelcome, incompatible change that would affect millions of current images. But it might be possible to add a mode switch, between legacy/narrow mode, or a selectivity slider that defaults to the current behaviour, but allows users to make the controls more specific.Your idea of using a luma mask doesn't change the Selective Tone sliders behaviour but it does allow the Exposure control to reduce just the selected range of highlights.
At this moment in time my thoughts are "what a kludge".
DXO should fix the Selective Tone sliders or at least provide some explanation as to the reasoning behind the behaviour?
I think DxO was well aware of how they're going to be used, hence its highly unusual decision to show the luminance mask button even if it's not enabled. Normally, PL only shows the FP and VP controls if you have access to them. It obviously hopes to sell a lot of copies of FP7!![]()