Converting to another color space flattens image (forgot about the option in the dialog)

I have been working on a layered Pro Photo RGB tif document which I want to keep layered, but when I go to Edit>convert to profile>sRGB this flattens the image. I also tried it converting to Adobe RGB and the same thing happened. This didn't happen in previous versions.
Windows 7, 64 bit.

See if unchecking Flatten Image to Preserve Appearance at the bottom of the convert profile dialog makes a difference.

Similar Messages

  • HT5312 Hey I forgot about the questions and answers, and when the balance of $ 15 and I want to buy software from iTunes for regrettably I could not and I were sent to you many not thrown a response, or retrieve answers frankly tired or help me and send E

    hey i forgot about the question and answers and when the balance of 15d and i want to buy software form i tunse for regettably i could

    The page that you posted from has instructions for how to reset them i.e. if you have a rescue email address (which is not the same thing as an alternate email address) set up on your account then steps 1 to 5 half-way down that page should give you a reset link.
    If you don't have a rescue email address (you won't be able to add one until you can answer your questions) then you will need to contact iTunes Support / Apple in your country to get the questions reset (these are user-to-user forums).
    Contacting Apple about account security : http://support.apple.com/kb/HT5699
    When they've been reset (and if you don't already have a rescue email address) you can then use the steps half-way down the HT5312 page that you posted from to add a rescue email address for potential future use

  • I've been a GCU member for awhile. Forgot about the 3 game limit. How can I fix it?

    I've been a GCU member for over 2 years. I forgot about the purchase limit on new games. I grabbed 4 copies of a game yesterday, and they shipped today. At some point today while I was spacing out I remembered about the limit for the program. What can I do for this, can I just return the 4th copy or will that not help?
    If a mod could get back to me about this I would appreciate it.

    Hello johnciti321,
    We appreciate you taking the time to contact us about the Gamers Club Unlocked benefits.  I'd advise you to return one copy of the game as soon as possible.  If you notice any issues with your membership after the return, please don't hesitate to send me a private message by clicking the blue box at the end of my signature. I'll be happy to check your account or you can view the current status of your account by clicking here and logging in.  After you log in, please click the "Rewards" page.  Your status and expiration should appear on the right side of the page.  
    Blake|Social Media Specialist | Best Buy® Corporate
     Private Message

  • How can I convert to NTSC color space?

    I'm developing graphics for a Roku application which requires that colors be broadcast safe in the SDTV NTSC color space. For instance, I cannot have true white or true black colors. They are not allowed.
    There is an RGB color space available. When I create a new document in CS6, I can select that profile as the color space. However, I am still able to paste in images that have pure white in them. When I save the document for web & devices, it still saves with the pure white.
    I'm positive I've done this conversion in the past before, but I cannot get it working in CS6. I've tried going to Edit -> Assign Profile and Edit -> Convert to Profile, but in both cases the colors I am dealing with still end up pure white.
    How can this be done?

    Hi,
    See if Filter>Video>NTSC Colors makes any difference.

  • Converting to different color space

    Dear Color Management Guru's,
    I have a question regarding converting digital files between color spaces. Is it correct to convert a file from a large color space like Adobe RGB to a smaller color space such as sRGB, or visa versa?
    Thanks in advance,
    TC

    I recently participated in a webinar and the instructor advised that you should 'never convert from from a large space like Adobe RGB to a smaller space like sRGB.
    That's not good advice.
    Convert when you need to convert. sRGB for web. CMYK for offset, etc.
    Furthermore, the instructor recommends that photographers set their cameras to capture in the sRGB space and then later convert to a larger space if the output device can accommodate it.
    Also bad advice.
    Capturing in sRGB hamstrings you from the outset. Almost every output device (monitor, inkjet, digital press, offset press) can exceed the color gamut of sRGB in at least one dimension. sRGB is the lowest common denominator of color spaces.
    My training as a film photographer makes me think that you would want to capture your files with as much data as possible.
    You are correct.
    At the very least, capture in Adobe98. But you really should be capturing in RAW. It gives you the most leeway when editing the image.
    My thinking is that files that are recorded in Adobe RGB and converted to sRGB do indeed loose date. However, the data that is discarded are colors that do not exist in a sRGB file, may be outside of what is perceptible by the eye, is outside of the ability of the output device to record, or colors that do not naturally exist in the subject to begin with.
    Well, kinda...
    The changes are definitely NOT "outside of what is perceptible by eye."
    When moving from Adobe98 to sRGB, you lose a significant amount of color in the blue/cyan part of the spectrum. Try it. Take an image that's been captured in RAW and processed into Adobe98 (or, just captured straight into Adobe98) and contains a deep blue sky or the kind of turquoise you see in a swimming pool or tropical ocean. Convert that image to sRGB and notice what happens to those blues and turquioses. Yuck. But, it is what it is. If the image is headed for the web, that's what you're dealing with.
    One question:
    Did you pay money for this webinar? You may want to try and get it back.
    Beware of the advice you hear on the internet.

  • How can I change a color of an image without affecting the texture, but based on a pantone pick?

    Here is an image of a paintbrush stroke that shows the texture of the paint.  I want to change the color to a specific pantone green in order to match a specific color pallet.  Rather than just using hue saturation to "guess" at the color (no pantone number), is there a way I can actually set a base color without losing the texture?

    You can only use the picker values as a guide on an image with many tones.
    I presume you are going to print as cmyk, so find the mix of the target colour and make a 'solid colour' adjustment layer and choose that mix. Then set the adj layer properties to 'hue' which should do it.
    Otherwise, add a 'hue/saturation' layer (and click on colorize in the adj layer palette) and move the slider to suit.
    If you convert to greyscale, you could colorize the pic with the spot colour too.

  • Color management and images uploaded to the web

    Hi,
    I use Photoshop on both a mac pro (OS 10.5) and a PC (Vista) and when I upload photos to the web, the images processed on my PC look just fine, but the images I process on my Mac look washed out and pale on the web. The funny thing is the Mac images look GREAT on the Mac, but washed out on the PC. Is there some color profile or calibration that I need to be doing? Please help!

    can I re-open/expand this one? I don't think it is quite this simple
    at present I perform a similar manual operation having set up a series of calibrations using the system prefs>displays>colour in different light and including gamma 2.2 version
    I use Nikon Capture NX2 for my photographic editing, but as you may not be familiar with it, it is serious software (dare I say here orders-of-magnitude better and more extensive than Aperture) and works on RAW (nef) files. I post on a number of equally serious web photo-forums posting at near professional level. There is a constant trickle of EITHER complaints about 'too dark' from PC users OR about colour, but am not concerned with that here.
    I tried out the suggestion of working at gamma 2.2 myself and found I had to adjust a good image by +0.67 EV to get back to normal. That is unacceptable and hate to think how results would print.
    So 10.6 is about to go to gamma 2.2 as normal, but what effect will that have on previous work done with 1.8, ie will the system correct everything by itself (or do we need to reach heaven first)?
    The more immediate effect of 10.6 will be that Nikon and others will probably take another 6 months to make their software compatible

  • After I rt click and hit "save image/page as" the dialog box doesn't open.

    When I try to copy an image or a web page I get no dialog box that opens after I right click and select "save image/page as". The option to send link works.

    Sorry, here the information that is required:
    Version 11.0.4.2 - CS6
    Installed recent updates: Yes
    OS: Windows 7 Pro (Service pack 1) 64 bit
    Model: HP Z420 Workstation
    Processor: Intel Xeon CPU E5-1620 @3.60Ghz
    Ram: 8Gb
    Has it worked before: yes. It started after I opened a project (trough "open project") because double clicking on this project gives the follwoing error: "The directory name is invalid". Via "Open project" I could open it.
    Do you have any third-party I/O hardware (e.g., AJA, Matrox, Blackmagic, MOTU)? No
    Quicktime 7 pro installed
    Do you have any third-party effects or codecs installed? Yes, Optical Flares & Trapcode. But is unrelated since it isn't a specific project.
    Are you using Render Multiple Frames Simultaneously multiprocessing? Yes
    Are you using the ray-traced 3D renderer? No
    Thanks for the help. If you need any other info, let me know

  • HT1222 My daughter had put in a password for my iphone and she forgot about the numbers. How can i reset it and what can I do ? I cant use the phone now ? pls help

    My Daughter had key in a password on my Iphone and forgot the number, now i can use my phone can you pls advice me how to unlock the password and use my phone again

    Hi ...
    If you can't remember the Passcode, if possible, restore the device from the computer it was last synced with by placing the device in recovery mode.
    Instructions here   > iOS: Unable to update or restore
    If you restore on a different computer that was never synced with the device, you will be able to unlock the device for use and remove the passcode, but your data will not be presen

  • Converting color space for web

    i shoot all my photos in adobe rgb. i would like to convert them for use on the web. i have read that they should be in sRGB color space. in photoshop i convert to sRGb color space but they still look the same as they did with adobe rgb, muddy and desaturated. can anyone help? i am getting extremely frustrated! thanks

    Probably you're using a web browser that assumes monitor RGB for untagged images, and the gamut of your monitor is smaller than sRGB. So when monitor RGB is assumed, your images look desaturated.
    You can get a wider gamut display. You can use a browser like Firefox with color management enabled, which assumes sRGB for untagged images. Or you can tag all your images with the sRGB profile (at a cost of 3.5k per image). In PS, you can assign your display profile after you've converted to sRGB to simulate what your browser is doing (or proof setup > monitor RGB).
    In general though, don't sweat it too much. All the images you've ever viewed on the web that were prepared for sRGB have been muddy and desaturated as you're now experiencing, and it's never bothered you before. Have faith in your users' capacity for ignoring these details...
    http://www.gballard.net/psd/saveforwebshift.html

  • New ICC v4 sRGB Color Space May Prevent Clipping Converting From ProPhoto RGB

    Just discovered and tried out this new sRGB color space downloaded from this page:
    http://www.color.org/srgbprofiles.xalter
    Here's a cropped demo with histograms of a raw image I've been working on in ProPhotoRGB in ACR 3.7 and CS2:
    http://www.flickr.com/photos/26078880@N02/2874068887/sizes/o/
    Please disregard the PRMG name in the demo. I got confused as to which was which on that site and thought that this version of sRGB was a PRMG=(Perceptual Reference Medium Gamut) profile. It's called sRGB_v4_ICC_preference.icc.
    Note the different color shifts using the Perceptual intent and unchecking Black Point Compensation=(BPC). Neat little features embedded in this profile, but not sure about how it renders certain colors close to clipping in the shadows. That site doesn't recommend mixed use of ICC v4 with v2 color spaces and output device profiles but I did it anyway just to see what it does.
    Who knows this may be the equivalent of handing scissors to children, but I'm just one of those curious children and thought I'ld share anyway.

    I'll try to respond to a few items above.
    The digital values in a Pro Photo RGB file should generally be the same as for a ROMM RGB file. The exception is that all possible Pro Photo RGB values are "legal" but not all ROMM RGB values are "legal." ISO 22028-2 restricts the legal ROMM values to those with PCS LAB values between 0 and 100 L* and -128 to +128 a* and b*.
    There is no enforcement if you use the illegal values in a ROMM file but as some of these values do not represent possible colors this is not advisable. I think it is good practice to try to stay mostly inside the ICC v4 PRM gamut with Pro Photo/ROMM images. You can check this using the gamut warning profile on the ICC site.
    If you have a Pro Photo RGB image you should just assign the ROMM profile to it. Converting to ROMM RGB should not change anything in the ideal sense but there is the possibility to introduce rounding errors and mismatch black points.
    The main difference between the Pro Photo RGB profile and the ROMM RGB profile is the former includes black scaling to zero (as is common with v2 color space and display profiles) and the latter does not (as is required with v4 profiles).
    In the duck picture, the reason for the difference is the ROMM profile black is at L*=3 so this is where the lowest blacks land when converting MRC to v2 sRGB (which has the sRGB blacks scaled to L*=0). In this case leaving BPC off is analogous to turning on "Simulate Black Ink" in Photoshop Proof Setup.
    All the ACR color space choices are v2 profiles with black scaling. If you want a v4 profile embedded you have to assign it (if you have a corresponding v4 profile) or convert to it.
    Both the sRGB and PRM gamuts fit within the ROMM RGB legal encoding range, but if you use a v2 profile with black scaling you should always turn on BPC when combining with a v4 profile. Otherwise the v4 profile will think the v2 profile represents a device with an infinite dynamic range. When BPC is on the Color Engine scales the black point of the source profile to the black point of the destination profile.
    The sRGB gamut extends outside the PRM gamut in some places, and the PRM gamut extends outside the sRGB gamut in other places. If you convert using a colorimetric intent in either direction some of the gamut will be clipped. The purpose of the sRGB v4 perceptual transforms is to minimize clipping in both directions.
    I can't do this justice here but basically scene-referred images are encodings of the scene colors and output-referred images are encodings of the picture colors on some medium for which the picture colors have been optimized. You can make a scene-referred image by setting the ACR sliders (except the white balance sliders) to zero and the curves tab to linear. You make an output-referred image when you adjust the sliders to non-zero values to make a nice picture as viewed on some medium. For example you might adjust the sliders differently to get the best results printing colorimetrically on glossy photo paper vs. on plain office paper.
    Often an important part of the transform to output-referred includes a midtone contrast and saturation boost. While there will likely be some highlight and may be some shadow compression, it is misleading to think of this transform only as a compression to some output medium dynamic range. In some cases the output medium dynamic range is larger than that of the scene.
    Usually the transform to output-referred is more complicated than a simple gamma function.
    Regardless of the image state (scene-referred or output-referred) the sRGB, Adobe RGB, or Pro Photo RGB nonlinearities will be applied to create the image data that you open into Photoshop.
    We are working in the ICC to prepare more information for posting on this topic.

  • Color space problem/confusion

    I posted the following message to another thread, but at the recommendation of a member I am starting a new thread here. For a couple of answers see the thread below.
    http://forums.adobe.com/message/3298911#3298911
    I will provide much more information hoping an Adobe support person will chime in. This is extremely odd.
    System: HP, AMD, Windows 7 64-Bit, Nvidia 9100, all updates to Windows, latest Nvidia 9100 driver
    Display: Samsung 226CW, Windows settings 32-bit color, correct resolution,
    Calibration: Done with ColorMunki, D65 target, done after monitor has been on for more than 30 minutes
    Personal:  (I am adding this information with some hesitation, please excuse it if  it sounds like I'm bragging; I am not). I have multiple posts on my  blog, have made many presentations on color managed workflow and am very  comfortable with the settings in Photoshop and Lightroom. Please take  this only as a baseline information, I am not bragging. In fact, I am  begging for information!
    Problem:
    Any, I mean ANY,  original JPEG image in sRGB space coming out of the camera with no  adjustments, any PSD file in sRGB space, any TIFF file in sRGB space  look significantly paler in Lightroom and in Photoshop CS5 than they  look in other Windows based image viewers like FastStone or XnView. This  should not need these applications to be color space aware, but the  situation is the same with or without their color managment turned on or  off. I have done the following:
    1. Totally uninstalled Lightroom 3 and reinstalled it
    2.  Recreated a brand new Lightroom catalog/library and reimported all the  images, converting all the RAW files to DNG (just in case!)
    3. Recalibrated the display
    When  I view a file, any file and I will use for the sake of simplicity a  JPEG file in sRGB color space, in Lightroom it looks pale. Since the  file is in sRGB color space, I have verified this, the rendering in  Lightroom should be the same as rendering in anything else. But it is  not. I took my monitor and connected it to this system with the same odd  behavior of rendering in Lightroom being much paler than outside. It  appears as if I am viewing an image in Adobe RGB in a windows viewer  that is not color managed.
    I further tried the following:
    1.  I copied various versions of one file, all in sRGB color space. One PSD  and two JPEG files from the folders of the above system and copied them  to my system, Intel, Windows 7 64-bit, display calibrated and profiled  with ColorMunki to the same standards as the problem system above.
    2. Imported them to Lightroom on my system
    3.  The rendering in Lightroom is identical to rendering outside Lightroom  for all the files and all are same as the rendering in FastStone on the  problem system. Outside rendering was done using FastStone as on the  problem system.
    My deduction is that something on the  problem system outlined in the opening of the message is interfering  with the Adobe rendering engine and I have no idea what it could be. I  WILL GREATLY APPRECIATE if an Adobe engineer could chime in and steer me  in the right direction. I am willing to try other things but I have run  out of ideas despite the fact that I have reduced much of the problem  to the lowest common denominator of sRGB and JPEG against a PSD in sRGB.
    Waiting anxiously of your help.
    Cemal

    Also, I know enough to calibrate a monitor when it is connected to a new computer. That said, even without calibration the behavior should have changed to display all the images in question the same but perhaps with somewhat off colors. Am I right? I am not arguing the point, I am rhetorically raising the question. If the 226CW is wide gamut and 244T is not, when I connect 244T on the same computer the wide gamut issue should be eliminated, should it not? I am not talking at this point about the "correct" color, but the same color in or out of Lightroom.
    Unfortunately when you connect another monitor to a computer and don't calibrate or manually change it, Windows will not change the monitor profile. Macs will autodetect and change the profile but this innovation has not reached windows yet. The behavior you observe is caused by managed apps using the monitor profile and unmanaged apps not. If the monitor profile is not changed, the behavior doesn't change.
    BTW, for a "cheap" software to be color space aware it does not need a quantum leap in technology I believe. It simply needs to know how to read the ICC profile and the LUT, is that correct?
    It's extremely simple to program color management into apps. Standard API libraries have been available in Windows for over a decade. The reason why this hasn't happened is related to the fact that Microsoft hasn't made IE color managed and the software makers do not want to confuse folks when images look different in their program vs IE. Considering that this still is the biggest issue people wrongly complain about in every color managed application (just check Photoshop fora) that is maybe not that strange.

  • What color space are the Color Lookup presets meant for?

    I've noticed that if I convert the same image to multiple color spaces and apply a 3D LUT with the new Color Lookup adjustment, the result is noticeably different.  From experimenting, it seems that the lookup tables operate on whatever RGB value is given to them no matter what color space.  Is there a certain color space these were optimized for?  For instance, would a certain color space give me a more authentic 2-strip look than another because of the space they were sampled in?  And if I create my own 3D LUTs, would I have to create a separate one for each color space in order to get a consistent look in all spaces?

    So do you know what color space was used to create the presets that are there, such as 2-strip and 3-strip?  Even though they don't know about color spaces, the different gammas on the input cause the look to come out different in all colorspaces, so it stands to reason that whatever color space the calculations and/or sampling was done in is closest to what was intended while the others are rough approximations.  For things like "warming" it doesn't matter, but for ones that simulate actual films I'm curious to know, especially since the 2-strip ones looks a little different than when you just copy the green channel into the blue and green channels as described on all the websites.

  • Color space conversion problem when importing JPEG's

    Hi,
    I'm currently playing with the trial version of LR. While importing JPEG's with different color spaces (sRGB and Adobe RGB) to LR I've noticed a strange effect: There is a small but noticable difference in color, depending if the JPEG was previously saved in AdobeRGB, or sRGB. All the images I've tested so far should not contain critical colors that exceed normal sRGB. When opened in CS2 both versions of a JPEG, AdobeRGB and sRGB, typically look perceptually identical, no matter if I leave the sRGB image to sRGB, or convert it to the working space (AdobeRGB). Also my color-managed image viewer behaves as it should. So I don't think it's a matter of the different color spaces.
    Looking at the imported images in LR I would say that the AdobeRGB image is correctly converted while the sRGB image suffers from a slight reddish cast, most noticable in skin tones. The effect is not as strong as if I would load the sRGB image into CS2 and skip color conversion to my working space (AdobeRGB).
    The sRGB versions of the JPEG's were obtained from the AdobeRGB JPEG's using CS2 for conversion.
    Anyone else here experienced a similar problem? Is this a bug in the xRGB-to-ProPhotoRGB conversion of LR, or a feature?
    /Steffen

    Hi Uli,
    thanks for pointing me to your thread. I followed the discussion with great interest. Actually, I think the effect I am describing here is of different nature and a LOT stronger, at least for the type of images I've tested.
    I did some more experiments yesterday with interesting results:
    1) When I export a processed RAW from LR to JPEG or PSD, no matter what Color Space (I tested AdobeRGB, sRGB and ProphotoRGB), and re-import those JPEG/PSD's to LR, they look absolutely identical to the RAW I started with. Also, at first glance, they look similar when opened in CS2, but only because I tested with color images. I can indeed see small differences when testing with B/W, as you described in your "Color management bug" thread.
    2) When I change the color space of an PSD or JPEG inside CS2 (I used the default setting 'relative colorimetric') and save it to JPEG and then import this JPEG to LR, colors are far off. The strength of this mostly reddish color cast depends on the color space of the imported JPEG, strongest for Prophoto, less strong for Adobe and sRGB. Interestingly, when I convert the color space inside CS2 and save the result to PSD, it will display correctly when imported in LR. Another interesting side effect: the thumbnails of LR-exported JPEG's in the "Open" dialogs of CS2 and LR (I guess those are not color-managed) show the typical color-flatness for the Adobe and even more the ProPhoto version. For the CS2-converted JPEG's, all thumbnails look just a colorful as the thumbnail of the sRGB version.
    3) Such an image which doesn't display correctly in LR will keep its color cast when exported again to a JPEG (not sure about PSD). So something goes wrong with the color conversion during the import of such CS2-converted images.
    My explanation so far is that CS2 uses a slightly different way of coding the colorspace information in the metadata of JPEG's which somehow prevents LR to recognise the color space correctly.
    Can you confirm this behaviour?
    Steffen

  • The availability of color space in RAW, TIFF and JPEG files

    This is useful if your new to DSLR photography.
    This is Nikon response on my question in the discussion: View photo metadata
    I'm assuming that you know that Adobe RGB shows about 50% and sRGB 35% of CIELAB color space.
    In a DSLR camera like the Nikon D800 you can select a color space (Adobe RGB or sRGB) in the shooting menu.
    In Adobe Lightroom 4.3 the RAW metadata shows no color space info. Therefore I asked why not?
    In the (Dutch) Nikon D800 manual on page 84 (about RAW) and 274 (about color space) and Nikon FAQ website there is no descripton about the color space availability/behavior in RAW, JPEG and TIFF files.
    In the book "Mastering the Nikon D800 by Darrel Young" on page 125 - 126 is written: "If you shoot in RAW format a lot, you may want to consider using Adobe RGB....."
    All experts on this forum answered: color space does not apply/affect the RAW data file or RAW files have no color space.
    The respone of Nikon Europe Support (Robert Vermeulen) was: In Nikon D800 NEF RAW files both color spaces (Adobe RGB and sRGB) are always physically available. In JPEG and TIFF files only the in the shooting menu selected color space is physically available. So the forum experts gave the correct answer!
    Of course you can convert afterwards a JPEG or TIFF file with sRGB color space to Adobe RGB but you don't get more colors.
    When you install the Microsoft Camera Codec Pack or FastPictureViewer Codec Pack they only show color space metadata for JPEG and TIFF files and nothing for RAW because color space "doesn't exist". I thought the codec packs removed the color space metadata for my RAW files.
    Adobe Lightroom also can not show color space for RAW files because that "doesn't exist".

    Van-Paul wrote:
    The respone of Nikon Europe Support (Robert Vermeulen) was: In Nikon D800 NEF RAW files both color spaces (Adobe RGB and sRGB) are physically available. In JPEG and TIFF files only the in the shooting menu selected color space is physically available.
    I still think this is an evasive answer that doesn't really pinpoint the exact chain of events that take place. They are:
    1. The raw file contains the naked data captured by the sensor. This is just a very dark grayscale image.
    2. In the raw converter it is encoded into a working color space to process the information. In Lightroom this is known as "Melissa RGB", or linear gamma Prophoto. It is also demosaiced to bring back the color information.
    3. From Lightroom it can be exported to one of the familiar color spaces like sRGB or Adobe RGB. This is, in principle at least, a normal profile conversion.
    These three steps are what the camera does to produce a jpeg. So the basic steps are the same, the camera is just doing it automatically (and usually butchering the image in the process...).
    This Darrell Young is, I'm sure, an excellent photographer, but in this he is seriously confused and just propagating a common myth. Anyway, thanks for bringing up this discussion, hope you didn't object too much to the tone of the answers... Our only concern here was to get this right and with no room for misunderstanding.

Maybe you are looking for