Colour difference : Photoshop vs. Browsers

04/02/2007 03:38:01 PM · #26

Originally posted by chimericvisions:

Originally posted by PhilipDyer:
If you're working in sRGB, then there should be no difference between what you see in Photoshop and what you see in a browser window n the same machine. Are you sure that you're saving in sRGB and not converting to another color space? If you use Save for Web, it will automatically save in sRGB.

Bzzt. Not true. Save for Web, at least in CS2, does not automatically convert to RGB, in my experience. I have had to re-upload photos from SfW because they were in the wrong color space.

How odd. I know Photoshop used to do this automatically, so if it doesn't any more, then they changed it. I'll need to look this one up.

04/02/2007 05:52:55 PM · #27

Okay - do these look different to anyone here ?

This version looks to me just as it does in PSE, I did not convert to sRGB prior to doing "save for web"

This version looks significantly different to me, I did convert to sRGB profile prior to "save for web"

Message edited by author 2007-04-02 17:53:13.

Artifacts

04/02/2007 06:16:51 PM · #28

Yes... the images look different. There is something amiss...

You earlier had said something about "BibbleLite". I've never heard of it and was wondering what roll, if any, it might be having because it sounds like you are doing things correct.

Another thing, did you say that the old software still works fine but the new does not? If so there is something different about how you are doing things that is the likely cause. The first suspect would be software setting differences between old and new software.

Message edited by author 2007-04-02 18:18:24.

Canon EF 24-70mm f/2.8L II

04/02/2007 06:23:25 PM · #29

BibbleLite is a raw convertor. It's got a lot more options than NEF Launcher does, but it's too advanced for me - I'm going to get rid of it.

NEF launcher is the RAW convertor that I got with my camera.

I don't use the Adobe RAW convertor because I get better results with NEF launcher.

The photos I posted, I used PSE 4.0 for, and still ended up with the funny colour issues.

I have a 30-day trial of PSE 5.0 downloaded, so won't be using it for long anyhow.

chimericvisions

Canon EOS-60D

04/02/2007 06:33:22 PM · #30

You're saying convert, so you're probably doing it right... but just make sure you're using "Convert to Profile" NOT using "Assign Profile", because that doesn't actually change the image, it just changes what profile you use to edit it with.

In the two examples you posted, it looks like the first one is already in RGB. It may be that your RAW software automatically uses RGB without prompting. Although if that's the case I don't know why it would change at all when you convert it.

04/02/2007 06:41:26 PM · #31

Just checked - it definitely says "convert colour profile"

Artifacts

04/02/2007 06:59:12 PM · #32

Originally posted by kashi:

Still proceeding under the assumption that this is a color space issues...

If you are using two new pieces of software then the first thing you want to do is eliminate one or the other as the cause.

BibbleLite SHOULDN'T be playing a roll but... Did your problem start after you started using it? RAW images don't have color spaces but if Bibble (or NEF Launcher) are like ACR, Adobe's RAW converter, it will assign a colorspace to the image when you open or save it so, conceivably, it could still be playing a supporting roll in your issue. Even if you want decide to bag Bibble, you will still want to track down and understand why you have the color problem.

I assume you will eliminate the "Assign Profile" from the "Convert to Profile" issues as suggested above. I never really thought about them being different, but then I've always used "Convert to Profile". :)

Message edited by author 2007-04-02 19:01:12.

04/02/2007 07:10:32 PM · #33

Okay - bagged Bibble and PSE 5.0

My monitor has a colour profile set by a pantone huey (and - just for fun - this is also new within the last few days). I do not know if this is an RGB or sRGB colourspace.

I use a Nikon D50, set to colourspace IIIa (sRGB)

NEF Launcher (Nikon Editor) uses a colourspace called "NiksRGB.icm" and is checked to "use this instead of an embedded profile when opening files"

PSE 4.0 - is now set to "Always optimize for computer screens" which says "computer screens are capable of reproducing all the colours within the sRGB color range. This setting will keep all the colors you see on screen within that range, ensuring an accurate display for any device that supports the sRGB color space"

Artifacts

04/02/2007 07:19:17 PM · #34

You made a bunch of changes... probably to many :)... did you cure the color issue?

Message edited by author 2007-04-02 19:19:46.

Canon EF-S 17-55mm f/2.8 IS USM

04/02/2007 09:11:00 PM · #35

Okay - a moment of clarity.

Even though the "convert to sRGB profile" is NOT greyed out, the file info shows a freshly opened file as being in the sRGB color space anyhow - no need to convert it at all.

splidge

Canon EOS-40D

04/03/2007 05:37:13 AM · #36

Originally posted by kashi:

I use a Nikon D50, set to colourspace IIIa (sRGB)

Just wanted to point out that if you are using RAW (NEF) the colour space you set your camera to doesn't make any real difference to the file, although the RAW converter MIGHT decide to use that setting to determine what colour space to output in...

Originally posted by kashi:

NEF Launcher (Nikon Editor) uses a colourspace called "NiksRGB.icm" and is checked to "use this instead of an embedded profile when opening files"

... but here you've overridden it on import.

I'm not sure what the NiksRGB.icm is describing but I suspect it's subtly different to standard sRGB.

Either way, what I suspect is happening is that NEF Launcher is outputting files tagged with that profile, which PS then honours when you load the file in, leading to:

Originally posted by kashi:

Well, certainly in my PSE5 if the image conforms to its notion of "sRGB" then the option will be greyed out. I don't think the files are standard sRGB when you open them up because if they were, you wouldn't be able to make them look different by converting them!

I suspect the files are coming out tagged with the NEF launcher's profile. What happens if you turn off the option in NEF launcher to override the profile on import?

The other option is, I know you've said you don't like ACR but I would suggest trying that out on a couple of files to see what impact it has on your colour problems. Certainly on my system with PSE5 I've never had any trouble using ACR (which with PSE5 is crippled to only output in sRGB). It also works fine with Lightroom (which uses ProPhoto RGB by default), although obviously I need to convert those to sRGB before saving for web.

splidge

04/03/2007 03:08:48 PM · #37

This is driving me absolutely batty !!

silverscreen

04/03/2007 03:21:30 PM · #38

I actually have the same experience...

I edit my pictures in PS Elements 5.0 - and I apply the sRGB profile when I start editing. But if I adjust the pictures to my liking in PSE and then upload them, they turn out darker on the website. So, I'll adjust the pictues to look a bit lighter than I like to make them look good when uploaded.

And, I have no idea why this is (and I'm afraid this thread didn't give me an answer either).

Nikon AF Zoom-Nikkor 24-85mm f2.8-4.0D

04/03/2007 03:37:18 PM · #39

Well, it's nice to know I'm not alone at least.

Nikolai1024

Nikon D300

04/03/2007 03:42:35 PM · #40

In photoshop, goto go proof colors and set it monitor RGB