Swatches go funny in ProPhoto RGB mode

I am running CS4 on XP 32 bit, in case that is relevant.
For years my working RGB has been AdobeRGB 98. Life has been fine. Recently I have changed my preferences in LR to use ProPhoto RGB as my destination color space when opening images in Photoshop.
I have logo colors which I have used for years which are in my swatches.
I have noticed that whenever I open a file in ProPhoto RGB, the logo colors are wildly skewed. The color of the image from LR is fine, but the swatches go wacky, so if I use my logo brush with the logo colors from the swatches, they are way off.
I would have thought that the color of a swatch was maintained if it remained in the gamut of the color space of any given image. It appears that this is not the case. If I had to guess, I would say that it is maintaining the numerical values of the colors, and since ProPhoto is so much larger that AdobeRGB that it is skewing the colors madly.
Is there a solution to this? Do I need to regenerate my swatches by opening a ProPhoto image and then opening my logo file, dragging the logo into the ProPhoto image and then adding the relevant colors to the swatches?

Anyone?

Similar Messages

  • Why do my custom swatches revert to RGB mode?

    Hi all,
    I'm a newbie to Illustrator. I have a few questions:
    When I create custom swatches, I choose the CYMK option in the drop down box. However, these swatches are appearing as "RGB" mode in my swatch palette. Why is that? How do I ensure my custom swatches stay in CMYK mode?
    When I later view the CMYK code for the swatches, I see that their numbers are skewed a little (for example, 34 may be 35 or 36, etc). Why is that?

    When you create a new document, make sure the color mode of the document matches with the swatch color mode. i.e if you're creating a new document in RGB and then using a CMYK swatch then the numbers will be converted to RGB. Make sure the document is also created in CMYK color mode by expanding the advaced options in new document creation dialog box.

  • Color problem with ProPhoto RGB color space

    Hi, everyone,
    I have wery special problem I think. I use MacBook pro 15" with retina display, adobe Photoshop CC and when I export RAW (from Nikon D7000) from Lightroom 5 to Photoshop with settings: 16 bit TIF, color space: ProPhoto RGB I have a problem with displaying the correct colors. As you can see in this picture:
    My problem are some "green" artefacts in absolutely black and white picture. I tried myself to solve this problem and found the following facts: when I convert picture into Adobe RGB or sRGB color space is everything OK - without green artefacts.
    But here is one important fact: I have calibrated monitor by datacolor spyder4elite and problem with ProPhoto RGB incorrect color displaying is only when the color calibration configuration is loaded. When I change my display calibration to standard apple color LCD profile than is everything OK.
    But using uncalibrated monitor and also Adobe RGB color space are no right solutions for me.
    My question is why I have problem with displaying ProPhoto RGB color space in photoshop under calibrated monitor profile and can anybody help me please?
    Thanks for answers.

    That's a classic example of the basic problem with 16 bit color. There is no solution that I know of.

  • Images opened in ProPhoto RGB has heavy banding

    HI,
    I am a photographer, and I shoot Canon 5D and 1Dmk3, shooting RAW and in AdobeRGB.
    If I open a correctly exposed CR2 file in Camera Raw, applying no changes at all to the photo, open it as ProPhotoRGB 16-bit, I get heavy banding in the shadows and gradients when the image opens in PS.
    If I then try to use a brush (normal soft tip), I also get heavy banding and posterization on the transitions between the different shades of that brush.
    I have double checked that my image, when open in PS, is indeed 16 bit ProPhoto RGB.
    If I open the same image in Camera Raw, but change the color space to Adobe RGB, these issues are gone!
    Late 2013 27" iMac with 24GB RAM, 750GTX with 2GB VRAM.
    RUnning OS X Yosemite 10.10 and latest PS CC 2014.
    DIsplay is calibrated, and these issues does not show when opening the same CR2 in Aperture.
    ANy ideas.

    I Should add, that if I create a new empty document with the same settings (ProPhotoRGB/16bit/300dpi), the same brush works fine.
    I recently did a shoot where I used a dark grey seamless background, and any given image looks great in Lightroom and ACR (imported as DNG), but when editing the same image in PS with the settings above, I get banding, pixelation, and posterization in the shadows, and in the light falloff on the grey background.
    Using raw files directly makes no difference from a DNG version...
    Again, change just the color space from ProPhoto to AdobeRGB, issue goes away most of the time.

  • Why does Lightroom (and Photoshop) use AdobeRGB and/or ProPhoto RGB as default color spaces, when most monitors are standard gamut (sRGB) and cannot display the benefits of those wider gamuts?

    I've asked this in a couple other places online as I try to wrap my head around color management, but the answer continues to elude me. That, or I've had it explained and I just didn't comprehend. So I continue. My confusion is this: everywhere it seems, experts and gurus and teachers and generally good, kind people of knowledge claim the benefits (in most instances, though not all) of working in AdobeRGB and ProPhoto RGB. And yet nobody seems to mention that the majority of people - including presumably many of those championing the wider gamut color spaces - are working on standard gamut displays. And to my mind, this is a huge oversight. What it means is, at best, those working this way are seeing nothing different than photos edited/output in sRGB, because [fortunately] the photos they took didn't include colors that exceeded sRGB's real estate. But at worst, they're editing blind, and probably messing up their work. That landscape they shot with all those lush greens that sRGB can't handle? Well, if they're working in AdobeRGB on a standard gamut display, they can't see those greens either. So, as I understand it, the color managed software is going to algorithmically reign in that wild green and bring it down to sRGB's turf (and this I believe is where relative and perceptual rendering intents come into play), and give them the best approximation, within the display's gamut capabilities. But now this person is editing thinking they're in AdobeRGB, thinking that green is AdobeRGB's green, but it's not. So any changes they make to this image, they're making to an image that's displaying to their eyes as sRGB, even if the color space is, technically, AdobeRGB. So they save, output this image as an AdobeRGB file, unaware that [they] altered it seeing inaccurate color. The person who opens this file on a wide gamut monitor, in the appropriate (wide gamut) color space, is now going to see this image "accurately" for the first time. Only it was edited by someone who hadn't seen it accurately. So who know what it looks like. And if the person who edited it is there, they'd be like, "wait, that's not what I sent you!"
    Am I wrong? I feel like I'm in the Twilight Zone. I shoot everything RAW, and I someday would love to see these photos opened up in a nice, big color space. And since they're RAW, I will, and probably not too far in the future. But right now I export everything to sRGB, because - internet standards aside - I don't know anybody who I'd share my photos with, who has a wide gamut monitor. I mean, as far as I know, most standard gamut monitors can't even display 100% sRGB! I just bought a really nice QHD display marketed toward design and photography professionals, and I don't think it's 100. I thought of getting the wide gamut version, but was advised to stay away because so much of my day-to-day usage would be with things that didn't utilize those gamuts, and generally speaking, my colors would be off. So I went with the standard gamut, like 99% of everybody else.
    So what should I do? As it is, I have my Photoshop color space set to sRGB. I just read that Lightroom as its default uses ProPhoto in the Develop module, and AdobeRGB in the Library (for previews and such).
    Thanks for any help!
    Michael

    Okay. Going bigger is better, do so when you can (in 16-bit). Darn, those TIFs are big though. So, ideally, one really doesn't want to take the picture to Photoshop until one has to, right? Because as long as it's in LR, it's going to be a comparatively small file (a dozen or two MBs vs say 150 as a TIF). And doesn't LR's develop module use the same 'engine' or something, as ACR plug-in? So if your adjustments are basic, able to be done in either LR Develop, or PS ACR, all things being equal, choose to stay in LR?
    ssprengel Apr 28, 2015 9:40 PM
    PS RGB Workspace:  ProPhotoRGB and I convert any 8-bit documents to 16-bit before doing any adjustments.
    Why does one convert 8-bit pics to 16-bit? Not sure if this is an apt comparison, but it seems to me that that's kind of like upscaling, in video. Which I've always taken to mean adding redundant information to a file so that it 'fits' the larger canvas, but to no material improvement. In the case of video, I think I'd rather watch a 1080p movie on an HD (1080) screen (here I go again with my pixel-to-pixel prejudice), than watch a 1080p movie on a 4K TV, upscaled. But I'm ready to be wrong here, too. Maybe there would be no discernible difference? Maybe even though the source material were 1080p, I could still sit closer to the 4K TV, because of the smaller and more densely packed array of pixels. Or maybe I only get that benefit when it's a 4K picture on a 4K screen? Anyway, this is probably a different can of worms. I'm assuming that in the case of photo editing, converting from 8 to 16-bit allows one more room to work before bad things start to happen?
    I'm recent to Lightroom and still in the process of organizing from Aperture. Being forced to "this is your life" through all the years (I don't recommend!), I realize probably all of my pictures older than 7 years ago are jpeg, and probably low-fi at that. I'm wondering how I should handle them, if and when I do. I'm noting your settings, ssprengel.
    ssprengel Apr 28, 2015 9:40 PM
    I save my PS intermediate or final master copy of my work as a 16-bit TIF still in the ProPhotoRGB, and only when I'm ready to share the image do I convert to sRGB then 8-bits, in that order, then do File / Save As: Format=JPG.
    Part of the same question, I guess - why convert back to 8-bits? Is it for the recipient?  Do some machines not read 16-bit? Something else?
    For those of you working in these larger color spaces and not working with a wide gamut display, I'd love to know if there are any reasons you choose not to. Because I guess my biggest concern in all of this has been tied to what we're potentially losing by not seeing the breadth of the color space we work in represented while making value adjustments to our images. Based on what several have said here, it seems that the instances when our displays are unable to represent something as intended are infrequent, and when they do arise, they're usually not extreme.
    Simon G E Garrett Apr 29, 2015 4:57 AM
    With 8 bits, there are 256 possible values.  If you use those 8 bits to cover a wider range of colours, then the difference between two adjacent values - between 100 and 101, say - is a larger difference in colour.  With ProPhoto RGB in 8-bits there is a chance that this is visible, so a smooth colour wedge might look like a staircase.  Hence ProPhoto RGB files might need to be kept as 16-bit TIFs, which of course are much, much bigger than 8-bit jpegs.
    Over the course of my 'studies' I came across a side-by-side comparison of either two color spaces and how they handled value gradations, or 8-bit vs 16-bit in the same color space. One was a very smooth gradient, and the other was more like a series of columns, or as you say, a staircase. Maybe it was comparing sRGB with AdobeRGB, both as 8-bit. And how they handled the same "section" of value change. They're both working with 256 choices, right? So there might be some instances where, in 8-bit, the (numerically) same segment of values is smoother in sRGB than in AdobeRGB, no? Because of the example Simon illustrated above?
    Oh, also -- in my Lumix LX100 the options for color space are sRGB or AdobeRGB. Am I correct to say that when I'm shooting RAW, these are irrelevant or ignored? I know there are instances (certain camera effects) where the camera forces the shot as a jpeg, and usually in that instance I believe it will be forced sRGB.
    Thanks again. I think it's time to change some settings..

  • PS CS with color space set to Prophoto RGB - will ACR change embedded profiles?

    Probably a foolish question but my problem is that I have a mixture of files:
    My own files (all initially RAW (NEF) which I import into ACR as 16 bit Prophoto RGB ).
    Files from family members and from slide scanning performed elsewhere - they are in 2 groups:
    The first of these from elsewhere acquired files were all JPEGs that I converted to Tiffs in Bridge before setting out to edit them-- all unfortunately 8bit and sRGB.
    The scanned files were scanned as tiffs but also 8bit and sRGB.
    My normal procedure is that I in ACR I have set the files to 16 bit and Prophoto RGB. In PS the same but also to preserve embedded profiles. I have the impression that working with the "foreign" files in 16 bit does give me more room for editing but that I should continue with the embedded profiles.
    Is there a way to ensure that the color profiles are not changed in ACR even if the line in the middle below says 16 bit Prophoto RGB (I have PS CS5). I would hate to have to change this line each time I view a file in ACR. I would hate more to loose the editing facilities in ACR as these acquired files do need som special care before they are mixed with my own in our family albums. I prefer the 16 bit Prophoto RGB option for my own files as I like to play with them - i.e. apart from including them in Photo Albums.
    I do see that a logical way is to process all the acquired files before going to my own files but it is so much more practical for me to work with a mixture of the files sorted chronologically - a year or month at the time.
    I would even consider getting an upgrade to CS6 if this version could help me.
    Can someone enligthen me?
    Thanks, Git

    Hi, Tom.
    The real issue here is getting accurate color. You can't get accurate color by setting your monitor profile to sRGB. sRGB is a virtual color space that doesn't describe the exact color gamut of any physical device. But, in order to display sRGB or any color space accurately, you need to get a characterization of your monitor.
    Here is an AWESOME way to get access to a colorimeter: http://www.lensrentals.com/rent/pantone-huey-colorimeter Looks like for $32 you can rent this for a week. Go in on this with a friend and profile both of your monitors and hardly pay a thing. If you have a reasonably good quality LCD monitor, this custom profile you make will be fairly accurate for many months. At the very least, this is way more accurate than having no regular calibration at all.
    Hope this helps!
    Bret

  • Weird bug?  Transparent background is black instead of checkerboard in RGB mode

    If I try to make a new RGB document with the Background Contents set to Transparent the canvas is filled with black instead of the checkboard pattern.  However over in the Layers window the little icon for the layer shows it as transparent with the checkerboard. In the Channels window it also appears transparent, and if I click on one of the channels which selects just one of them the canvas changes from black to the checkboard.  If I click on the RGB channel at the top the canvas changes to black again.
    Why is this happening and how do I fix it?
    If I open a new document in CMYK I get the checkerboard like I'm supposed to.
    I bought a new PC a few days ago and this is a fresh install of Adobe CS4 on Windows 7.  Photoshop is updated to version 11.0.2.
    I could swear this wasn't happening a couple of days ago when I first installed it, and it never happened on my old XP computer. 
    edit to add: all files show a black background in RGB mode instead of the checkerboard pattern, not just when creating a new document.

    What are the Photoshop > Preferences > Transparency & Gamut > Transparency Settings?
    Boilerplate-text:
    Does turning off OpenGL in the Performance Preferences and restarting Photoshop have any bearing on the issue?
    Other than that are Photoshop and OS fully updated and have you performed the usual trouble-shooting routines (trashing prefs by keeping command-alt-shift/ctrl-alt-shift pressed while starting Photoshop, 3rd party plug-ins deactivation, system maintenance, font validation, etc.)?

  • Open File in RGB mode

    How to Open file in RGB mode in illustrator using Javascript

    if you have CS6 or above you can executeMenuCommand
    app.executeMenuCommand ('doc-color-rgb');
    or
    app.executeMenuCommand ('doc-color-cmyk');
    this will switch the active documents colour mode

  • Why are my RGB colours dull in illustrator? The doc is set to RGB mode.

    Hi,
    I'm designing in Illustrator, RGB mode and using RGB colours. However, when I export to png, the colours in the png file are bright and vivid (the correct rgb colours I assume) but in illustrator they are dull. It's making it very hard for me as I actually want the duller colours, not the really bright ones. Attached is a screen shot to show the difference. Left is png, right is ai.

    ah, thanks. I never knew that option was there. I just thought that if i'm working with RGB and using RGB colours, then they should output as the same?

  • Does firefox 5 support wide gamut or profiled monitors or sRGB, Adobe RGB, or ProPhoto RGB files?

    How does ff5 support sRGB, AdobeRGB, and or ProPhoto RGB? How does ff5 support profiled monitors?

    How does ff5 support sRGB, AdobeRGB, and or ProPhoto RGB? How does ff5 support profiled monitors?

  • Adjusting Black (K) while in RGB mode?

    Ok, so basically I'm wokring on an image in RGB mode, and I have my INFO box open, and I have the sample picker #1 and #2 set to display CMYK values.
    I'm not sure if many people realize that even if you're in RGB mode you can actually view other color information, including CMYK, within the INFO Box. If you click on the little Eye Dropper icons located within the INFO Box, it allows you to choose between different color info to be displayed, i.e. LAB, HSB, Grayscale, RGB, CMYK, etc, regardless of the color mode you're actually in.
    So I'm working on an RGB image, but I'm viewing the color info in CMYK, and my question is how do I directly adjust the K, or black, wihtin an RGB image, if I don't actually have the Black Channel available while I'm using Curves or Levels for example?
    I tried using the 'Brightness and Contrast' adjustment, but it affects everything else as well, not just the K/Black.

    I'm not really trying to affect the 'Black Channel,' I know it's confusing. In fact, technically, there is no Black Channel to speak of, because I am in fact in RGB mode.
    Basically I was just trying to increase K, Black, in the INFO Box, from 0 to 4, under the #2 sampler, without affecting CMY. Because my INFO Box, is set to read CMYK values, but I am still in RGB mode. So I'm not really trying to affect the Black Channel, I'm just trying to affect what's being read as Black, while I'm still in RGB mode.
    Right now, it's reading C=11, M=42, Y=51, K=0, and I wanted to change K to 4 without affecting the other colors, without affecting C, M and Y. 
    I just wanted to see if that was at all possible.
    I don't think using another color profile is the path I want to go down. Right now I'm just using the standard sRGB.
    I actually had to look up GCR, grey component replacement, and I don't think that's what I'm looking for either.
    I just want to make a move in Photoshop that would accomplish changing the Black readout from 0 to 4 with out affecting CMY, or at least minimally affecting CMY.
    But I guess it's not really possible at all, using the adjustments and/or the blend modes? I've tried a couple of things and nothing seems to work really.

  • Why do ProPhoto RGB files "Saved For Web" with "Convert to sRGB" selected show up as "untagged" after saving?

    For years I've managed my entire workflow in sRGB, thinking if I can make an image look good in sRGB, it's golden in any other color space.  Lately, however, I've begun shooting in Adobe RGB and mastering my images in ProPhoto RGB.  When I save an image for the web, using the "Save for Web" menu item, and check the box that says "Convert to sRGB", the images look fine, but when I check the color profile in Bridge, it says "Untagged", not sRGB IEC61966-2.1, as I'm used to.  Am I doing something wrong, or is this normal? 
    Thanks!

    I'm using Photoshop cc2014, Mac mavericks.  I'm not near my computer right now, but if memory serves, both Convert and Embed are checked.  Wouldn't bet my life on it, but I'm pretty sure.  I'll definitely confirm tomorrow.  Thanks!
    Sent from my iPad

  • Missing ProPhoto RGB and Mini Bridge in CS5 version 12.0.4??

    I am missing the ProPhoto RGB in the Color Settings in Photoshop CS5.
    Also the Mini  Bridge in Photoshop CS5 just shows Waiting for Bridge, but never retrieves anything. I did a video to show the problems in detail at:
    Thank you for any help you can give.
    Windows 7 Ultimate 64 Bit, Intel i5, 4GB Ram, ATI Radeon 5400

    Thanks for you information.
    I have installed all the pre-requiste softwares and packages as per this link
    www.oracle-base.com/articles/apps/OracleApps_12_InstallationOnOEL45.php.
    installdbf.log --> exited with 0
    ApplyDatabase_05130109.log --> ApplyDatabase Completed Successfully.
    adconfig.log --> AutoConfig is exiting with status 0
    NetServiceHandler.log --> adgentns.pl exiting with status 0
    I see the following error message at the end of this log file appsutil/log/$CONTEXT_NAME/MMDDHHMM.log.
    FINISHED INSTALL PHASE : DATABASE : Tue May 13 01:57:39 EDT 2008
    /training/trn/oracle/TRN1/db/tech_st/10.2.0/temp/TRN1_varsha/adrundb.sh has succeeded
    java.lang.NoClassDefFoundError: oracle/apps/ad/tools/configuration/NetServiceHandler
    Please refer to the remaining logs on applications node at - /training/trn/oracle/TRN1/inst/apps/TRN1_varsha/logs/05130035.log
    I have installed OEL4 and made the requiredchanges
    Does this mean you have already installed all
    pre-req. software/packages?
    It completed step 1 100% and during step 2 around66%
    Please review the following log files for further
    details about the error:
    <RDBMS
    ORACLE_HOME>/appsutil/log/$CONTEXT_NAME/installdbf.log
    <RDBMS
    ORACLE_HOME>/appsutil/log/$CONTEXT_NAME/adcrdb_<SID>.l
    og
    <RDBMS
    ORACLE_HOME>/appsutil/log$CONTEXT_NAME/ApplyDatabase_<
    MMDDHHMM>.log
    <RDBMS
    ORACLE_HOME>/appsutil/log/$CONTEXT_NAME/<MMDDHHMM>/adc
    onfig.log
    <RDBMS
    ORACLE_HOME>/appsutil/log/$CONTEXT_NAME/<MMDDHHMM>/Net
    ServiceHandler.log

  • CS5 doesn't open/process ProPhoto RGB correctly...

    I'm new to Photoshop, so I apologize if the answer is obvious!
    When opening RAW images from LR 3.3 to edit in CS5, it does not seem able  to  support the ProPhoto RGB color profile, even after switching the   working space to ProPhoto RGB in CS5. It always ends up looking like   this:
    I'm  only able to open up the photo in CS5 when I change the color space  in  LR's "External Editing" preferences to sRGB. I guess I could live  with  that, but I don't understand why my photos won't open in ProPhoto  RGB  as this is the profile I'd like to use. It shouldn't be this   complicated, they're both by Adobe, right? Ahhhh!
    Anyone have any insight?

    Voilà. As you can see, the image looks normal in the layers tab... not sure what the problem could be...

  • Photoshop Elements 16 bit/ProPhoto RGB  ?

    At this point in time I don't believe PSE10 or indeed 11 supports 16 bit working or ProPhoto RGB. This is an issue when transferring images from Lightroom for editing in Layers etc. I currently use Photoshop CC for this purpose, which is great but to be honest complete overkill for my purposes. PSE would be absolutley spot in if it could handle editing in 16 bit and/or ProPhoto RGB.
    Can anyone shed any light on future releases of PSE and if/when this functionality will be included.
    I know these facilities aren't there at the moment.
    Thanks.

    LyndonPshop wrote:
    At this point in time I don't believe PSE10 or indeed 11 supports 16 bit working or ProPhoto RGB.
    16 bits : PSE10 and PSE11 support 16 bits, except for layers and local tools.
    Both can handle native Prophoto files. Just try it with Prophoto files from Lightroom. You are limited to sRGB or aRGB if you are working from your camera's raws or jpegs directly in PSE, but since you have Lightroom, you don't miss anything.
    But the real answer is that advanced Elements users without LR do use the ACR module, which works in 16 bits and Prophoto (from raws or jpegs). Nearly all adjustments where 16 bits is important to avoid posterization can be done in ACR. Anyway all your output devices (display or printer) will require 8 bits and sRGB or aRGB.

Maybe you are looking for