SRGB instead of ProPhoto or Adobe1998

sRGB instead of ProPhoto or Adobe1998
Hello to all ...
Why use ProPhoto or Adobe1998 color spaces in Lightroom (or even Photoshop cs3),
specially in what concerns to jpeg images, if many ( not all ) of specialized
printing enterprises will only adept sRGB to ( forcing me to convert them to this
color space after all editing work) ?
And, besides this, in my opinion, using sRGB has the advantage of being well interpreted by third party programs.
Please comment in detail if there is any the inconvenient of using sRGB !
Lots of thanks in advance,
Miguel Garcia

>Please comment in detail if there is any the inconvenient of using sRGB !
Well if you are shooting JPEG, staying in sRGB (in Photoshop) wouldn't be such a bad thing. But, Lightroom and Camera Raw were designed first and foremost as raw processors. There are a lot of reasons why one would want PP RGB or A RGB since your camera sensor is capable of capturing a lot more color than sRGB and many printers can print colors outside of sRGB.
But, if you are commenting on why Lightroom uses a linear ProPhoto RGB color space as it's processing space, well, I suspect you need to learn a bit more about image processing to really understand it. LR is using a linear (gamma 1.0) version of ProPhoto RGB in order to contain all colors any files can have to reduce errors and clipping. Processing JPEG & TIFF files as well as raw files benefit from the large gamut of color and the linear space.
The fact that photo labs require sRGB has more to do with lowering expectations (most people's displays are in sRGB so they'll get what they see) and the fact that the labs aren't too keen on having to hire knowledgeable (and costlier) personnel. Not all photo labs are, uh, so backwards...Costco, a low cost chain store actually has custom profiles one can download for most of their stores. An examination of their profiles reveals that Costco's printers (the same ones used by the "other photo labs" demanding sRGB) do indeed have a gamut of color larger than sRGB.
So, you use what you want. If you want to use sRGB, that's ok since that's one of the color spaces you can export in. But, I'll stick with ProPhoto RGB for everything other than images going to the web.

Similar Messages

Open with External Editor Profile sRGB instead of Adobe RGB

Hi,
I know in the export presets I can adjust what profile aperture will use. But what about when I open with External Editor. I like doing this because I can open my image in PhotoShop make my adjustments then save it and have aperture manage my files. But when I do this it opens the file with Adobe RGB, my lab and I sometimes want Adobe RGB. How can I change this without exporting the file and reimporting the file. Thanks.

Aperture uses a color space larger than AdobeRGB and sRGB. When an image is sent to Photoshop is converted to a 16bit AdobeRGB PSD file in order to get the largest color space to work with.
sRGB would be necessary when exporting to the web and/or send it to a printer that requieres that color profile, and that's why you have it in the export presets.

How do I get photoshop to open my images as sRGB instead of Adobe RGB?

My Camera is set to sRGB but when I open the raw files they are opening as adobe RGB. I take photos of clothing for online stores and when the Adobe RGB images are loaded onto their site it is turning all of the skin tones grey. I don't want to manually change every photo when I open them in photoshop.
Also, what is better for portraits and printing? sRGB or Adobe RGB?
Britt

This is set in ACR workflow options (the blue link below the main image window).
The camera setting is irrelevant, that only applies to in-camera processed jpegs. A raw file has no color space until it's opened into one in the raw converter.
Stay with sRGB until you know why you want a bigger color space. It has advantages, but also carries risks that can bite you if you don't know what you're doing.

Bridge exports to sRGB instead AdobeRGB

Hi,
I've a problem with the Bridge export functionality.
When I export (Nikon) RAW files to jpg files (directly via the Bridge Export functionality, without using Photoshop) always sRGB is taken as profile for the jpgs (it doesn't matter if I open the Raw files before with Camera Raw and set AdobeRGB as profile).
I can't find a setting that enables Bridge to export with AdobeRGB profile (like in Lightroom).
Any hints?
My configuration:
Windows 7 Home Premium 64bit.
Photoshop CS5
Thanks,
Holger.

Thanks. Installing a third party plug-in will be my last solution.
I've read the description of the plug-in and was wondering if it was developped for CS4. At least the Bridge in CS5 has the Export functionality (I do not know the Bridge in the previous CS4 version, perhaps there the plug-in was needed).
In the CS5 version I can specify own presets like "High Quality" export or "Export for email". Very nice but the profile is wrong.
When I use the workaround "Tools - Photoshop - Image Processor" (sorry I do not know if this is the correct wording since I use the german version of CS5) the image processor from Photoshop will be taken. There I do not have my presets, but at least the profile is set to AdobeRGB.
I also tried already Lightroom. There the export functionality works fine. But threre are two drawbacks.
1) The color labeling will not be imported from Bridge (meaning when I specify a picture as "red" or "green" this will not be recogniced by Lightroom. Same, the other way round. Setting a color label or only exporting in Lightroom and opening the Bridge the label will be displayed as "white" (formerly red, green or whatever). So my labeling is lost (for the newly exported jpgs). I do not understand why there is not a better integration for this feature of these two Adobe products.
2) There is a known bug with the Spot Removal Tool and jpgs (at my system the tool is so slow with jpgs that you can't use it => Lightroom freezes for seconds with every move of the mouse, with Raw files it works perfectly)
One last question. If you do not use the export functionality from Bridge, how do you convert your Raw files to jpg?
Thanks for the plug-in link,
Holger.
Remark after post:
I have found a solution for the color labeling problem with Bridge - Lightroom.
They have to use the exact same wording (there is also a preset in Lightroom to use the Bridge standard). Then it works.
Message was edited by: H.D.

LR4 Colour issues

When I export my images from LR4 to Flickr (or anywhere else on the web) they always appear a bit pinker than in LR. I know LR4 develops in ProPhoto by default and, as is best practice for the web, I always export in sRGB for the web. I don't want to have to 'soft proof' every single photo I take (such a hassle), and I'm guessing this is a discrepency between colour profiles. SO, is there any way I can change LR4 so that I can develop all my images in sRGB instead of proPhoto, as I used to in LR3? There was never a discrepency when I was editing in sRGB in LR3. This has only been an issue since upgrade and it really bugs me!
Also ~ from the help files proPhoto seems to assume an ability to callibrate your monitor, but not everyone has the means to do this ~ l it's a bit unfair. My monitor has an autocalibration tool and it's colours are pretty accurate, but there is no profiling 'file' that I could use for LR to read & allign itself with.

I seem to remember being able to CHANGE the develop module in LR3 so that I was working in sRGB. And when I was working in LR3, on the SAME monitor I never had colour issues between develop and export to Flickr.
If it's not the profiling, what else is it that's changed?
Not everybody has the means to buy calibration equipment. It's #1 on my wish list and I am serious about my photography, but I work on a very low budget and can only spend as I earn! I don't buy lenses. I bought one 35mm and that's me ~ everything else it's out of budget right now. A decent calibrator does not come cheap and I see no point buying a cheap one that probably won't be much better than the auto that's already built into my screen!
I just want to also say ~ when my pictures are professionally printed the colour matching seems fine ~ so I don't actually believe I have a serious monitor calibration issue.

Export using sRGB IEC61966-2.1 color profile

HI,
I want to export some photos, in JPG format using color profile sRGB IEC61966-2.1. In the "Export to Hard Drive" dialog box I see where to select the color space where I can select sRGB, AdobeRGB (1998), ProPhoto RGB, or Other. When I select "other" I see a list of color profiles but sRGB IEC61966-2.1 is not included in the list.
How can I add sRGB IEC61966-2.1 to this list?
Thanks -- Dan

LR uses the standard v 2 profile (sRGB IEC61966-2.1) as I stated. You can, from the print module, replace it with a v 4 profile (sRGB_v4_ICC_preference. ). Of course this won't be used by any browser except Safari, may confuse print services, but does give some better results, unfortunately until at least Firefox sorts out their reluctance to allow v 4 profiles (and of course IE is beyond redemption) it isn't worth it. I wonder if Adobe will ever default to the v 4?

Default setting saving files as sRGB

How do I default saving files as sRGB instead of Adobe RGB? Currently I have to convert to sRGB and then save. I am using photoshop CS5.

How are you opening your images? Through Camera Raw? If so, you may want to change the color space the images are opened in using the link at the bottom-center of the Camera Raw dialog.
-Noel

How can I make Aperture share on Flickr with sRGB?

Since I upgraded to 3.3, all photos I share on Flickr have an embedded Adobe RGB profile. Changing Web Export presets has no effect; neither does any other setting I can find. How can I make Aperture share the images with sRGB instead of Adobe RGB?

If it is possible you do it by changing the print product country in the iPhoto preferences
LN

Printing too dark in CS4

I have CS4 on Tiger 10.4.11 on a completely color managed system, Epson 4800 printer. Printing seems to be broken in the new version. Prints are very dark. I know to select "Photoshop Manages Color" in Color Handling, and "No Color Management" in the printer color management dropdown. The procedure works fine in CS3.
That something is up is suggested by this wrinkle. In this case I am printing using advanced b/w. If under color handling I choose "Printer Manages Color" and go into the b/w advanced setup, it's still too dark. If instead I choose "No color management", then make my choices in advanced b/w, it works fine.
One would first think that it's a double color management problem, but I'm turning it off anywhere I can see it in CS4, and still having problems. Is there a new secret handshake I haven't puzzled out yet?

> So, Eric, you are saying we need to Convert to a space (or gamma) in
> Photoshop before Command+P -- because the Epson Adv B&W driver will
> assume a color space/gamma -- what would that assumption be based on
> (gamma of our Mac default MonitorRGB)? Assuming I am not talking
> about feeding the Epson grayscale.
Yes.
The ABW driver wants to be fed gamma 2.2-encoded image data.
This is why my standard recommendation for printing to the ABW driver __ONLY__ is to use:
Color Handling = Photoshop Manages Colors
Printer Profile = Adobe RGB
Rendering Intent = Relative Colorimetric
Black Point Compensation = Enabled
Why does this work? Because no matter what your image working space is (e.g., sRGB, Adobe RGB, ProPhoto RGB, Apple RGB, ColorMatch RGB, etc.), doing this will cause your image data to be encoded in gamma 2.2 before the data gets passed off to the driver. (Adobe RGB has a gamma encoding of 2.2.)
The same workflow will work in Lightroom, too. You just need to check the "Display Profiles" checkbox in Lightroom to access Adobe RGB when selecting a printer profile.
If you are in grayscale mode instead of RGB mode, choose "Gray Gamma 2.2" instead of "Adobe RGB" for the printer profile.
However, the catch is that -- as noted in this thread -- there is currently a glitch, which we (Adobe + Apple + Epson) are investigating. One of the symptoms of that glitch is that the above suggested workflow does not work on Leopard.
> Does this CS4-Apple-Epson issue have anything to do with some users
> reporting dark prints in Photoshop Manage Color - No Color
> Adjustment Epson workflow? -- For example, someone using 1.8 gamma
> Monitor RGB...
Unlikely.

Problems with jpg export and color profiles

I browsed the forum but I didn't find any recent thread about the issue I'm experiencing right now, I wonder if it's common or it just affects me. Mavericks, Aperture 3.5, all up-to-date.
I imported a RAW file (I tried with both a Nikon and a Sony camera), made a few adjustements and then exported the picture as a jpg. It looked good in the Finder, in Photoshop, in Preview. When I uploaded the file to flickr, everything was ok.
Then, I browsed flickr via its iOS app and - surprise - the image is completely wrong: colors are washed out, desaturated, with an awful greenish dominance. I tried a few things and discovered soon that also opening the file on my Mac with GraphicConverter has the same ugly result. Same with the iOS version of Safari.
I use ProPhoto RGB as my default color space in Aperture. I changed to sRGB: same result. I changed to AbobeRGB and te output is finally consistent through all the platforms and apps.
Too bad I managed to do this only for one photo because, even if I changed the settings, every other photo I exported is still sticking with ProPhoto RGB. The problem is surely here because I solved it changing manually the color space to AdobeRGB with Pixelmator and re-saving the images one by one. But of course this cannot be a successful workflow...
Any experience about this?
Thank you!

OK, I can reply to myself. The issue has mysteriously gone away - no idea why. Edit: The issue is gone on Desktop, with GraphicConverter. From iOS, pictures still look weird.
About the exported default, my bad: I was using presets and they choose their own settings for color space. Still, no idea why the first one was exported in Adobe RGB instead of ProPhoto RGB (the default for "JPEG - fit within 2048x2048").
Message was edited by: difool

Losing saturation when exporting from 1.3

Hello!
I need some help. I just started noticing that when I export my jpegs from Lightroom that I am losing saturation in my images. What am I doing wrong? Do I need to change my settings to something else?
Is anyone else having this problem?
I am exporting as RGB.
Thanks!
Jen

Chaps,
I'm with Jao on this one.
Here's how it is:
|----------------------| ProPhoto Gamut
|-------------------| Camera Gamut
|----------------| Monitor Gamut
If you're in control of your colour management, you are exporting a ProPhoto file and then transforming it to sRGB:
|----------------------| ProPhoto Gamut
|                | ^
|                | |_ "Clipped" data lost in transform
|                |
|----------------| sRGB Gamut
In this case "80% ProPhoto red" maps to "100% sRGB red" and the picture looks right, although it may be clipped. You can't see this clipping on the monitor though. The monitor can't tell the difference between "80% ProPhoto red" and "100% ProPhoto red". You understand I'm making it up with my "80%" and "100%", that's why they're in quotes.
If you're not in control of your colour management, you are exporting a ProPhoto file and then assigning sRGB to it:
|----------------------| ProPhoto Gamut
|                     /
|                    /
|                   /   <- Squeeze down assigning sRGB to ProPhoto pic
|                  /
|                 /
|                /
|----------------| sRGB Gamut
That produces exactly the symptoms you describe. Something that was "80% red" in ProPhoto should map to something "100% red" in sRGB as described above. With bad colour management, one maps "80% ProPhoto red" to "80% sRGB red" and they look nothing like each other.
Note that so-called
color stupid applications - like Preview on Windows, for example - do exactly that.
However, both Photoshop CS3 and Lightroom are not color stupid.
I can easily force CS3 into doing it by a) not embedding the colour space when I save the file and/or b) "applying" a profile instead of "converting to" a profile.
Lightroom does neither of these things by default on my machine.
Your mileage may vary.
Damian
PS I don't work for Adobe.

Converting colour profile of final print package before printing

How do I convert the colour profile of a Lightroom custom printing package from Adobe Prophoto to sRGB before printing? For that matter, how do I save the thing? I have no interest in saving the template, or the collection separately, since neither has any use without the other. And without saving them as one finished item, I have no way to convert the colour profile of that item. I can see clearly from the appearance of the print preview that the above mentioned colour profile conversion is required.

You cannot change the profile in Lr to <sRGB>.
If you want to print sRGB, select <Managed by Printer> for Color Profile under Color Management.
Then in your printer's dialog select <sRGB> instead of <Application managed> (or similar wording - depending on your printer).
BTW: the term is not "Adobe proPhoto" it's "proPhoto RGB".

CS3 printing too dark - works in CS2

Hi,
I've just upgraded to CS3 and everything seems to work EXCEPT printing. The pictures print but are much much too dark compared to CS2. The CS2 photoshop prints are what I see on the monitor and has worked for a couple of years.
I've tried to make all the CS3 settings the same as CS2 but I must be missing something.
I've set the print setup to:
"Let Printer determine Colors" and "relative colormetric" so that the printer applies the ICC profiles, not Photoshop.
I make sure the printer driver dialog is set to "ICC" and "relative colormetric".
I've set the "color settings" under edit to be the same as my CS2 settings.
In everything I'm using the same color spaces in CS3 that I use in CS2.
So, what have I forgotten?
Thanks

> So, Eric, you are saying we need to Convert to a space (or gamma) in
> Photoshop before Command+P -- because the Epson Adv B&W driver will
> assume a color space/gamma -- what would that assumption be based on
> (gamma of our Mac default MonitorRGB)? Assuming I am not talking
> about feeding the Epson grayscale.
Yes.
The ABW driver wants to be fed gamma 2.2-encoded image data.
This is why my standard recommendation for printing to the ABW driver __ONLY__ is to use:
Color Handling = Photoshop Manages Colors
Printer Profile = Adobe RGB
Rendering Intent = Relative Colorimetric
Black Point Compensation = Enabled
Why does this work? Because no matter what your image working space is (e.g., sRGB, Adobe RGB, ProPhoto RGB, Apple RGB, ColorMatch RGB, etc.), doing this will cause your image data to be encoded in gamma 2.2 before the data gets passed off to the driver. (Adobe RGB has a gamma encoding of 2.2.)
The same workflow will work in Lightroom, too. You just need to check the "Display Profiles" checkbox in Lightroom to access Adobe RGB when selecting a printer profile.
If you are in grayscale mode instead of RGB mode, choose "Gray Gamma 2.2" instead of "Adobe RGB" for the printer profile.
However, the catch is that -- as noted in this thread -- there is currently a glitch, which we (Adobe + Apple + Epson) are investigating. One of the symptoms of that glitch is that the above suggested workflow does not work on Leopard.
> Does this CS4-Apple-Epson issue have anything to do with some users
> reporting dark prints in Photoshop Manage Color - No Color
> Adjustment Epson workflow? -- For example, someone using 1.8 gamma
> Monitor RGB...
Unlikely.

Colorspaces and data preservation when going in and out of L.A.B for color enhancement

There was a similar post 2 years ago which did not quite answer this specific question.
I am using a technique to enhance colors by converting to LAB and applying the image in an overlay or softlight blend. My images in RGB are all kept in ProPhoto colorspace. They are all in RAW format (specifically Nikon's .NEF). When I switch to LAB and then back to RGB, it appears that ProPhoto is replaced by sRGB colorspace.
I am then converting from sRGB back to ProPhoto.
In this process, am I losing color data as the gamut is squeezed into sRGB that does not return after going back to ProPhoto?

Hi Stan,
My first instinct is to ask how you're switching from Lab back to RGB.
Your PS colour settings may have sRGB set as the default. If you're simply choosing mode / RGB, it will convert your profile to sRGB from the Lab colour space. Definitely not what you're looking for.
You have a couple of options if this is the case. You can open up your colour settings window by choosing it from the main Edit menu. Switch your default RGB setting to ProPhoto if this is what you prefer to use the majority of the time. You can save various custom configurations and choose them when they suit the task at hand.
Also, instead of choosing mode / RGB you can choose 'convert to profile' from the main Edit menu and configure your conversion there. I typically use prefer to use this approach since I can experiment with the various settings. It also ensures that I'm converting to my intended profile.

Printing a pdf created in Pages 09

I created a newsletter in Pages 09 (already bailed on the "upgrade" which can't even link text boxes). I converted it to a pdf so that it can be printed on a Xerox work centre 7535. The colors do not match those on screen - the are much darker/grayer/muddy. Also, the photos are blurry/bitmapped. Any suggestions?
Message was edited by: DianeA

The 7535 uses autocolor sensing and will do CMYK colors when specified from the Pages color picker, you may have sent sRGB instead. What resolution photos did you place in your Pages document? There are also four printer resolutions that can be set:
Toner Saver - 600x600 dpi with limits on maximum saturation
Standard - 600 x 600 dpi with 256 half-tone levels
Enhanced - Raster image processing at 600x600 dpi with 8 bits/pixel. Halftone creation with resolution enhancement and LED marking at 1200x2400 dpi with 256 halftone levels.
High Resolution - 1200x1200 dpi with 256 halftone levels
You are using the Oct. 13, 2013 OS X print drivers for the built-in controller and the 2013 drivers and patches for the EFI Fiery controller?
WorkCentre warmed up?
Thoughts?

SRGB instead of ProPhoto or Adobe1998

Similar Messages

Maybe you are looking for