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: 684029" data-attributes="member: 13090"><p>I think the reason some people are not seeing a difference between the sRGB image(s) and the aRGB image(s) is because some browsers/image viewers respect color-space while others do not. It's entirely possible a particular phone, tablet, browser, etc. is displaying aRGB images in an sRGB color-space.</p><p></p><p> [USER=13196]@hark[/USER] :: Not that you're asking for my advice on your workflow but I feel your pain regarding clipping and such when working with a pure sRGB workflow. That's one of the reasons I switched to an aRGB workflow as well. In short, I import and do all my raw processing in aRGB. As a final step I'll convert the image to sRGB, do a "Save As" and use that .jpg for posting online. If, and when, I find I have clipping issues once an image is converted to the sRGB color-space, I deal with it then, on a case-by-case basis. It's annoying to some degree, having to do that, but I'd rather do that than sacrifice the wider overall gamut that aRGB provides. Remember... You can always down-sample but once down-sampled, there's no going back... I decided on this workflow after experimenting with even wider gamuts, such as ProPhoto, and finally decided that working with aRGB is a good, middle of the road sort of path. </p><p></p><p>My thoughts on shooting .jpg are simpler: shoot and process in sRGB. If I'm shooting .jpg's the whole reason is to AVOID post-processing altogether. If I'm going to process a shot, I'm going to process a raw file. I'll let my camera "post-process" my .jpg's.</p><p></p><p>Just my two-cents.</p></blockquote><p></p>
[QUOTE="Horoscope Fish, post: 684029, member: 13090"] I think the reason some people are not seeing a difference between the sRGB image(s) and the aRGB image(s) is because some browsers/image viewers respect color-space while others do not. It's entirely possible a particular phone, tablet, browser, etc. is displaying aRGB images in an sRGB color-space. [USER=13196]@hark[/USER] :: Not that you're asking for my advice on your workflow but I feel your pain regarding clipping and such when working with a pure sRGB workflow. That's one of the reasons I switched to an aRGB workflow as well. In short, I import and do all my raw processing in aRGB. As a final step I'll convert the image to sRGB, do a "Save As" and use that .jpg for posting online. If, and when, I find I have clipping issues once an image is converted to the sRGB color-space, I deal with it then, on a case-by-case basis. It's annoying to some degree, having to do that, but I'd rather do that than sacrifice the wider overall gamut that aRGB provides. Remember... You can always down-sample but once down-sampled, there's no going back... I decided on this workflow after experimenting with even wider gamuts, such as ProPhoto, and finally decided that working with aRGB is a good, middle of the road sort of path. My thoughts on shooting .jpg are simpler: shoot and process in sRGB. If I'm shooting .jpg's the whole reason is to AVOID post-processing altogether. If I'm going to process a shot, I'm going to process a raw file. I'll let my camera "post-process" my .jpg's. Just my two-cents. [/QUOTE]
Verification
Post reply
Forums
Learning
Post Processing
Adobe RGB vs. sRGB
Top