Iliah Borg
Forum Pro
Yes, broadly speaking that's it.Iilah is referring to the condition where color and/or tone modifications are made after the linear-to-perceptual tone transform has been applied
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.
Yes, broadly speaking that's it.Iilah is referring to the condition where color and/or tone modifications are made after the linear-to-perceptual tone transform has been applied
Good post Glenn. Two pet peeves:"linear" refers to the original light measurements captured in the raw file. Sometimes called 'scene-linear". Usually looks dark and/or dull.
2) Human vision expects a linear input. How could it not? Light behaves pretty well linearly right up until it hits the eyes. From then on the HVS behaves like it always does, non-linearly, based on a linear input."Non-linear", obviously, refers to a departure from scene-linear, through some kind of tone transform, or "curve". This almost always has to be done to a raw image to make it presentable, having to do with the non-linear response of human vision
Good post Glenn. Two pet peeves:"linear" refers to the original light measurements captured in the raw file. Sometimes called 'scene-linear". Usually looks dark and/or dull.
1) Scene linear does not' look' dark, it only appears dark if the output medium is not properly color managed (i.e if it tries to apply a gamma curve where none is needed) , otherwise it will look 'properly' bright. It may on the other hand look dull but see 2) below.
But, isn't "perceptual" about what the brain does with the linear input?2) Human vision expects a linear input. How could it not? Light behaves pretty well linearly right up until it hits the eyes. From then on the HVS behaves like it always does, non-linearly, based on a linear input."Non-linear", obviously, refers to a departure from scene-linear, through some kind of tone transform, or "curve". This almost always has to be done to a raw image to make it presentable, having to do with the non-linear response of human vision
The 'curve' before the input, may be necessary mainly because today's cameras capture a larger DR than the output medium, so it's an easy way to squeeze the former into the latter. Absent that it looks 'dull'. Though it carries its own problems, such as chromaticity shifts. One of DcamProf/Lumariver's better attributes is that it tries its best to compensate for such.
Jack
Hello !I've bought today a Xrite Color Checker Passport,i wanted to create my own custom profiles using the Xrite ''ColorChecker Camera Calibration Software''.
I made 1 Daylight profile and 1 Daylight Shade profile,they work fantastic !
Now the question is...should i make 1 night and 1 blue hour profile to cover almost every scenario ?I am talking mainly for landscape photography...i know that i have to create also Tungsten,Fluorescent light...but mainly i take pictures of nature,so Sunrise,Sunset,Daylight,Blue hour and Night.
Right. Linear input from the scene or, alternatively, linear output from an output medium, say a monitor. Ideally the output of the monitor is identical to what's coming from the scene; second best would be proportional to it. Meaning that the scene, the capture, the raw conversion, and the output render on the monitor are in the end ideally linearly related. We strive for the ideal but, alas, practice never achieves it (nor in many cases is it necessary to do so).But, isn't "perceptual" about what the brain does with the linear input?Good post Glenn. Two pet peeves:"linear" refers to the original light measurements captured in the raw file. Sometimes called 'scene-linear". Usually looks dark and/or dull.
1) Scene linear does not' look' dark, it only appears dark if the output medium is not properly color managed (i.e if it tries to apply a gamma curve where none is needed) , otherwise it will look 'properly' bright. It may on the other hand look dull but see 2) below.
2) Human vision expects a linear input. How could it not? Light behaves pretty well linearly right up until it hits the eyes. From then on the HVS behaves like it always does, non-linearly, based on a linear input."Non-linear", obviously, refers to a departure from scene-linear, through some kind of tone transform, or "curve". This almost always has to be done to a raw image to make it presentable, having to do with the non-linear response of human vision
So if we had a 12 stop DR scene, a linear pipeline and a 12 stop CR monitor, would we need a tone curve for maximum fidelity? In an ideal world not.The 'curve' before the input, may be necessary mainly because today's cameras capture a larger DR than the output medium, so it's an easy way to squeeze the former into the latter. Absent that it looks 'dull'. Though it carries its own problems, such as chromaticity shifts. One of DcamProf/Lumariver's better attributes is that it tries its best to compensate for such.
Just for reference:Right. Linear input from the scene or, alternatively, linear output from an output medium, say a monitor. Ideally the output of the monitor is identical to what's coming from the scene; second best would be proportional to it. Meaning that the scene, the capture, the raw conversion, and the output render on the monitor are in the end ideally linearly related. We strive for the ideal but, alas, practice never achieves it (nor in many cases is it necessary to do so).But, isn't "perceptual" about what the brain does with the linear input?Good post Glenn. Two pet peeves:"linear" refers to the original light measurements captured in the raw file. Sometimes called 'scene-linear". Usually looks dark and/or dull.
1) Scene linear does not' look' dark, it only appears dark if the output medium is not properly color managed (i.e if it tries to apply a gamma curve where none is needed) , otherwise it will look 'properly' bright. It may on the other hand look dull but see 2) below.
2) Human vision expects a linear input. How could it not? Light behaves pretty well linearly right up until it hits the eyes. From then on the HVS behaves like it always does, non-linearly, based on a linear input."Non-linear", obviously, refers to a departure from scene-linear, through some kind of tone transform, or "curve". This almost always has to be done to a raw image to make it presentable, having to do with the non-linear response of human vision
So if we had a 12 stop DR scene, a linear pipeline and a 12 stop CR monitor, would we need a tone curve for maximum fidelity? In an ideal world not.The 'curve' before the input, may be necessary mainly because today's cameras capture a larger DR than the output medium, so it's an easy way to squeeze the former into the latter. Absent that it looks 'dull'. Though it carries its own problems, such as chromaticity shifts. One of DcamProf/Lumariver's better attributes is that it tries its best to compensate for such.
On the other hand, a 12 stop scene out of an 8 stop CR monitor definitely needs some sort of tonal compression lest the output look 'dull'. See for instance linearly rendered Figure 13 before the tone curve here (vs Figure 15 after):
https://www.strollswithmydog.com/raw-file-conversion-steps/
Jack
Can you describe steps You've taken? I'd love to repeat that experiment but I'm really beginer in creating video files...Just for reference:
As an experiment, I've taken a shot without a tone curve and converted it into a Rec.2020 HLG video, which then was fed to a Vizio P65-F1 - the results were, to say the least, impressive.
It's too bad we're a LONG way from having a consistent and well standardized way to deliver stills to HDR displays.
ffmpeg -loop 1 -r 24 -t 30 -i DSC02708_03.tif -vf pad=1438:2160,zscale=tin=linear:t=arib-std-b67:m=bt2020nc,format=yuv420p10le,pad=3840:2160:1200:0:black -c:v libx265 -preset medium -crf 26 -x265-params "colorprim=bt2020:atc-sei=18:colormatrix=bt2020nc" antelope.mp4Can you describe steps You've taken? I'd love to repeat that experiment but I'm really beginer in creating video files...Just for reference:
As an experiment, I've taken a shot without a tone curve and converted it into a Rec.2020 HLG video, which then was fed to a Vizio P65-F1 - the results were, to say the least, impressive.
It's too bad we're a LONG way from having a consistent and well standardized way to deliver stills to HDR displays.
Br, Pawel.
Just reset, then select linear profile and PV2. "Zero" of some adjustments is set with non-zero value. Brightness 50, Blacks 5, Contrast 50 and Curve Medium Cobtrast makes ACR pipeline true linear.PV2, linear curve, and all adjustments (exposure, blacks, brightness, contrast, fill light, etc.) set to 0 is linear rendering.What means non-linear rendering ?I am not familiar.Maybe that's because you are applying them together with non-linear rendering.Xrite software creates profiles which are more reproduction ones than general use - I never liked colors comming out of them in classical landscape photography.Good profile and exact colour balance kill the light. That's good for reproduction and documenting experiments, for forensics, but not necessarily good for art.Hello !I've bought today a Xrite Color Checker Passport,i wanted to create my own custom profiles using the Xrite ''ColorChecker Camera Calibration Software''.
I made 1 Daylight profile and 1 Daylight Shade profile,they work fantastic !
Now the question is...should i make 1 night and 1 blue hour profile to cover almost every scenario ?I am talking mainly for landscape photography...i know that i have to create also Tungsten,Fluorescent light...but mainly i take pictures of nature,so Sunrise,Sunset,Daylight,Blue hour and Night.
If you want to preserve the perception of colour of the blue hour, consider an option not to neutralize it fully.
I've found that Lumariver (which is GUI for free dcamprof) created much more natural profiles out of colorchecker targets. Probably due to nice-for-human-eye color shifts.
Br, Pawel.
-
My photo-blog: http://pawel.online
You got it exactly wrong.Brightness 50, Blacks 5, Contrast 50 and Curve Medium Cobtrast makes ACR pipeline true linear.
Great article, Iliah. But you've missed the main point. ACR with Adobe Standard profile applies default tone curve. If DCP-profile doesn't have ProfileToneCurve tag, ACR applies the default one. Default tone curve pushes midtones exactly +1EV . Plus BaselineExposue. That is why you'v got 47% instead of 18%. Difference is 1.38EV, very close to +1EV after default tone curve and +0.35EV baseline exposure. By setting sliders to 0 you've got 18% gray of patch M by chance. The process wasn't linear. Later you measure values of another pathes of Q13, but you've used synthetic dng file with embedded dcp-profile. That syntetic dng image could have embedded dcp-profile with explicit linear tone curve. That is why you've got that RGB values. If you measured the values of the real image from the top of your article, you would get different values of non-linear process.You got it exactly wrong.Brightness 50, Blacks 5, Contrast 50 and Curve Medium Cobtrast makes ACR pipeline true linear.
Here is our artice that explains the issue https://www.rawdigger.com/howtouse/overriding-raw-converter-default-adjustments-settings
Try your setting instead without modifying the dcp to make the embedded curve (0,0) (1,1) and prove the resulting numbers for G with gamma 1 form a linear progression, increasing 2x per stop.you've missed the main point.You got it exactly wrong.Brightness 50, Blacks 5, Contrast 50 and Curve Medium Cobtrast makes ACR pipeline true linear.
Here is our artice that explains the issue https://www.rawdigger.com/howtouse/overriding-raw-converter-default-adjustments-settings
"If DCP-profile doesn't have ProfileToneCurve tag, ACR applies the default one
Iliah, i've made some research to explain you more clearly what I mean.Try your setting instead without modifying the dcp to make the embedded curve (0,0) (1,1) and prove the resulting numbers for G with gamma 1 form a linear progression, increasing 2x per stop.you've missed the main point.You got it exactly wrong.Brightness 50, Blacks 5, Contrast 50 and Curve Medium Cobtrast makes ACR pipeline true linear.
Here is our artice that explains the issue https://www.rawdigger.com/howtouse/overriding-raw-converter-default-adjustments-settings
"If DCP-profile doesn't have ProfileToneCurve tag, ACR applies the default one
To embed a linear curve into an existing profile, I use a very fast, reliable, and simple method:
> exiftool -ProfileToneCurve="0 0 1 1" -o new.dcp old.dcp
"
Are you suggesting that a user does the above (as in my comment to the article)? If so, IMHO you should have explained it explicitly, starting with what is "linear profile" in your "Just reset, then select linear profile and PV2. "Zero" of some adjustments is set with non-zero value. Brightness 50, Blacks 5, Contrast 50 and Curve Medium Cobtrast makes ACR pipeline true linear" and how to make one.
...Iliah, i've made some research to explain you more clearly what I mean.Try your setting instead without modifying the dcp to make the embedded curve (0,0) (1,1) and prove the resulting numbers for G with gamma 1 form a linear progression, increasing 2x per stop.you've missed the main point.You got it exactly wrong.Brightness 50, Blacks 5, Contrast 50 and Curve Medium Cobtrast makes ACR pipeline true linear.
Here is our artice that explains the issue https://www.rawdigger.com/howtouse/overriding-raw-converter-default-adjustments-settings
"If DCP-profile doesn't have ProfileToneCurve tag, ACR applies the default one
To embed a linear curve into an existing profile, I use a very fast, reliable, and simple method:
> exiftool -ProfileToneCurve="0 0 1 1" -o new.dcp old.dcp
"
Are you suggesting that a user does the above (as in my comment to the article)? If so, IMHO you should have explained it explicitly, starting with what is "linear profile" in your "Just reset, then select linear profile and PV2. "Zero" of some adjustments is set with non-zero value. Brightness 50, Blacks 5, Contrast 50 and Curve Medium Cobtrast makes ACR pipeline true linear" and how to make one.
That's not my settings, as shown on Figure 13 on our https://www.rawdigger.com/howtouse/overriding-raw-converter-default-adjustments-settings, we account for baseline exposure:Max DE with your settings for linear process (profile Adobe Standard, Process Version 2, Blacks 0, Brightness 0, Contrast 0, Curve Linear)

Frankly, I don't see how making anything other than a linear camera profile is useful. The profile is supposed to represent the camera's data, tone and color, for transforming into other gamuts and tonalities. Doing anything else in a camera profile to me is just a stupid pet trick to do processing work in a place not intended....Iliah, i've made some research to explain you more clearly what I mean.Try your setting instead without modifying the dcp to make the embedded curve (0,0) (1,1) and prove the resulting numbers for G with gamma 1 form a linear progression, increasing 2x per stop.you've missed the main point.You got it exactly wrong.Brightness 50, Blacks 5, Contrast 50 and Curve Medium Cobtrast makes ACR pipeline true linear.
Here is our artice that explains the issue https://www.rawdigger.com/howtouse/overriding-raw-converter-default-adjustments-settings
"If DCP-profile doesn't have ProfileToneCurve tag, ACR applies the default one
To embed a linear curve into an existing profile, I use a very fast, reliable, and simple method:
> exiftool -ProfileToneCurve="0 0 1 1" -o new.dcp old.dcp
"
Are you suggesting that a user does the above (as in my comment to the article)? If so, IMHO you should have explained it explicitly, starting with what is "linear profile" in your "Just reset, then select linear profile and PV2. "Zero" of some adjustments is set with non-zero value. Brightness 50, Blacks 5, Contrast 50 and Curve Medium Cobtrast makes ACR pipeline true linear" and how to make one.
That's not my settings, as shown on Figure 13 on our https://www.rawdigger.com/howtouse/overriding-raw-converter-default-adjustments-settings, we account for baseline exposure:Max DE with your settings for linear process (profile Adobe Standard, Process Version 2, Blacks 0, Brightness 0, Contrast 0, Curve Linear)
Figure 13. PV 2 (2010), zeroed-out defaults, 0.25 BaselineExposure subtracted
We are discussing here profiles created by X-Rite ColorChecker Camera Calibration tool. Fact is, the option to create linear profiles was added to X-Rite profiling engine SDK only May 11 2021, after much pressure from our side. Did it make to the end-user product? AFAIK it's a no. That triggered my response. If you read our page, modification to make a DCP profile linear is mentioned in my comments, as I already said.
I think it is if there are things to be communicated about 'linear'. Thanks for engaging in it.I have many different cameras of different brands, a studio with stable lights, and I check things based on my own shots, taken in tightly controlled environment, against the target spectral response measurements. On a side note, Dan Margulis is famous not for being blind. With un-modified DCP zeroing-out the settings in ACR results in normal saturation and normal brightness, no acid colours any more.
I don't see this discussion as a useful one.
Combining profiles and looks is a bad idea, you (and Kodak) are right.Frankly, I don't see how making anything other than a linear camera profile is useful.
Those are fairly bad. With a linear rendition you should be getting about half thatIliah, i've made some research to explain you more clearly what I mean.Try your setting instead without modifying the dcp to make the embedded curve (0,0) (1,1) and prove the resulting numbers for G with gamma 1 form a linear progression, increasing 2x per stop.you've missed the main point.You got it exactly wrong.Brightness 50, Blacks 5, Contrast 50 and Curve Medium Cobtrast makes ACR pipeline true linear.
Here is our artice that explains the issue https://www.rawdigger.com/howtouse/overriding-raw-converter-default-adjustments-settings
"If DCP-profile doesn't have ProfileToneCurve tag, ACR applies the default one
To embed a linear curve into an existing profile, I use a very fast, reliable, and simple method:
> exiftool -ProfileToneCurve="0 0 1 1" -o new.dcp old.dcp
"
Are you suggesting that a user does the above (as in my comment to the article)? If so, IMHO you should have explained it explicitly, starting with what is "linear profile" in your "Just reset, then select linear profile and PV2. "Zero" of some adjustments is set with non-zero value. Brightness 50, Blacks 5, Contrast 50 and Curve Medium Cobtrast makes ACR pipeline true linear" and how to make one.
I downloaded raw image of studio shot on Nikon 4DS with ColorChecker24 and made some measurements and calculations. You can examine that measurements by yourself.
Here some results:
1. Max DE with your settings for linear process (profile Adobe Standard, Process Version 2, Blacks 0, Brightness 0, Contrast 0, Curve Linear) is 11,06.
2. Max DE with Adobe Linear profile and default (non-zero) settings (profile Adobe Linear, Process Version 2, Blacks +5, Brightness +50, Contrast +25, Curve Medium Contrast) is 6.61. Colors of gray patches exactly the same as with previous settings. But color patches are more close to reference values.
3. I've made the most simple profile Adobe ColorMatrix with only four image-related tags ColorMatrix1, ColorMatrix2, DefaultBlackRender and ProfileToneCurve. Only 22 numbers. Settings: Process Version 2, Blacks +5, Brightness +50, Contrast +25, Curve Medium Contrast. Max DE 6.52, very close to Adobe Linear. Just interesting.
Adobe's insistence on doing so appears to be the likely root cause of nearly all Sony color complaints...Combining profiles and looks is a bad idea, you (and Kodak) are right.Frankly, I don't see how making anything other than a linear camera profile is useful.
From the raw file for the Nikon 4DS above, not necessarily representative but SMI 88 (pretty good) as follows:Those are fairly bad. With a linear rendition you should be getting about half thatIliah, i've made some research to explain you more clearly what I mean.Try your setting instead without modifying the dcp to make the embedded curve (0,0) (1,1) and prove the resulting numbers for G with gamma 1 form a linear progression, increasing 2x per stop.you've missed the main point.You got it exactly wrong.Brightness 50, Blacks 5, Contrast 50 and Curve Medium Cobtrast makes ACR pipeline true linear.
Here is our artice that explains the issue https://www.rawdigger.com/howtouse/overriding-raw-converter-default-adjustments-settings
"If DCP-profile doesn't have ProfileToneCurve tag, ACR applies the default one
To embed a linear curve into an existing profile, I use a very fast, reliable, and simple method:
> exiftool -ProfileToneCurve="0 0 1 1" -o new.dcp old.dcp
"
Are you suggesting that a user does the above (as in my comment to the article)? If so, IMHO you should have explained it explicitly, starting with what is "linear profile" in your "Just reset, then select linear profile and PV2. "Zero" of some adjustments is set with non-zero value. Brightness 50, Blacks 5, Contrast 50 and Curve Medium Cobtrast makes ACR pipeline true linear" and how to make one.
I downloaded raw image of studio shot on Nikon 4DS with ColorChecker24 and made some measurements and calculations. You can examine that measurements by yourself.
Here some results:
1. Max DE with your settings for linear process (profile Adobe Standard, Process Version 2, Blacks 0, Brightness 0, Contrast 0, Curve Linear) is 11,06.
2. Max DE with Adobe Linear profile and default (non-zero) settings (profile Adobe Linear, Process Version 2, Blacks +5, Brightness +50, Contrast +25, Curve Medium Contrast) is 6.61. Colors of gray patches exactly the same as with previous settings. But color patches are more close to reference values.
3. I've made the most simple profile Adobe ColorMatrix with only four image-related tags ColorMatrix1, ColorMatrix2, DefaultBlackRender and ProfileToneCurve. Only 22 numbers. Settings: Process Version 2, Blacks +5, Brightness +50, Contrast +25, Curve Medium Contrast. Max DE 6.52, very close to Adobe Linear. Just interesting.
https://www.strollswithmydog.com/open-raspberry-pi-high-quality-camera-raw/
