AdobeRGB* VS Adobe RGB

When I open an image in PSE3 it shows RGB/8* and another image opens and shows RGB/8 with no asterick.
The first image is shot in sRGB and the second is shot in AdobeRGB.
Is this why the asterick appears?
Thanks
Richard Cooper

Richard,
Colin is correct, "RGB/8*" does indicates your document colour profile does
not match your work space profile. PSE4 works as Colin said. However, you
said you have PSE3. PSE3 works a little differently -- you can only get
"RGB/8*" when you have your color settings set to "Full Color Management".
If you have your color settings anything else, you won't see that.
You asked "So, PSE3 workspace is set to RGB and any image that is not RGB
would be astericked.
Correct?"
No, not quite. First of all, let's go over what "RGB/8" means. The "8" part
is easy. This is just the bit depth of the color channels. In this case 8
bits per channel. The "RGB" part is the color mode of the image. If the
mode were Grayscale this would read "Gray", Indexed mode would read
"Indexed" and so forth. Since yours says "RGB", the image is in RGB mode.
PSE3 only supports a few color modes. RGB is one and Grayscale, Bitmap, and
Indexed are the others. If you try to open an image in an unsupported mode
such as CMYK or LAB, you'll get a popup message saying the mode is
unsupported and there will be a button to allow you to convert to RGB mode.
The "*" on the end has to do with the color profile associated with the
image. Profile and Mode are not the same thing. The mode describes how
colors are represented (RGB says that each color will be represented by a
Red value, a Green value, and a Blue value). By themselves, these are just
numbers in the range of 0 to 255. Determining what those numbers mean is
the role of the profile which decribes how these color values are to be
interpreted. There can be many profiles for the same mode. Adobe RGB and
sRGB are both RGB profiles and are probably the most common. There are
other RGB profiles as well.
When you set your color settings to "Full Color Management", you told PSE3
that you wanted it to use Adobe RGB for the default internal working color
space. However, this setting will also attempt to retain any color space
profile which may be embedded in the image. The "*" tells you that PSE3 did
just that. Your default color space is Adobe RBG but your working color
space is something else -- most likely sRGB, but other RGB profiles could
have been embedded instead. When you see the "*" in PSE3, your work space
profile is not Adobe RGB, you are using the embedded profile.
PSE4 is improved over PSE3 in how it handles color management and profiles
and can do limited conversions between sRGB and Adobe RGB. You might want
to consider upgrading to it if you need to convert Adobe RGB to sRGB often.
Bob

Similar Messages

  • Color management: Adobe RGB 1998 issues in print module

    When printing to a JPEG file from the Print Module, I've noticed that the "Adobe RGB" profile differs substantially from the "Adobe RGB (1998)" profile supplied with Windows.
    When viewed with Photoshop, the "Adobe RGB" images are much more saturated than the image previews from the Lightroom window. Photoshop displays the same "Adobe RGB (1998)" profile for both files.
    I have tried to reinstall Lightroom, but this has not solved the problem.
    It seems that when selecting "Adobe RGB", Lightroom is in fact converting the image to sRGB, but embeds the "Adobe RGB (1998)" profile.
    ICC profile selection: http://julianchoquette.com/fichiers/forum/lightroom-color-a.png
    This will output files that look like the previews in Lightroom: http://julianchoquette.com/fichiers/forum/lightroom-color-b.png
    Profile selection pop-up: http://julianchoquette.com/fichiers/forum/lightroom-color-c.png

    Yeah that is completely different. My guess is that this is the bug I mentioned before. It should not happen but clearly does. It works normally on my system (I just tried again).
    >Note that both dialogs do not display exactly the same name for the Lightroom provided Adobe RGB profile. http://julianchoquette.com/fichiers/forum/lightroom-export-dialog.png
    That's normal and doesn't mean anything. On my computer it actually says "AdobeRGB" without the (1998) that yours shows but I believe that's simply a difference between the Mac and PC version. You can try whether it does the same thing if you select prophoto. But somebody with Vista x64 and LR 2.3 should try the same thing to see if this is a bug specific to the PC version of LR.

  • Adobe RGB (1998) Missmatch

    When I do the following:
    1) Importing an image into Aperture (eater saved in Camera as Adobe RGB (1998) or in Photoshop CS3 with Adobe RGB (1998)
    2) Within Aperture: Edit with Adobe Photoshop CS3
    then Photoshop gives me this Mismatch Window:
          Embedded:  Adobe RGB (1998)
    Working Space:  Adobe RGB (1998)
    OSX 10.5.4 has an Adobe RGB (1998) Profile so does Adobe CS3.
    How can I solve this Mismatch. The same Profile is in two locations.
    a) Library: Application Support: Adobe: Color: Profiles: Recommended: AdobeRGBN1998.icc
    b) System: Library: ColorSync: Profiles: AdobeRGB.icc
    bc

    Odd thatn it would give you a mismatch when they're the same profile.
    In Photoshop go to Edit >> Color Settings
    Make sure RGB is set to Adobe RGB (1998) in the Working Spaces area.
    Also make sure that RGB is set to Preserve Embedded Profiles in the Color Management Policies area. This setting should stop the error messages unless you have "Ask when Opening" checked.
    Thay's all I can think of.
    DLS

  • Missing red color in adobe RGB

    I shoot raw with Nikon Camera. I am having a problem with getting red color in photoshop. . For nef files, I open them in Capture NX2 and then save as jpg in Photoshop.  The jpg image was opened in Photoshop CS5 with a color setting of sRGB, beatiful red color is seen on the screen. When the same.file was opened in in Photoshop CS5 with a color setting of AdobeRGB ("aRBG"). the red color turned into orange color.
    As shown here,  the only difference in color is red hue between sRBG and aRGB.  This is not an isolated case.  All of my pictures look like that.  When printed on Canon i9900 inkjet printer under "Photosbhop Manages Colors setting, red color comes out in orange color.  But printing under Printer Manges Colors" setting, they came to be close to red color.   I do not understand why aRBG does not produce red color.  Could someone explain to me why?
    PS: I could not upload two pictures (sRBG and aRBG).  It seems that inserting image was disabled.

    hummer777 wrote:
    The jpg image was opened in Photoshop CS5 with a color setting of sRGB...
    When printed on Canon i9900 inkjet printer under "Photosbhop Manages Colors setting...
    These statements are vague or functionally incomplete.  For example, are you saving your JPEGs with a color profile embedded?  When you choose "Photoshop Manages Colors", what profile is set for the printer?
    Do you have a basic understanding of color-management?
    The kinds of color shifts you're describing can occur if you are assigning a profile different than the one the RGB values are encoded in, or viewing an image encoded in Adobe RGB with a non-color-managed application.
    The document color profile needs to match the profile used to encode the RGB values, and the application needs to interpret the color profiles of both the document and the output device for the color to be displayed or printed properly.
    May I recommend going out and seeking some primers on basic color management online.  Keep in mind a lot of what's published is sometimes misleading or downright inaccurate, because a lot of people have trouble understanding color management at first.  Try to avoid advice that says "set it like this", but seek the information that describes how color management actually works, so that you can get your mind around it and make your own informed decisions how to set things up.
    -Noel

  • 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.

  • MPB 17" and what Adobe RGB color space coverage I might expect from it

    Hello,
    I am photographer and currently PC user. However, I plan to dive to the Mac’s world.
    Before I become a Mac user, I have few questions.
    Now I think about MacBook Pro 17”, i7 2.66MHz, 8GB RAM, 500 GB 7200rpm HDD and antiglare screen.
    I plan to use additional monitor for photo editing.
    I did search on google about *NVIDIA GeForce GT 330M* and *Adobe RGB color space* it covers, however, it gave me no results related to Mac. The only information about this card and Adobe colors I found is that Sony Vaio use this graphic card and in some forums, one say it covers 98% and in other 100% of Adobe color space which made me wonder what type of screen Vaio have.
    - is MacBook Pro 17” good for photo editing?
    - what % of AdobeRGB color space I might expect from it on my external screen or what % of sRGB colors space it delivers?
    - Is it possible to calibrate Mac’s native screen and external one, use both at the time and have different profiles on each?
    - Tell me anything that would stop me thinking about MBP for photo editing?
    Thank you for your time reading this and hope to find the answers here.

    You should consider posting your questions in the Pro Application section for Aperture. You will bump into more photographers there than you will here. But I will make an attempt at answers:
    whats about Adobe color space?
    No, the MBP screen will not encompass the Adobe Color Space. In fact, few desktop monitors are capable of this.
    does the native MBP screen display full color range the video card is able to produce...
    There really is no limit to the color extremes, which define a color space, as established by a graphics card. So your question is not a well formed question. An old ATI Rage card with 8-bit output would reveal the same color gamut as would the NVIDIA GeForce GT 330M connected to the same display. The gamut is determined by the attached display, not the graphics card.
    ...or connecting external monitor to it’s mini display port would bring much wider color range to my eyes?
    Yes, certainly the potential for that exists. Notebook screens are usually a compromise and can't be expected to compete with a high-end desktop display in many categories, including color gamut. But whether it would bring a "much wider color range to" your eyes is hard to say. It depends on what type of external display is in use.

  • Adobe RGB vs. sRGB

    In iPhoto 5, when importing photos from my Canon 20D with the color space set to Adobe RBG, JPEGS look washed out. Raw images (.cr2) look fine. If I set the camera to sRGB, both the JPEGS and Raw images look OK - the JPEGS are not washed out. Has this issue been fixed in iPhoto 6? I want to use the Adobe RGB to get the larger color space, as the camera supports it, but do I have to always use raw images to import in iPhoto? (Photoshop Elements handles this fine....)

    The »s« in srgb supposedly stands for »standard« (though »small« or »s..t« have also been mentioned) and this color-space is so small as to be representable without clipping on most monitors, so it’s recommended to be used for internet-work.
    AdobeRGB on the other hand is much larger and intended for professional image-editing.
    If You wonder what small and large mean in this context just create an rgb-document with a Spectrum-gradient and assign (not convert) different profiles to it and see how the appearance of pixels of any given rgb-value change.
    Or compare the two profiles in ColorSync Utility (in the Utilities-folder).
    Of course working in the larger space can cause problems when an image has to be output in a smaller space (as many/most offset printing spaces are), but soft-proofing can help recognize them in time.
    Anyway reading up on color management should do You no harm.
    It would seem advisable to shoot RAW-images if Your camera offers that option.

  • SRGB vs Adobe RGB

    What the heck is the difference between sRGB vs Adobe RGB?
    Do I have to reset this in my camera too?
    I have a Canon 5D  Mark 11
       Thanks, Penni

    The »s« in srgb supposedly stands for »standard« (though »small« or »s..t« have also been mentioned) and this color-space is so small as to be representable without clipping on most monitors, so it’s recommended to be used for internet-work.
    AdobeRGB on the other hand is much larger and intended for professional image-editing.
    If You wonder what small and large mean in this context just create an rgb-document with a Spectrum-gradient and assign (not convert) different profiles to it and see how the appearance of pixels of any given rgb-value change.
    Or compare the two profiles in ColorSync Utility (in the Utilities-folder).
    Of course working in the larger space can cause problems when an image has to be output in a smaller space (as many/most offset printing spaces are), but soft-proofing can help recognize them in time.
    Anyway reading up on color management should do You no harm.
    It would seem advisable to shoot RAW-images if Your camera offers that option.

  • Can't save in Adobe RGB, Elements 10

    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.

    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
    point but...
    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"
    printer.
    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!

  • Adobe RGB to SRGB export Lightroom CC

    Hello
    I am getting quite the discoloration when exporting my Adobe RGB photos into SRGB with Lightroom.
    Some colors like blue gets heavily saturated, while reds/browns hidden inside in grass and foliage gets an ugly boost, making grass look very unatural.
    This color shift is visible in both Windows Explorer, XN Viewer and when i import the exported photos into Lightroom itself. Adobe RGB exports looks great. SRGB looks whacky.
    Is there any trick i can use to get more accurate color conversion in Lightroom? Right now its kind of Texas.

    I have put your file through my Lr setup and this what I found.
    1) Paper gamut warnings are very different from yours, noticeably I don't get any warning on the top left corner of the blue sky and get warnings is less of your backpack than you do
    2) I virtually get no monitor warnings (just some gamut warnings on the backpack)
    3) This is a screenshot of an AdobeRGB export and sRGB export (100% quality and 300 pixels per inch) [I have sent you the originals via Dropbox, please see private message]
    Perhaps the sRGB is a bit darker but the there isn't a huge difference between the sky.
    It could be your profile and/or your wide gamut display (as @twenty_one has said). My display is a Samsung S27B970, calibrated 2 days ago with an i1 Display Pro from x-Rite.
    Have a read through Tony Jay replies to this recent thread Soft proofing sRGB on wide gamut monitor - Lightroom Forums. It might be worth to soft proof using your monitor profile, which is what Tony Jay is doing for image 5 in his 1st reply to that thread.
    Edit: Tony Jay replies are a year old, so not that recent.

  • Book photos sRGB or Adobe RGB?

    Which profile should the images for a book have?
    sRGB or Adobe RGB?

    I am sorry but I do not think you really understood what profiles are for. An image (be it a JPEG, TIFF or even PDF, since it DISPLAYS something) MUST have metainformation on what its color values mean independently of what device you want to display them on. Without that info a PDF output would be caothic and unforseeable, since each device would interpret it according to the device's defaults.
    That metainformation, combined with the information of how a device displays color (that is, a calibrated screen or printer), makes it possible to display images in several devices as close as possible to each other and to its supposed abstract colors (real colors, independent of device). If there is no metainformation (a profile) on what those RGB or CMYK values mean independently of any device, you are simply subject to the color shifting that any device is naturally subject to cause when not instructed on how to correct it. I.e. if a pixel in your image is a neutral gray -not color tinted- and you display it on a screen that shifts to red, you can still make it show a neutral gray if the color engine of your software shifts the image to the opposite color before displaying it. The software accomplishes that by combining the device profile you created when calibrating the device -or at least, by associating it to a default profile intended for that device- and the profile of the image. This is an oversimplification, since profiles in images deal with quite more than just color shifting.
    PDF's are intended to be portable (hence, what the P in PDF stands for) and, then, must have a way of guaranteeing that color is reproduced as faithfully as the displaying device allows to. PDFs without information on profiles would be useless to their aim without this metainformation.
    So PDFs DO STORE profile information.
    The only catch up on this is that PDFs can contain several images, so in fact PDFs do not embed a single profile to govern all images inside it, but one profile for each embedded image.
    Quoting you, then, those embedded profiles are what make the point of the PDF - " a self contained freely readable document in its own format" *that displays the same colors in all devices* (* = as close as the device is able to, as long as the device is calibrated, and as long as the device's software also is profile-aware; which can apply pretty much to any computer).
    Answering the question of the first poster, I'd go for sRGB, since that is the color gamut most cameras are calibrated for. While AdobeRGB is wider, you will probably not be getting a wider color gamut since your camera did not capture it in the first place. Besides, not all printing services have a decent color workflow, and some will ignore the profiles you embedded (which is catastrophic since that means they will interpret the color values in your photos according to another supposed profile -because by definition, always that there is an interpretation of color values into an output, a theoretical profile is being used even if not aware of that, since that is what a profile does: turn abstract -digital- color values into real colors). And since sRGB is quite more used than AdobeRGB, their device will most probably output closer to the former. AdobeRGB images interpreted in an sRGB color space become dramatically desaturated.
    I hope that helps. If you need me to be more explicit on something, just ask.

  • Why does PS 7 not recognize Adobe RGB files?

    I have an Olympus E-620 DSLR. When I set the color space in the camera to sRGB, after downloading the images, when I click to open them in Photoshop 7, the images are properly identified as sRGB files. When I set the color space in the camera to Adobe RGB, Photoshop does not recognize the format. Please see the picture below.
    Question 1: Why does Photoshop not recognize the Adobe RGB files?
    Question 2: What can I do to make Photoshop recognize Adobe RGB files?
    Question 3: If I assign in Photoshop the Adobe RGB profile to an unrecognized Adobe RGB file, does that even make any sense? Is the "extra data" that Adobe RGB offers compared to sRB even there even if the profile is not recognized in the first place?
    I am very grateful for any comments and advice!

    Buko. wrote:
    Are you saying that the file is really AdobeRGB and because PS7 is so old its defaulting to sRGB? which is why you are assigning?
    Yes...if the file name starts with an underscore _IMG12345 then the image is indeed in Adobe RGB. It's a failure and limitation of the EXIF spec that only allows for two different EXIF tags relating to color space...either sRGB or "unspecified".
    Since the camera makers wanted to offer Adobe RGB as a color space choice in camera JPEGs, the underscore was the ONLY way to say whether a file was in sRGB or Adobe RGB. Note that camera JPEGs do NOT have an embedded profiles, just the EXIF tag. And yes, Photoshop 7 is/was too old to understand the Adobe RGB underscore color space.
    A lot of stuff has changed (sometimes radically) since that piece of software was released...heck, there wasn't even a Camera Raw until about 9 months AFTER Photoshop 7 was released. Camera Raw 1.0 was released Feb. 19th, 2003, Photoshop 7 was released about April 2002.

  • Can you show slideshow within Lightroom 4.4 in Adobe RGB color space?

    Can you show slideshow within Lightroom 4.4 (not export out from LR) in Adobe RGB color space provided that you are using a wide gamut monitor which is capable and hardware calibrated & profiled to show such color space?
    If this is possible, what is required to do so in Windows 8 and i7-4770 & HD Graphics 4600 platform or does LR take care of it automatically?
    This is very basic question, however, I could not find a clear answer/info from LR documentation, so wish that someone can advice.

    Those settings are probably stored in a plist somewhere in ~/Library/Preferences. If you can locate the appropriate file, you should be able to copy it to all the network user folders.

  • RAW output to an adobe rgb and srgb look identical in bridge but different in PS on wide gamut monitor.

    Photoshop CS6.  Wide gamut HP LP2475w monitor.  Spider 3 Elite calibrated.  Working space adobe rgb.  When outputting a raw to Adobe RGB jpg it looks a bit whacked with color blotches/jumps in PS.  The sRGB of it does not.  BUT......in bridge they look identical.  The adobe rgb jpg almost acts like viewing an image in a non-color aware browser on a wide gamut monitor.  Like bridge shows it right but photoshop is showing it whacked out.  I can't tell what is lying to me and if there is even a problem with the image.  Here is a half second 2 frame gif alternating between the two from a screen cap.  http://www.extremeinstability.com/hmm.gif  Abrupt blotchy color changes with the adobe rgb when viewed in photoshop.  And again, when you look at the two images in bridge they don't show that, they look identical.
    Thanks,
    Mike

    I guess I now learned that Bridge only generates srgb previews.  So I see them the same in there I guess.  Looks like it comes down to the adobe space and jpg.  Oddly enough an 8 bit adobe tiff covers it fine without breaking up.  Can see the 3 on this gif.  http://www.extremeinstability.com/3.gif 

  • Converting RGB images (sRGB or Adobe RGB) to 709 color space.

    I'm trying to determine the correct way to convert RGB images (sRGB or Adobe RGB) to 709 color space.  I can't just use the "covert to profile" function to do this because it does not produce results that fall within the 16 to 235 range that 709 dictates.  I've read that you can simply use the "Levels" adjustment and change the output levels to 16 to 235.  While this would clearly compress the luminance to the correct range, I'm not entirely clear if the end result would be a proper conversion (i.e. if color and gamma, for example, would be technically correct.)
    I noticed that converting the profile to "HDTV (Rec. 709)" does alter the image, so I'm wondering what the result would be if I did both this AND used the levels control to compress the output range to 16 to 235.
    Thanks for any feedback on this.

    (1)
    http://en.wikipedia.org/wiki/Rec._709
    (2)
    http://en.wikipedia.org/wiki/Rec._601
    The transfer functions for Rec.709 (1) refer to the range [0..1] or for 8 bits per pixel [0...255].
    It seems that the clipping, black=16 and white=235 has to happen after the application of the
    transfer function. If this should be true, then we don't have a level compression but a level
    clipping at both ends, as already for Rec.601 (2), like here:
    The ICC-Profile HDTV(Rec.709) in Photoshop contains the primaries and the white point
    (both like that in sRGB) and the transfer functions for [0..1], coded by a LUT with high resolution,
    as found by Profile Inspector. There is no clipping.
    By the way, that`s the internal profile name, I don't know the file name of the profile.
    Softproofing, source in sRGB, target HDTV(Rec.709), without clipping:
    With numbers not preserved: no change of the appearance, as expected.
    With numbers preserved: shows the effect of different effective gammas. 
    Your questions are very clear and I'm not sure whether my comments help. The information
    in the internet is not convincing.
    Best regards --Gernot Hoffmann

Maybe you are looking for

  • ITunes can no longer play CDs, not sure why

    Something very strange. For some reason iTunes no longer will play or import audio CDs. I have never had a problem before this playing or importing CDs - I just imported 3 CDs last weekend. If I insert a CD, iTunes never even mounts it. If I open the

  • IDOC XML Message status:029

    Hi all, in RSXMB_SHOW_STATUS i have 21.000 messages in status 29. How can i delete them ? Regards

  • My app store app is missing. Where can i find it??

    How to find the app store app and Get it back om my i pad?

  • What is the latest Safari revision for Mac OSX 10.4.11

    I have a vintage Mac G3 B/W Desktop PPC, which still operates perfectly.  But, at times Safari 4.1.3. periodically crashes.  Is there a later revision that I can upgrade to?  Software Update says the computer is up to date.

  • FORALL & INSERT

    I am using FORALL to insert all the records in a plsql table to DB table. The order in which the columns are present in the PLSQL table is different from the order in which the columns are present in the DB table. Is there anyway to specify particula