Forums
New posts
Search forums
What's new
New posts
New media
New media comments
New profile posts
Latest activity
Media
New media
New comments
Search media
Members
Current visitors
New profile posts
Search profile posts
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Menu
Log in
Register
Install the app
Install
Forums
Learning
Post Processing
Adobe RGB vs. sRGB
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="Horoscope Fish" data-source="post: 684035" data-attributes="member: 13090"><p>Fun stuff, no? LOL...</p><p></p><p></p><p></p><p>Well, yes and no... aRGB is a broader color-space than sRGB. Period. </p><p></p><p>However, there is much overlap between the two color-spaces... aRGB overlaps with sRGB everywhere <em>except in the Blue and Green channels</em>:</p><p><span style="color: #FFFFFF">......</span></p><p>[ATTACH]299536[/ATTACH] </p><p><span style="color: #FFFFFF">.....</span></p><p>That being the case I would say, "yes"; aRGB images will be better able to capture color in those areas not covered by the sRGB color-space but, since the overlap is effectively 100% in the Reds, i'd say, "no" to that part of your question. I may be splitting hairs a wee bit but I'm trying to be fair and accurate. What matters to me is that aRGB is the wider color space and that's why I've chosen to use it. It's bigger, it's arguably "better" than sRGB so why NOT use it, right? The answer to that is, because every so often you'll clip a color channel when converting a shot from the wider aRGB gamut to the smaller sRGB gamut. You then have to either go back and correct it in the aRGB color-space (so it doesn't clip when converted to sRGB) or learn to just let it go and get on with life. Sometimes (most of the time, in my experience) the clipping is so minimal I just let it go.</p><p></p><p></p><p></p><p>You're on the right track. When a photo is assigned a particular color-space it has been "tagged". This means the photo itself contains a bit of information about it's color space that image viewing software can read and understand. Some (and these days I think most) Internet browsers see that tag and will display images accordingly. Safari is color-managed, Firefox is color-managed and I don't know about Chrome. For a long time Chrome was not color-managed, but that may have changed. Individual applications on your phone, tablet, etc. may or may not be color-managed. I would think this day in age they would be but it's not a given and it can account for why the same photo will look different on different devices.</p></blockquote><p></p>
[QUOTE="Horoscope Fish, post: 684035, member: 13090"] Fun stuff, no? LOL... Well, yes and no... aRGB is a broader color-space than sRGB. Period. However, there is much overlap between the two color-spaces... aRGB overlaps with sRGB everywhere [I]except in the Blue and Green channels[/I]: [COLOR="#FFFFFF"]......[/COLOR] [ATTACH=CONFIG]299536._xfImport[/ATTACH] [COLOR="#FFFFFF"].....[/COLOR] That being the case I would say, "yes"; aRGB images will be better able to capture color in those areas not covered by the sRGB color-space but, since the overlap is effectively 100% in the Reds, i'd say, "no" to that part of your question. I may be splitting hairs a wee bit but I'm trying to be fair and accurate. What matters to me is that aRGB is the wider color space and that's why I've chosen to use it. It's bigger, it's arguably "better" than sRGB so why NOT use it, right? The answer to that is, because every so often you'll clip a color channel when converting a shot from the wider aRGB gamut to the smaller sRGB gamut. You then have to either go back and correct it in the aRGB color-space (so it doesn't clip when converted to sRGB) or learn to just let it go and get on with life. Sometimes (most of the time, in my experience) the clipping is so minimal I just let it go. You're on the right track. When a photo is assigned a particular color-space it has been "tagged". This means the photo itself contains a bit of information about it's color space that image viewing software can read and understand. Some (and these days I think most) Internet browsers see that tag and will display images accordingly. Safari is color-managed, Firefox is color-managed and I don't know about Chrome. For a long time Chrome was not color-managed, but that may have changed. Individual applications on your phone, tablet, etc. may or may not be color-managed. I would think this day in age they would be but it's not a given and it can account for why the same photo will look different on different devices. [/QUOTE]
Verification
Post reply
Forums
Learning
Post Processing
Adobe RGB vs. sRGB
Top