I want to save a picture from Elements 10 to an Adobe RGB color space .jpg file. I have set the color management optimiztion to Adobe RGB but it still saves as sRGB. In the Save As window it says it is saving as ICC Adobe RGB but it saves it sRGB anyway! Also, there's no way to know this unless you run another program that detects the color space, such as QImage. Is this a bug or am I missing something? I want to save in Adobe RGB.
No. It's not from the camera. The camera is set to Adobe RGB or whatever it's supposed to be. When I use Elements 9 I have no problem saving an Adobe RGB file.
I would contact Adobe about this but there's no way to contact them. I'm a bit frustrated tthat I can't use a product I paid for. Why would I want to upgrade to Elements 11?
Some where along the way (in photoshop cs5 to conform with the current standards)) adobe changed the way the data was written to jpegs, so pse 10 might have that change as well and some programs won't read the data right.
I just saved a canon EOS 60D file to jpeg from pse 10 in the adobe rgb 1998 color space and both krita and gimp said the profile was adobe rgb 1998.
When I open the image into Photoshop 10 directly after editing in Camera
RAW and then choosing Document Profile for what to display in the bottom
left corner of the image window it says Adobe RGB.
Thanks for continuing to get back to me!
When I go to "Image Menu>Convert Color Profile" the "Convert to Adobe RGB"
profile is grayed out, which I assume means it's already in Adobe RGB since
the convert to sRGB is not grayed out.
Everything is a confirmation that your image is in aRGB.
What is not clearly explained by the previous posts, is that the camera setting of aRGB or sRGB is only active for jpegs.
Raw files from camera have no color profile.
At most, your camera setting choice may be recorded in the metadata.
In Elements, you have no menu to choose the color space in the ACR dialog. That choice is made by selecting your option in the editor, menu edit/color settings.
If you choose 'Optimize for printing', that option is transferred to the ACR plug-in to do the proper conversion in aRGB.
(Note that if you are starting with an sRGB jpeg, you won't gain anything in converting to aRGB).
Thank you for your reply.
I'm using QImage to print the image after it is edited in, and saved from,
I do everything as you said. I open the image into PSE from camera RAW and
it says Adobe RGB in the lower left corner. I then save the image as Adobe
RGB. Then I open the image in QImage and it says the image is in sRGB.
When I do the same thing with PSE 9, QImage says the image is in Adobe RGB.
An interesting thing is that, using PSE 10, I read the saved (by PSE 10) image,
that QImage says is sRGB, back into PSE 10, PSE 10 says it is Adobe RGB down
in the lower left corner.
When I read the image saved by PSE 10 (Qimage says sRGB) into PSE 9, it
also says Adobe RGB in the lower left corner.
There is something wrong. QImage thinks files saved by PSE 10 are sRGB and
files saved the same way by PSE 9 are Adobe RGB.
I just did a test with a raw image (CR2) processed through ACR with the preference option set to 'Optimize for print'. Not surprisingly, the raw conversion resulted in an aRGB profile. Then I tested if color aware software like Firefox or Faststone could recognize the profile : they did not.
I then searched in the exif viewer plugin of Firefox : the standard location is not documented : 'uncalibrated'. But if you delve into the Adobe specific section of the metadata, you find the correct profile, which explains why other Adobe software do recognize it.
I'll have to check with other versions (6 and 11) to see if they behave in the same way... it won't be long!
I do not see any change in versions 6 and 11 compared with version 10. (I don't have version 9 nor qImage).
Yes. It appears that PSE 10 saves the tiff image as Adobe RGB, according
to QImage. So now what? I can't save jpg as Adobe RGB? Is this a bug?
To be precise : it seems you can't save jpegs edited in Elements as Adobe RGB (the real color space being aRGB) with a correct metatdata understandable by non Adobe softwares. Your image is really in Adobe RBG, but Qimage or other software won't read the info present in the Adobe section of the metadata.
Is it a bug ? If that is confirmed I believe so, but I don't understand why a serious software like qimage is unable to get the info in the metadata.
In photoshop elements 10 are you using File>Save As or File>Save?
Are there layers in the file before saving?
From my understanding of QImage, it will default to sRGB if it thinks there is no profile embedded.
What version of QImage are you using?
Here's something over on photoshop.com that is similar to your experience:
I don't know whether whatever change in photoshop cs5 was carried over to pse 10 or not, but it seems QImage was updated to fix the issue.
With this document, it's very clear what happened in the metadata. Who is right, Adobe or Qimage ?
- The color space is stored in two places in the metadata. The first one is not changed by Adobe. When Adobe makes changes, they are stored in the Adobe section of the metadata.
- Qimage reads only the first one, ignoring the Adobe section. Is it ok ? Qimage ignoring Adobe section is not smart and does not seem prudent from a marketing point of view ... and perhaps it's a bit arrogant from Adobe to expect other developers to take its own metadata into account. It's up to you to choose.
- Both parties rejected the responsability to the other one... and both took measures to correct the problem in ulterior versions.
What I'd like to stress is that there is no way to tell the profile of a jpeg except if that is written in the metadata section. That does not solve the problem of BrackmanPhotography with his present versions of PSE and Qimage .
R_Kelly and MichelBParis,
Thank you for looking into this for me!
I'll try to answer R_Kelly's questions. Not sure if it matters at this
Do I use File Save, or File Save As? I use both. I usually use File Save
As when saving jpg.
Are there layers in the file before saving? No. I always Flatten Image
before saving jpg.
What version of QImage am I using? I'm using an old version, v2005.101. I
see that the latest version is, v2010.209 I believe. This issue may have
been corrected in subsequent versions beyond v2005.101. I'm not going to
be able to determine this myself as I have the old version I got from a
friend just to see if the files are sRGB or AdobeRGB. I don't have a
printer hooked up myself. My friend has the printer; an Epson 9800 44"
I see the thread from the PS / QImage posts. Interesting. Yes, seems like
there are similar issues there.
Let me see if I understand all this so I can take the appropriate measures.
It appears that, due to the color space data being written in 2 places in
jpg, QImage is the culprit in that it doesn't read the place where the
Adobe color space information is written. (Adobe may be arrogant but...).
I wonder why Qimage recognizes the Adobe color space information in TIFF
files and not in JPEGs. Assuming Qimage does recognize the Adobe color
space information in TIFF files does that mean I need to save in TIFF and send
TIFF files to QImage? If this is true then one should save using TIFF
format and not JPEG using the v2005 version of QImage, which is what my
friend prints my images with. The disadvantage in doing this is that the
TIFF files are much larger to store that JPEGs. But, given the situation I
need to save in TIFF. Is that correct?
Thanks a lot!
Well there is one more thing you might try, as strange as it sounds, you might try unchecking the save profile box in the save as dialog and see if QImage
reads the Adobe 1998 (aRGB) profile correctly.
Thank you for the suggestion. When I tried unchecking the save profile box
in the Save As dialog it had no effect. QImage still sees the file as sRGB.
You all may not be able to tell me this but I'd like to know is subsequent
versions of QImage have rectified this issue.
Europe, Middle East and Africa