<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:media="http://search.yahoo.com/mrss/"

	>
<channel>
	<title>
	Comments on: Raw editor comparison &#8211; Shadows	</title>
	<atom:link href="https://wadetregaskis.com/raw-editor-comparison-shadows/feed/" rel="self" type="application/rss+xml" />
	<link>https://wadetregaskis.com/raw-editor-comparison-shadows/</link>
	<description></description>
	<lastBuildDate>Sun, 10 Dec 2023 17:22:19 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: Wade Tregaskis		</title>
		<link>https://wadetregaskis.com/raw-editor-comparison-shadows/#comment-3183</link>

		<dc:creator><![CDATA[Wade Tregaskis]]></dc:creator>
		<pubDate>Thu, 28 Jan 2016 15:59:57 +0000</pubDate>
		<guid isPermaLink="false">http://blog.wadetregaskis.com/?p=3435#comment-3183</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://wadetregaskis.com/raw-editor-comparison-shadows/#comment-3182&quot;&gt;Jim M&lt;/a&gt;.

I had not - I hadn&#039;t realised that Aperture&#039;s &#039;Black point&#039; slider crushed the shadows like this.  I&#039;ve updated the post to at least note that this was the problem, and present a more favourable result from Aperture.  Thanks for pointing this out!

Is there a foundational premise or workflow theory backing this behaviour?

I&#039;ve never met this kind of thing in any other image editor, of any kind.  I find it very unintuitive, and difficult to use.  Granted I&#039;ve only just discovered it, so perhaps it&#039;ll become more intuitive with time, but... it does seem at the very least to make (dramatic) shadow recovery exceedingly fiddly.  I tried pulling one slider (e.g. &#039;Exposure&#039;) first and then the other, but they counter-act with each other and you get weird results.  I found I had to move &#039;Exposure&#039; up only portion at a time, maybe 75% of where I think it needs to go, and then adjust the &#039;Black point&#039; to suit, and then repeat a bunch of times, narrowing in on the final settings.  Tedious.

Plus, it just doesn&#039;t match how &#039;exposure&#039; works anywhere else.  If I double my actual exposure in-camera, e.g. via aperture or shutter speed adjustment, then it doesn&#039;t arbitrarily keep the blacks pulled down.  I guess that&#039;s why it&#039;s so unintuitive to me.

For future reference:  the &#039;Black point&#039; seems to &#039;override&#039; all other exposure-related adjustments too, e.g. Levels and Curves.

FWIW I have used the &#039;Black point&#039; slider several times in the past, when I found that it worked well enough to adjust shadows / pseudo-contrast a bit.  But even then I&#039;d never realised how it was gatekeeping my shadow detail.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://wadetregaskis.com/raw-editor-comparison-shadows/#comment-3182" data-wpel-link="internal">Jim M</a>.</p>
<p>I had not &#8211; I hadn&#8217;t realised that Aperture&#8217;s &#8216;Black point&#8217; slider crushed the shadows like this.  I&#8217;ve updated the post to at least note that this was the problem, and present a more favourable result from Aperture.  Thanks for pointing this out!</p>
<p>Is there a foundational premise or workflow theory backing this behaviour?</p>
<p>I&#8217;ve never met this kind of thing in any other image editor, of any kind.  I find it very unintuitive, and difficult to use.  Granted I&#8217;ve only just discovered it, so perhaps it&#8217;ll become more intuitive with time, but&#8230; it does seem at the very least to make (dramatic) shadow recovery exceedingly fiddly.  I tried pulling one slider (e.g. &#8216;Exposure&#8217;) first and then the other, but they counter-act with each other and you get weird results.  I found I had to move &#8216;Exposure&#8217; up only portion at a time, maybe 75% of where I think it needs to go, and then adjust the &#8216;Black point&#8217; to suit, and then repeat a bunch of times, narrowing in on the final settings.  Tedious.</p>
<p>Plus, it just doesn&#8217;t match how &#8216;exposure&#8217; works anywhere else.  If I double my actual exposure in-camera, e.g. via aperture or shutter speed adjustment, then it doesn&#8217;t arbitrarily keep the blacks pulled down.  I guess that&#8217;s why it&#8217;s so unintuitive to me.</p>
<p>For future reference:  the &#8216;Black point&#8217; seems to &#8216;override&#8217; all other exposure-related adjustments too, e.g. Levels and Curves.</p>
<p>FWIW I have used the &#8216;Black point&#8217; slider several times in the past, when I found that it worked well enough to adjust shadows / pseudo-contrast a bit.  But even then I&#8217;d never realised how it was gatekeeping my shadow detail.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Jim M		</title>
		<link>https://wadetregaskis.com/raw-editor-comparison-shadows/#comment-3182</link>

		<dc:creator><![CDATA[Jim M]]></dc:creator>
		<pubDate>Thu, 28 Jan 2016 09:03:06 +0000</pubDate>
		<guid isPermaLink="false">http://blog.wadetregaskis.com/?p=3435#comment-3182</guid>

					<description><![CDATA[Did you make any attempt to adjust the black point in Aperture?  It looks rather obvious (to me) that&#039;s where the failure is.]]></description>
			<content:encoded><![CDATA[<p>Did you make any attempt to adjust the black point in Aperture?  It looks rather obvious (to me) that&#8217;s where the failure is.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
