Preview: colour (color) profile conversion

The colour profile of my camera (a Nikon SLR) is usually set to Adobe RGB (1998). Recently I reset it to sRGB by mistake and took some photos, which I therefore wanted to convert to Adobe RGB. I did so with three different applications: Preview, Photoshop and GraphicConverter. The results seemed inconsistent, so I conducted the following little experiment.
1. I photographed something with my camera set to Adobe RGB (1998): image 'A'.
2. I immediately photographed the same objects with the camera set to sRGB, ensuring that lighting conditions were the same as before.
3. I converted the sRGB image to Adobe RGB (1998) three times, using the three applications listed above: images 'A-Pr', 'A-Ph', 'A-Gr'.
4. I viewed all four images in the same application and on the same display, so as to eliminate differences in the characteristics of different applications and displays.
Regarding 'A' as the standard for comparison, 'A-Ph' appeared virtually identical to it. 'A-Pr' and 'A-Gr' were very similar, and both were noticeably more red than 'A'. I have reported this to the originator of GraphicConverter and he is looking into it as far as that application is concerned. But this also seems to be a problem with Preview, and I should welcome explanations. Can this be put right?

I am now in correspondence with the originator of one of the programs that I used in this experiment. I haven't got a full answer yet, but it obviously isn't an Apple problem, so I shall regard this question as answered.

Similar Messages

Preview.app & Color Profiles?

Okay, I figured this would be the best place to ask this question. Okie, so I have a couple of JPEGs before I switched to the RAW format so I'm pretty sure these have color profiles in them (right clicking, Get Info reveals RGB). However, when I view them in Preview, they look absolutely like crap. When I port them over to Photoshop, it appears just as it should.
HOWEVER, images which are exported using sRGB from Aperture (RAW to JPEG), appear fine in both Preview and Photoshop. So whats going on?

My suspicion is that rendering an image with a small color space (sRGB IEC 61966-2.1) into a wider one should work as there are no constraints. Of course, writing a wide color space (as is Aperture) to a small one such as sRGB or sRGB IEC:blah without on screen proofing it first means you will get all sorts of effects you didn't want. BTW, as far as my understanding goes, sRGB is merely the short-hand of sRGB IEC 61966-2.1 and includes ITU-R BT.709/2 file transformation. Hence the popularity of sRGB.
This (if I understood the initial q.) begs a q. as to why you see differences between an sRGB and an sRGB IEC blah profile of course.
sRGB was defined by HP and MSFT, the adopted by W3C, Pantone etc. as the standard for color rendition on "typical" 1996 color CRT monitors. These CRT's had restricted ability to present color accurately in office lighting conditions, and so the color space is very restricted. Additionally, since it focused on CRT's, it has a way curvaceous gamma curve (to map CRT luminance at different black levels to a perceived linear brightness by Mk 1 eyeballs) which is why it throws contrasts off so much on LCD's.
Light-hearted reading for insomniacs at ...
http://www.srgb.com/srgboverview/index.htm

Smart collection has "source color profile" as filter option, does not work on camera profiles

In Lightroom 5 i tried to use the "source color profile" filter option in smart collection, however it only seems to work on rgb files (jpg, tiff) that have a profile embedded. It does not work on values like "Adobe Standard" which is a "source" profile of a RAW file, or any of the camera profiles i can choose fo given Raw file. What am i doing wrong?
The Help does not give any clue on this, nor does the coverage by any of the Lightroom guru's like Juleanne Kost.

In my opinion the filter is acting correctly.
The Adobe Standard profile is not a profile defined in the source file, it is a profile assigned to the file in the raw converter and used with raw files that do not have a source color profile, already, so to me the filter is acting correctly because “source” means where the profile comes from, rather than what profile a master photo has had assigned to it.
The source-color-profile option is useful to determine the size of the color gamut in a file’s color numbers which indicates its suitability for various purposes: An sRGB file can be safely uploaded to the web, an AdobeRGB file is going to look right on a wide-gamut monitor and printablebut shouldn’t be uploaded to the web, while a ProPhotoRGB file has a large color space and can be safely edited in a way that adjusts the colors significantly, especially if it is 16-bit, without color-banding or posterization, but a ProPhotoRGB file will probably not look good if directly uploaded to the web or sent to a print-shop that doesn’t do their own color profile conversions.
I would agree that being able to filter raw files based on the assigned color profile would also be useful, but this is a different thing, to me at least, than filtering by the source-color-profile.

Exported Raw Conversion Image Resolution and Assigning a Color Profile, etc

In Aperture 1.1, although I set the exported Raw conversion image resolution to 300 dpi in the preferences, it continues to come out at 72 dpi which is something of an inconvenience. Also, is it possible to assign a color profile to the "exported version" so that it is congruent to my PS CS2 color workspace (if that is what its called). Is this program capable of carrying out a conversion as a background operation? Finally, can the layout windows be configured so that they remember how they have been used in the past? Thanks.

Iatrogenic huh! Cool!
Anyway, I'm not real clear on what it is you are trying to accomplish. Despite your obvious vocabulary skills, there seems to be some disconnect relative to what you are trying to accomplish. You are right that "exporting a version" in Aperture is roughly equivalent to what happens in ACR when you "Open" a RAW image into Photoshop. In both cases you have, hopefully, already done the adjusting of parameters you want prior to "exporting", or "opening". When you "open" or "export" you wind up with an "image" composed of pixels, whereas in the RAW adjustment phase you are just working with a temporary thumbnail and a set of mathematical instructions. Big difference, I suppose is that when you "open" and image from ACR into CS2, the resulting image is truly just pixels and has not had a "file type" applied to the file yet, until you "save" it, while in Aperture, if you "export" a file to CS2, or to the desktop, you end up with the file type already applied. Presuming you "export" a 16 bit TIFF or PSD, there is no operational difference.
I could be wrong, but with the new Bayer Demosaicing algorithms in Aperture 1.1, and the Camera RAW adjustments, you should be able to come up with an adjusted image that is VERY close if not identical to one done in ACR, with the possible exception of lens abberation adjustment. I was very critical of the RAW adjustments in 1.0.1, but I am very happy with the capabilites in 1.1. That said, I think there is still some room for improvement in user friendliness of some of the adjustments such as Levels.

Bad ramifications of color profile used in previews

It seems that Aperture's choice of color profile for its previews has some rather wide implications. In a RAW workflow, previews are assigned an Adobe RGB profile. In a JPG workflow, previews aren't generated at all at first (which makes sense - no need to create a JPG from a JPG), but they are created once you edit a photo. Then once again, the preview is assigned an Adobe RGB profile, irrespective of the color profile of the original photo. This all kind of makes sense. Presumably, Adobe RGB is the same as, or close to, the color profile Aperure uses internally.
The problem comes when photos are "shared". With the Aperture preference set to "Share previews with iLife and iWork", Aperture generates an XML file that can be used by external programs. This XML file points the external program at the previews (or the original in the case of an unedited JPG). Then photos can be picked up in various places:
* In mail.app via the Photo Browser.
* In any app via the Media section in Finder.
* On an Apple TV via the "Choose photos to share" option in iTunes.
BUT - all these photos (with the exception of an unedited JPG) will ALWAYS have an Adobe RGB profile. This is generally not good, since the photos will display badly in any app that isn't color managed. Unfortunately, this seems to apply to Apple TV. Photos there have the typically subdued look of Adobe RGB when not color managed. The situation actually gets worse with JPGs. An unedited JPG which originally had an sRGB profile will display fine, but as soon as you edit that photo in Aperture, it willl display badly because now iTunes/Apple TV is working with an Adobe RGB profile. I've done tests and it's painfully obvious.
Anyone else come across this? I'm not sure what can be done. Maybe having an option to generate proviews using sRGB would be good, but that might involve too much processing in Aperture when it's continually generating previews as you edit.
Thoughts appreciated!

The export settings don't have any effect on the problem, unfortunately. What preference are you referring to? Do you mean the Import "tab" in Aperture prefs? That just governs what Aperture uses for its initial preview. it will now, by default, use the preview that is embedded in every RAW file to speed up processing. As soon as you look at the photo, even without editing it, it will then generate its own JPG preview (with Adobe RGB profile).
I haven't received any other feedback about this problem anywhere, which is surprising to me. I think I can only post the problem through Apple feedback, and hope for the best. It seems that, in the meantime, the only course of action is to export everything you need to display properly on an AppleTV, and re-import those JPGs into Aperture (or iPhoto) so they can be displayed via iTunes. A royal pain!

Preview Color Profile Info

I know it's got to be there but I cannot find a way to show the embedded color profile information in Lightroom. I tried LIbrary View Options and Prefernces. Also tried a search in the Help area as well as as search in this forum.
Can someone help? :-)
Linda

Phil,
If I understand you right, yes. I'll say it back to make sure.
I start by processing all my images and often do additional enhancements in Photoshop, all in the Adobe RGB color space. Once I'm done with the core processing, I then will have different folders with different images and their profiles.
One will be a folder of web images in the sRGB colors space. Another folder will contain images with a particular printer profile that is embedded for output. If I use my own printer they will contain the Canon i9900 profile. If it's an outside printer the images will have that printer's profile.
When I open images in Lightroom I want to know if Lightroom is giving me a preview that is consistent with the embedded profile.
I also would like to be able to have the option to see what profile is embedded.
Hope that helps clarify. I'm a little sleep deprived lately.

Preserving ICC Color Profile in image conversion.

Hi-
I'm quite lost on how to preserve a color profile using the JAI tools. I'm hoping somebody can help.
Basically, I have a TIF, which I read the image and it's metadata, and can dump everything out showing the non-standard embedded color profile. Then I want to save the image as a jpg with the same color profile information embedded, but it doesn't seem to be automatic, and I can't find the proper API.
I'm actually shooting for JPeg2000, but I'm using standard JPG for now, so that I can easily open the resulting image up in photoshop to see the embedded color profile.
My read code is something like this:
BufferedImage img = null;
IIOMetadata md = null;
ImageTypeSpecifier spec = null;
Iterator<ImageReader> readers = ImageIO.getImageReadersByFormatName("TIFF");
ImageReader reader = readers.next();
md = reader.getImageMetadata(0);
ImageInputStream iis = ImageIO.createImageInputStream(new File("foo.tif"));
reader.setInput(iis);
TIFFImageMetadata tmd = (TIFFImageMetadata)md;
TIFFField f = tmd.getTIFFField(BaselineTIFFTagSet.TAG_ICC_PROFILE);
ICC_Profile p = ICC_Profile.getInstance(f.getAsBytes());
ICC_ColorSpace cs = new ICC_ColorSpace(p);
spec = ImageTypeSpecifier.createInterleaved(cs, new int[] {0}, DataBuffer.TYPE_BYTE, false, false);
ImageReadParam rp = new TIFFImageReadParam();
rp.setDestinationType(spec);
img = reader.read(0, rp);
And my write code is something like this:
Iterator<ImageWriter> writers = ImageIO.getImageWritersByFormatName("JPG");
ImageWriter writer = writers.next();
ImageOutputStream ios = ImageIO.createImageOutputStream(new File("foo.jpg"));
writer.setOutput(ios);
ImageWriteParam wp = configWriteParam(writer);
wp.setDestinationType(spec);
writer.write(md, new IIOImage(img, null, md), wp);
Any ideas for me? I'm completely stumped.
Thanks!
-Eric.

It worked fine before but than one day (don't remember for sure when) it started not working. I think I probably updated my Photoshop at the same time so something may have changed there.
Hello Sergei,
First of all, Welcome to the  Discussions forums!
Have you Repaired Permissions after the Photoshop update on that machine?
littleshoulders

Hidden color profiles

A profile which appears in Windows/System32/Spool/drivers/color does not appear in the Printer Profile Window of the Print Window. A second profile does appear there but not in Windows/System32/Spool/drivers/color. This is after twice rebooting my WIndows XP system, running Photoshop CS3. Any suggestions, please?

Catpearl,
On my WinXP system, my default color profile directory is WINNT/System32/Spool/drivers/color. First check that. I was on Win XP Home, and it varies from one version to another. It's probably right the way you have it, but double check to be sure.
I assume you are printing from Photoshop using "Print with Preview"? If so, you can instruct Photoshop to select a profile and rendering intent in the PS Print with Preview dialog box and it should find the profiles if they are in the right location. If you install profiles when PS is open, you may have to shut down PS and restart so it sees them. If you set the profile in PS's PwP, then turn off color management in your printer driver so you don't do double color management and conversion (butt ugly).
If you are selecting profiles in your driver, it may or may not see custom profiles. Not sure, since I always use PS print with preview when printing from Photoshop and select profiles there, or I use the PS print plugin that comes with my Canon iPF6100 printer (which bypasses the O/S completely, uses a 16 bit print stream, and talks directly to the printer...very cool and well thought out).
It could be you have profiles in the wrong location, your printer driver doesn't see them, you have a corrupted file, or there is a glitch in the driver installation. Just guesses. Also, it could be your driver settings....if you select certain settings, it may just look for the "canned" profiles that were installed with the driver. Grasping at straws, since I don't know you printer model, settings you are using, what you are using to print, etc.
Hope this triggers some ideas and investigation that pays off.
Lou

DNG files rendered with wrong color profile?

Does someone else also have a problem with DNG (digital negative) files showing incorrect colors when opened in Apple software (Preview, iPhoto, Aperture..)?
I have a Nikon D750 and currently consider using DNG as archive format for my RAW files.
But the converted DNG files are shown with a wrong color profile when opened via Apple's own camera raw framework...
It works in Adobe software - such as Lightroom - but any software using the OS X internal camera raw framework seems to use the wrong color profile when opening the DNG. Note that the original D750 NEF files are opened and rendered correctly.
I am using OS X Yosemite 10.10.2 with the latest Camera Raw Compatibility Update 6.02 installed.
On the Adobe side, it is Lightroom 5.7 and DNG Converter 8.7.1.
I tried all kinds of different conversion settings. It does not seem to make a difference whether I embed preview images in the DNG or not, whether I shoot in 12 or 14bit RAW, and whether I include the original RAW file into the DNG or not. I also tried to explicitly select the 'Camera Standard' color profile in Lightroom first and then export the DNG, but still on the OS X side the resulting image looks wrong as compared to the original NEF.
Any other Nikon user here who could verify my problems?

A few simple tests on your end may help you better understand:
1. Capture the same image (same camera settings in RAW and JPEG)
2. Open these images in Canon DPP - they will be a close match, this is because Canon DPP and the Canon camera itself use similar RAW processing algorithms
3. Open convert the CR2 to DNG, and open the CR2, DNG, and JPEG in Adobe Camera RAW - the CR2 and DNG should be a very close (if not identical) match if you use the same processing settings for each, since they are both being processed by ACR's algorithms; the JPEG will probably not match as it was processed with Canon's algorithms
What you are seeing is at the HEART of raw processing, and has nothing to do with color spaces or with DNG being at fault. The very nature of RAW processing means every processor (DPP, ACR, CaptureOne, etc) will produce different results by default - that's not to say that with some adjustments you can't match one processor's results to another, but it won't be the case by default.
The choice of RAW processor has FAR more an impact on your results than color space - in fact color space should have virtually no visual impact, though depending on the scene photographed you might have better gradations in some color spaces, better handling of highly saturated colors in some, but the overall look should remain close regardless of color space choice.
Further, as has been pointed out by others, raw files (which includes CR2 and DNG) do not have a color space - raw files are by definition raw image data which has yet to be processed into a color space. When you see color space assignments in RAW processors, that is relevant to the files you create FROM the raw files, not relevant to the raws themselves.
Before bringing inflammatory language and false assumptions to a forum with a high level of expert membership you might want to research the issue, and devise some simple tests (like above) to help you understand the issue first.

Iphoto 9.5 not supporting color profiles supported in '11

JPG Photos in iphoto 11 from Scancafe.com with color profile OS14000_A2_B8_oG that worked with iphoto '11, now not working with iphoto 9.5 and now unable to re-import.
First some background. I was using iphoto 11 and had no problem importing the scancafe jpg photos (color photos) from the DVD's. Everything was fine until I upgraded my mac mini to mavericks and upgraded iphoto 11 to 9.5. It seems iphoto 9.5 does not support the color profile of the jpgs that were scanned by scancafe. That color profile is OS14000_A2_B8_oG. I noticed that after upgrade of iphoto, that jpgs with this color profile are no longer seen at full size (they are visible as preview in iphoto, they are also visible in the mac program Preview, they also seem to work in aperture). But, when I try to view as full size in iphoto it is just black. Interstingly, the face detection from iphoto 11 still hovers, but now over black photo. The photo is still in the Masters area of the iphoto library, iphoto is just unable to view as full size.
When I tried to import the photo again, iphoto says the jpgs are unreadable. So, after hours of frustration, I realized iphoto doesn't seem to be supporting the color profile: OS14000_A2_B8_oG. When I used Adobe Lightroom 5 (Imported all first) to export as jpg (batch export) and removed the color profile (it then defaults to sRGB), the pictures were able to be imported into iphoto and were visible at full size.
To make a long story short, it seems that apple didn't provide support for this color profile with iphoto 9.5. Which is interesting, because they used to support it in iphoto 11.
Any ideas how I can save the work I have done on these photos: descriptions, face recognition, etc. without having to reimport jpgs with new color profile?
It would seem simple for apple to support the color profile and continue to do so. This foreshadows the slow removal of support for older file format and color profiles as software is upgraded. Will the photos in our iphoto library be visible in 10 years without conversions and reimporting? This is a concerning precedent.

Not what but who. That would be me. Keith is referring to this Applescrip: Embed sRGB Profile-Applescript, that you can download from Toad's Cellar. However, I've found it doesn't work on all files and have created an Automator workflow that is more reliable: Convert to JPG and Embed sRGB profile.
Both are on Toad's Cellar and you can try both. They will have to be applied to the image files outside of iPhoto before importing into iPhoto.
Happy Holidays

Photoshop Elements 11/ Missing Color Profile CMYK - Does anybody know why + what to do?

I am missing the color profile CMYK in the elements software I use.
I need to convert some data form RGB to CMYK.
Is there a setting I may change?
Thanks for helping
Regards,
ChrizB

If you only need to do this once, the easiest thing is to ask your printer to do it for you. They'll probably charge you something, but at least it will be done right. Properly converting to CMYK is considerably more complex than, say, converting from sRGB to Adobe RGB. There are a number of third party options for doing this--I think irfanview will do it in windows, and preview does it for macs, but those are pretty basic conversions that don't allow you to adjust for out of gamut colors.

Which color profile to work with

hi,
since recent i'm working with linux open source software for my DTP, which has been posing some problems, especially concerning my colors. This has nothing to do with Linux but with the fact that i don't know a lot about color management (though do find it interesting)
I have a hard time understanding (visualizing) the actual workflow of color management.
What i understand so far: When i import an image in my DTP software (Scribus), that image may have an embedded color profile (RGB) or may not. When it doesn't, the software assigns a profile to it, through the color engine (Litlle CMS). I assume it does this automatically? Otherwise I am able to assign my own profile to it, directly in Scribus. But what color profile do i assign when i export to PDF, to send off for printing? What is important to take into account regarding the commercial printer?
I've calibrated my screen using the Spyder 2 Express software, and the software has created an .icm profile for that screen. This .icm profile is automatically installed in the directory and thus also in Scribus. But when i assign this profile to my file and i export to PDF, does my commercial printer on the other side of town recognize this profile? Shouldn't i be exporting in a standard ICC profile, like Adobe RGB(1998)?
This is the part where it's hard for me to understand what to do with the profile my Spyder has created.
My sole objective however is to see on my screen as exactly possible as what comes out of the printer on the other side of town.
Thank you for your help.
Bart

borisbastoss wrote:
But what color profile do i assign when i export to PDF, to send off for printing? What is important to take into account regarding the commercial printer?
Just to be clear, in a properly color managed workflow, you do not assign at the PDF export stage. You would either preserve all profiles, or convert to a destination profile. The term assign would lead some to believe there is false profiling going on but I realize that is not what you meant.
You must contact the commercial printer to find out whether to convert to his destination color, or instead perform no color conversion and preserve your current source color spaces.
Hopefully he can provide you with a destination ICC profile which fully describes the print condition. In that case, you can convert to this color space when you export. After PDF creation you can view the destination color with an ICC compliant PDF reader to soft proof the print result.
I am not familiar with the applications you have mentioned. Adobe apps have a way of previewing destination color while still in the source space. It is called Proof Setup. You may or may not posses a tool like this. If you do you may be able to soft proof before PDF creation.
Also I am not sure if you are using Adobe Acrobat to view your PDF output. Whatever you use, it needs to honor ICC profiles to render accurate soft proofs.
As already mentioned, your monitor profile is for your soft proofing purposes only. It is not a source color space or a destination color space, and should have no involvement in PDF output.
borisbastoss wrote:
My sole objective however is to see on my screen as exactly possible as what comes out of the printer on the other side of town.
It can be difficult to get an extremely accurate soft proof. You need the destination ICC profile, and the proper tools for your display to translate this color space for you to see. If your printer is using the SWOP (Specifications for Web Offset Printing) standard or GRACoL, then there are ICC profiles you can download from the IdeAlliance website:
http://www.idealliance.org/industry_resources/branding_media_and_color/g7
Bear in mind, if the printer specifically tells you not to convert and to include all source profiles, this is called a late binding workflow (relatively rare). Late binding is progressive, but the problem is that you can't soft proof in the print color space. Even though the idea behind any color conversion is to preserve appearance, there are many source RGB colors that cannot be reproduced in print (referred to as out of gamut colors). Examples are vibrant blues, greens, oranges, and violets. You probably won't encounter a late binding printer, but without a destination ICC you just have to trust him to do the best possible conversion to move the job to his output device, whatever it may be.

Printed images...sRGB vs. iMac color profile / iPhoto vs. PSE...

Hello – I have searched the various forums available, found a wealth of information on the subject, and then became even more confused. So, here goes:
The question is in regards to color profiles on my display vs. color profiles embedded in the printed image.
I have my display set to iMac Color Profile (or should I use the sRGB Profile, which gives the display a coolor, or more bluish overall tint), and then in PSE I have sRGB embedded. When I make a print going through PSE, the colors look good and overall is a pleasant image. When I take the same image and save it into iPhoto and then print it, the overall image is slightly darker and the colors a little more saturated. Overall, another pleasant image, just slightly different.
So, I suppose my question is: what is iPhoto doing that makes the printed image a bit more saturated? How should I have my colors on the display set?
Thanks.

Printer_Rick wrote:
sRGB is Adobe's default RGB color space. It is the standard for world wide web. It is used by Pantone. In short it is the RGB profile most commonly encountered
I will re-iterate it's not my working RGB space, I don't care for it, I don't consider it ideal for CMYK conversion.
The idea that sRGB is the most common profile is a misconception.That profile was created to simulate an uncalibrated enviroment (monitor).Thats why if you use Photoshop function "Save for Web" it converts to sRGB then strips profile information.And this is only because until recently most web browsers didnt have any Color Management.I know Firefox has but the others until recently didnt (might be diferent know thought).
If its used by Pantone or not I dont know,but if it is I would like to know why and for what purpose cause it doesnt make any sense...
Its not ideal for any print (CMYK convertion) since it's very narrow gamut will most probably clip many satured colors.
The only good thing about it (besides being a grey balanced profile) is that you can be sure the person you send it too will not see many variations (shifts) in color from what youre seing on your calibrated monitor using Photoshop or any other ICC aware aplication.Thats why I always send previews of work in sRGB, because most of the time people that have to evaluate it dont even bother to open them in Photoshop,they use e-mail programs or browsers,let alone calibrated/profiled monitors.
I think the idea behind making it default is just that,being on the safe side.People that are aware of that ussually change it unless theyre working mainly for the Web.
This and much more you can find on the links about Bruce Fraser.He made great contributions to make people aware of Color Management.
Hope this helps.
Especificaly u can read this one:
http://www.creativepro.com/article/out-of-gamut-getting-a-handle-on-color-management
Images on examples are self-explanatory.

Odd color shift and OS color profile question

I've run into something that leads me to believe that the OS X color profile management has caused me a problem. I'd like to figure out how to tell the OS to not manage color profiles in order to avoid future problems. So far this is only an issue when dealing with CMYK images.
A little background...
I received a JPEG image from a photographer. Converted it to CMYK and made minor edits in Photoshop, not touching the color profiles or trying to color correct. I saved a JPEG of the edited image, and imported it into Freehand 10. When imported, the entire image shifted slightly pink. When viewed in Preview or Photoshop it looked fine. It was only when I imported it that it shifted.
A friend suggested this might have something to with color profiles, so I fiddled around with both PS and FH to make sure they were using the same ones. Even when they were the image shifted pink. This was on my desktop machine, recently upgraded to Tiger.
I noticed my PowerBook was still running Panther. I took the same image, same data file, same programs and when I imported the image again, it was fine. Looked just like it did in PhotoShop and Preview. I immediately saved out a PDF for posterity and press use.
Given the above, the only real variable is the version of the OS. This leads me to believe that there's something about how Tiger handles color profiles on the OS level that's causing this shift. What I don't know is how to remove the OS' meddling to remove it from the workflow.
Any ideas?
Thanks in advance...
G4 Dual 867 Mac OS X (10.4.3) 768MB RAM, 120GBHD

audi454 wrote:
1. AdobeRGB
2. Im not sure what you mean, preferences in PSE?
3. My client has a print release, I use WHCC to print my pictures and I believe they require sRGB as well.
4. Yes I always shoot in RAW.
Thanks for taking the time to help, I looked at my Lightroom color settings since that's how I import my pics and it was set on Adobe Pro I believe... I changed it to sRGB.
Sent from my iPhone
Thanks for the info : I'll start with the 4th question because it's the less known factor with Elements
If you shoot raw, the settings of your camera (Adobe RGB) will be ignored. This setting works only with the out of camera jpegs. A 'raw' file has no color profile, so PSE needs to know which profile you want for the conversion. You won't find any menu or dialog entries in ACR for that purpose. So, to convert the file when you 'Open' in the editor, PSE looks at the settings in your editor (my question #2, Menu Edit/Color settings...
If you have chosen option 1, 'Always optimize for computer screens', PSE will convert the raw file to sRGB profile.
If you have chosen 'Always optimize for printing', PSE will convert to aRGB...
If you want to take advantage of the slightly wider color space of Adobe RGB because your home printer can use it, select the second option, but if you have to send the picture in sRGB, do not forget to convert before sending. Menu /image/convert color profile.
If you don't want to bother, use sRGB with the option 1. You won't risk forgetting to convert the client version.
Never use 'No color management' in the menu /edit/color settings
If you first convert to sRGB with option 1, you won't get any advantage to convert to aRGB afterwards

Setting color Profile in PSE8

In setting the color profile for pictures to be exported to FCS3 for HDTV it is recommended to use color profile HDTV (rec. 709). This setting is not available.
For SD a color profile of sRGB is recommended, which is available Image > Convert Color Profile > convert sRGB.
Is there a way to set the proper color profile for HDTV?
Thank you
Kent

Elements is very limited in its ability to convert to different colour spaces. Basically it only offers you a choice of AdobeRGB or sRGB.
There is a free profile conversion program from here.... http://www.drycreekphoto.com/tools/profile_converter/
You'll need to get the profile you need which I think is available here.... http://www.adobe.com/support/downloads/detail.jsp?ftpID=4074
Although it says MAC OS you should be able to just unzip the file and put the appropriate profile in the correct folder for your system.
Colin

Preview: colour (color) profile conversion

Similar Messages

Maybe you are looking for