Depends on FastRawViewer settings.
One can switch off "Exposure adjustments affect OverExposure display" on FastRawViewer Preferences - "Exposure" tab
Depends on FastRawViewer settings.
One can switch off "Exposure adjustments affect OverExposure display" on FastRawViewer Preferences - "Exposure" tab
I've always thought the people you dub "Real Worlders" are not people who distain technicalities or think that learning by doing is always superior, but rather people who realise there is often a gap between theory and practice.
For example, theory often idealises situations by ignoring inconvenient complications. Or theory yields very precise results that some people get too attached to without taking into account that there is often a lot of slop in the real world. For example, I see little point to obsessing over that last 5%, if your own working practice rarely achieves 50% precision! (Apologies if I've got my precision and accuracy reversed, I can never remember which is which). Extreme technicalities are perhaps important to those working on the bleedin edge but maybe not so much for the more journeyman worker.
The more extreme characterisation of the anti-science approach probably does exist, but less visibly than the bodge job majority, IMO.
He is telling you what you did pre-screenshot...
Nothing, he did nothing.
What happened is that Donald didn't switch "Exposure adjustments affect OverExposure display" off, and not to push any agenda, but because he isn't yet familiar with the software.
FastRawViewer Preferences -> "Exposure" -> "Exposure adjustments affect OverExposure display" on/checked, OE+corr statistics shows the result of hidden Adobe exposure correction applied. As this hidden correction, in this case (camera model / ISO setting), is about +0.35 EV, one has 4.2 K green pixels indicated as clipped before even applying any manual corrections.
@DannoLeftForums has written:He is telling you what you did pre-screenshot...
Nothing, he did nothing.
What happened is that Donald didn't switch "Exposure adjustments affect OverExposure display" off, and not to push any agenda, but because he isn't yet familiar with the software.
FastRawViewer Preferences -> "Exposure" -> "Exposure adjustments affect OverExposure display" on/checked, OE+corr statistics shows the result of hidden Adobe exposure correction applied. As this hidden correction, in this case (camera model / ISO setting), is about +0.35 EV, one has 4.2 K green pixels indicated as clipped before even applying any manual corrections.
Thanks for the explanation. I have pushed back exposure in FRV to - 3ev and still the magenta clipping highlights still show.
@IliahBorg has written: @DannoLeftForums has written:He is telling you what you did pre-screenshot...
Nothing, he did nothing.
What happened is that Donald didn't switch "Exposure adjustments affect OverExposure display" off, and not to push any agenda, but because he isn't yet familiar with the software.
FastRawViewer Preferences -> "Exposure" -> "Exposure adjustments affect OverExposure display" on/checked, OE+corr statistics shows the result of hidden Adobe exposure correction applied. As this hidden correction, in this case (camera model / ISO setting), is about +0.35 EV, one has 4.2 K green pixels indicated as clipped before even applying any manual corrections.
Thanks for the explanation. I have pushed back exposure in FRV to - 3ev and still the magenta clipping highlights still show.
Yes, because clipping is present in the raw data, and no amount of lightness change in FastRawViewer, + or -, will change that.
Thanks for the explanation. I have pushed back exposure in FRV to - 3ev and still the magenta clipping highlights still show.
Then perhaps that particular raw file was actually clipped in the green channel.
@DonaldB has written:Thanks for the explanation. I have pushed back exposure in FRV to - 3ev and still the magenta clipping highlights still show.
Then perhaps that particular raw file was actually clipped in the green channel.
Yes, about 2.1 K green pixels are clipped.
@DannoLeftForums has written:He is telling you what you did pre-screenshot...
Nothing, he did nothing.
What happened is that Donald didn't switch "Exposure adjustments affect OverExposure display" off, and not to push any agenda, but because he isn't yet familiar with the software.
FastRawViewer Preferences -> "Exposure" -> "Exposure adjustments affect OverExposure display" on/checked, OE+corr statistics shows the result of hidden Adobe exposure correction applied. As this hidden correction, in this case (camera model / ISO setting), is about +0.35 EV, one has 4.2 K green pixels indicated as clipped before even applying any manual corrections.
my exposure correction was turned off.
@IliahBorg has written: @DannoLeftForums has written:He is telling you what you did pre-screenshot...
Nothing, he did nothing.
What happened is that Donald didn't switch "Exposure adjustments affect OverExposure display" off, and not to push any agenda, but because he isn't yet familiar with the software.
FastRawViewer Preferences -> "Exposure" -> "Exposure adjustments affect OverExposure display" on/checked, OE+corr statistics shows the result of hidden Adobe exposure correction applied. As this hidden correction, in this case (camera model / ISO setting), is about +0.35 EV, one has 4.2 K green pixels indicated as clipped before even applying any manual corrections.
my exposure correction was turned off.
I think i understand now, the OE+corr is adobe default correction for my camera + the actual over exposed pixels.
@IliahBorg has written: @DannoLeftForums has written:He is telling you what you did pre-screenshot...
Nothing, he did nothing.
What happened is that Donald didn't switch "Exposure adjustments affect OverExposure display" off, and not to push any agenda, but because he isn't yet familiar with the software.
FastRawViewer Preferences -> "Exposure" -> "Exposure adjustments affect OverExposure display" on/checked, OE+corr statistics shows the result of hidden Adobe exposure correction applied. As this hidden correction, in this case (camera model / ISO setting), is about +0.35 EV, one has 4.2 K green pixels indicated as clipped before even applying any manual corrections.
my exposure correction was turned off.
I know. Above, I explained what happened.
@DonaldB has written: @IliahBorg has written: @DannoLeftForums has written:He is telling you what you did pre-screenshot...
Nothing, he did nothing.
What happened is that Donald didn't switch "Exposure adjustments affect OverExposure display" off, and not to push any agenda, but because he isn't yet familiar with the software.
FastRawViewer Preferences -> "Exposure" -> "Exposure adjustments affect OverExposure display" on/checked, OE+corr statistics shows the result of hidden Adobe exposure correction applied. As this hidden correction, in this case (camera model / ISO setting), is about +0.35 EV, one has 4.2 K green pixels indicated as clipped before even applying any manual corrections.
my exposure correction was turned off.
I think i understand now, the OE+corr is adobe default correction for my camera.
Yes, that's correct.
@DonaldB has written: @DonaldB has written: @IliahBorg has written: @DannoLeftForums has written:He is telling you what you did pre-screenshot...
Nothing, he did nothing.
What happened is that Donald didn't switch "Exposure adjustments affect OverExposure display" off, and not to push any agenda, but because he isn't yet familiar with the software.
FastRawViewer Preferences -> "Exposure" -> "Exposure adjustments affect OverExposure display" on/checked, OE+corr statistics shows the result of hidden Adobe exposure correction applied. As this hidden correction, in this case (camera model / ISO setting), is about +0.35 EV, one has 4.2 K green pixels indicated as clipped before even applying any manual corrections.
my exposure correction was turned off.
I think i understand now, the OE+corr is adobe default correction for my camera.
Yes, that's correct.
so its 2.1k + adobe correction = 4.2k ?
@IliahBorg has written: @DonaldB has written: @DonaldB has written: @IliahBorg has written: @DannoLeftForums has written:He is telling you what you did pre-screenshot...
Nothing, he did nothing.
What happened is that Donald didn't switch "Exposure adjustments affect OverExposure display" off, and not to push any agenda, but because he isn't yet familiar with the software.
FastRawViewer Preferences -> "Exposure" -> "Exposure adjustments affect OverExposure display" on/checked, OE+corr statistics shows the result of hidden Adobe exposure correction applied. As this hidden correction, in this case (camera model / ISO setting), is about +0.35 EV, one has 4.2 K green pixels indicated as clipped before even applying any manual corrections.
my exposure correction was turned off.
I think i understand now, the OE+corr is adobe default correction for my camera.
Yes, that's correct.
so its 2.1k + adobe correction = 4.2k ?
That's right.
@DonaldB has written: @IliahBorg has written: @DonaldB has written: @DonaldB has written: @IliahBorg has written: @DannoLeftForums has written:He is telling you what you did pre-screenshot...
Nothing, he did nothing.
What happened is that Donald didn't switch "Exposure adjustments affect OverExposure display" off, and not to push any agenda, but because he isn't yet familiar with the software.
FastRawViewer Preferences -> "Exposure" -> "Exposure adjustments affect OverExposure display" on/checked, OE+corr statistics shows the result of hidden Adobe exposure correction applied. As this hidden correction, in this case (camera model / ISO setting), is about +0.35 EV, one has 4.2 K green pixels indicated as clipped before even applying any manual corrections.
my exposure correction was turned off.
I think i understand now, the OE+corr is adobe default correction for my camera.
Yes, that's correct.
so its 2.1k + adobe correction = 4.2k ?
That's right.
Thank you very much and your patients, it takes a little while to sink in after using the same 2 programs for 15 years and trying to learn something new.
Thank you ...
I'm very happy we are moving forward.
[quote="@DannoLeftForums"]
In any case I already know I can add up to 1/2 a stop of extra exposure* from where the camera histogram and/or blinkies show clipping so the Sony feature doesn't enable me to do anything I can't do now 🙂
[\quote]So we can neatly wrap this up then.
Well over 600 posts about how you safely can add up to 1/2 stop exposure. More if you’re daring. Living on the edge eh!
SO BLOODY WHAT?
Folks could have taken thousands more photos in the time it’s taken to argue a whole lot of nothing on this thread.
A well exposed pile of crap never trumps a good photograph.
Focus on creating amazing images……..
Your enmity of theory [about a 100 posts here alone] does not cease to amaze
@BurnImage has written:[quote="@DannoLeftForums"]
In any case I already know I can add up to 1/2 a stop of extra exposure* from where the camera histogram and/or blinkies show clipping so the Sony feature doesn't enable me to do anything I can't do now 🙂
[\quote]So we can neatly wrap this up then.
Well over 600 posts about how you safely can add up to 1/2 stop exposure. More if you’re daring. Living on the edge eh!
SO BLOODY WHAT?
Folks could have taken thousands more photos in the time it’s taken to argue a whole lot of nothing on this thread.
A well exposed pile of crap never trumps a good photograph.
Focus on creating amazing images……..
Your enmity of theory [about a 100 posts here alone] does not cease to amaze
My contribution has been about balancing science over practical implementation. What’s your contribution and/or objection exactly?
@BurnImage has written:Well over 600 posts about how you safely can add up to 1/2 stop exposure. More if you’re daring. Living on the edge eh!
The topic was 'the best'.That 1/2 stop (often more than that in practice) appreciably reduces noise. Therefore, if you want 'the best' that's what you go for. Of course in many situations, maybe even most situations, one has other priorities than 'the best', hence you don't bother - but what Jim was commissioned to write about was 'the best'.
And of those posts, a fair proportion are yours, arguing much the same as this one. It always makes me wonder, when people drop dozens of posts complaining about too many posts - thus further increasing the number of posts but failing to move the conversation on at all.
My posts on this thread have been about balancing the science against real world implementation.
You seem to have a personal beef with that vs folks banging on to the nth degree of pixels blown.
Fine, carry on 😂