| Author | Thread |
|
|
11/12/2008 12:37:33 PM · #26 |
Even closer now.
Now, the jpgs for DPC HAVE to be sRGB no?
Okay, I did the edits with the proofing off and monitor RGB on. I convert from 16-bit to 8-bit TIFF, then I go to save for web and it looks like the one with the proof on, so I'm wondering if I need to edit with the proof on to show what I am getting?
|
|
|
|
11/12/2008 12:51:18 PM · #27 |
Ah!
I think I now need to set my RAW color space on my camera to Adobe RGB as well.
Do DPC jpgs need to be sRGB?
|
|
|
|
11/12/2008 12:59:00 PM · #28 |
Originally posted by goinskiing:
Ah!
I think I now need to set my RAW color space on my camera to Adobe RGB as well.
Do DPC jpgs need to be sRGB? |
Anything on the web when you're using a browser which ignores embedded profiles needs to be sRGB. |
|
|
|
11/12/2008 12:59:07 PM · #29 |
Originally posted by goinskiing:
Do DPC jpgs need to be sRGB? |
I think the problem is that some browsers recognize and apply color profiles and some do not, and those which do not assume sRGB, therefore using it (and adjusting to make your final output look good in it) offers the greatest likelihood of everybody seeing essentially the same image. |
|
|
|
11/12/2008 01:00:27 PM · #30 |
Originally posted by goinskiing:
Even closer now.
Now, the jpgs for DPC HAVE to be sRGB no?
Okay, I did the edits with the proofing off and monitor RGB on. I convert from 16-bit to 8-bit TIFF, then I go to save for web and it looks like the one with the proof on, so I'm wondering if I need to edit with the proof on to show what I am getting? |
I don't but that doesn't mean you shouldn't or don't need to. If you get consistent results without then I don't see the need to do that. |
|
|
|
11/12/2008 01:02:16 PM · #31 |
Wow this is complicated. I think I have the knowledge now to at least play around with it and see what I get. Thanks for your help everyone, if you come up with any other ideas, let me know.
Message edited by author 2008-11-12 13:03:16.
|
|
|
|
11/12/2008 01:03:17 PM · #32 |
Originally posted by goinskiing:
Wow this is complicated. |
Welcome to colour management. ;oP |
|
|
|
11/12/2008 01:07:52 PM · #33 |
Originally posted by cpanaioti:
Originally posted by goinskiing:
Wow this is complicated. |
Welcome to colour management. ;oP |
It's even more fun if you're color-blind ... ;-)
 |
|
|
|
11/12/2008 06:33:50 PM · #34 |
Originally posted by cpanaioti:
Originally posted by goinskiing:
If I transfer my .CR2 file from DPP it doesn't ask, it just opens it as (RGB/16) .TIF in Photoshop. |
AdobeRGB 1998?
That's good. That is a wider space than sRGB so it will be better to edit in that space and only convert to sRGB when you're ready to save for web.
|
Not true.
You need to do the edits in the color space of the final output - so if you're editing for web then you need to edit in sRGB (and 8 bit). Anytime you convert from one colorspace to another of a different size not all the colors can be matched up so the computer/conversion algorythim has to guess/interpolate/estimate the missing/non-aligning colors. You will get a color shift.
Now say you edited in 16 bit adobe RGB for 5 hours and then convert (save) to 8 bit sRGB - the colors will shift to some degree. Now what do you do? Edit it all over again, huh? Do you do that in sRGB/16 and keep converting hoping the end result looks good? Of course not. You'll need to edit it as 8 bit sRGB, huh?
Remember that all labs and most if not all printers expect sRGB files. While there are exceptions they are rare, very rare. And only a very few, expensize, specialized monitors can even display all of sRGB let alone the wider adobe RGB. So why bother to edit in a format/color space that you cannot see or print or display in?
|
|
|
|
11/12/2008 06:34:55 PM · #35 |
Originally posted by GeneralE:
Originally posted by cpanaioti:
Originally posted by goinskiing:
Wow this is complicated. |
Welcome to colour management. ;oP |
It's even more fun if you're color-blind ... ;-)
|
Oh that's an easy one. It's called shoot everything in black and white (or let the lab handle all your color).
|
|
|
|
11/12/2008 06:51:38 PM · #36 |
Originally posted by Prof_Fate:
Originally posted by cpanaioti:
Originally posted by goinskiing:
If I transfer my .CR2 file from DPP it doesn't ask, it just opens it as (RGB/16) .TIF in Photoshop. |
AdobeRGB 1998?
That's good. That is a wider space than sRGB so it will be better to edit in that space and only convert to sRGB when you're ready to save for web.
|
Not true.
You need to do the edits in the color space of the final output - so if you're editing for web then you need to edit in sRGB (and 8 bit). Anytime you convert from one colorspace to another of a different size not all the colors can be matched up so the computer/conversion algorythim has to guess/interpolate/estimate the missing/non-aligning colors. You will get a color shift.
Now say you edited in 16 bit adobe RGB for 5 hours and then convert (save) to 8 bit sRGB - the colors will shift to some degree. Now what do you do? Edit it all over again, huh? Do you do that in sRGB/16 and keep converting hoping the end result looks good? Of course not. You'll need to edit it as 8 bit sRGB, huh?
Remember that all labs and most if not all printers expect sRGB files. While there are exceptions they are rare, very rare. And only a very few, expensize, specialized monitors can even display all of sRGB let alone the wider adobe RGB. So why bother to edit in a format/color space that you cannot see or print or display in? |
Were you converting or assigning? If assigning, you'll definitely see a colour shift. If converting, the conversion options chosen will influence the result.
And, edit in 8 bit?
Message edited by author 2008-11-12 19:24:02. |
|
|
|
02/09/2009 07:55:13 PM · #37 |
Here is some info I came across on why color looks different in browsers than in photoshop
//www.gballard.net/psd/honormyembeddedprofile.html
|
|
Home -
Challenges -
Community -
League -
Photos -
Cameras -
Lenses -
Learn -
Help -
Terms of Use -
Privacy -
Top ^
DPChallenge, and website content and design, Copyright © 2001-2025 Challenging Technologies, LLC.
All digital photo copyrights belong to the photographers and may not be used without permission.
Current Server Time: 08/24/2025 09:11:21 AM EDT.
