Color Space corruption in CS5 v.12.0.4

I have been having a great deal of trouble with colour instability since  recent updates to CS5 also. Am running XP64, CS5 12.0.4, Camera Raw  6.4.1. I run Adobe RGB 1998 workflow from camera to printer.
Seems to be totally random result of some files returning an sRGB colour  space and some returning AdobeRGB 1998 when converted to jpegs for  printing. Same result for scanned images too, so it is not the camera.  The 32bit version appears to be worse, but the 64 bit version does it  too.
EXIF details in Bridge show Adobe RGB, but this is not the case when  viewed with a hex editor. I processed the same two files (one a psd  & the other a tiff) no less than seven times with totally random  results. I could not return a pattern. Sometimes sRGB & sometimes  Adobe!
The only way I can get around it is to include a new line in the action  that sends the files to the print output folder which is: Edit/Convert  to profile/AdobeRGB 1998. This seems to ensure me the result I need to print accurately.
There is a thread on this at Phoshop.com at http://feedback.photoshop.com/photoshop_family/topics/corrupt_jpg_from_12_0_4
Note to ADOBE - NOT HAPPY!!
Colin

Hi Mylenium
Thank you for rthe reply. Where do I find that preference setting?
Does the Mac Update function not update the graphics card driver?
A.T.

Similar Messages

  • Everything is Green in RGB color space in Photoshop CS5 Mac

    The image explains it all.
    CMYK works fine, but RGB doesn't. The preview (in the channels pane) looks fine though.
    Pixelmator had the same problem, but I fixed it by turning off color management in Pixelmator.
    My question is, how can I fix this problem in a legal copy of Photoshop CS5 Extended?
    My Monitor is a dell e193fp, and am running Mac OS X 10.7.2.
    My video card is an ATI Radeon HD 4600, and I have a Mid-08 Mac Pro.

    It could be your display profile, or a problem with the video card drivers.
    I'd bet on the profile.
    Also: RGB is not a colorspace. RGB is a color model, or color mode.  A model or mode describes the number of channels, not the meaning of the channels.
    sRGB and Adobe RGB are colorspaces.  A colorspace describes the meaning of the color channels (a specific red, a specific green, a specific blue, a specific white point, a specific tone curve) for a given mode or model.
    For a color mode or model, there can be many spaces.

  • Color space AE CS5 Versus AE CS4 = !#%%$

    Hello,
    I'm trying to export HD uncompressed 10-bit with color space HDTV (rec.709) clips of VFXs footage that were done on AE CS5.
    My main project file to which I want to integrate them in on AE CS4 which I am using (the AE CS5 render are made by someone else that has it).
    My project file settings is in HDTV (rec.709) 16bit with mostly cineform clips, but with a few other VFXs shot that were renderer in HD uncompressed without problems (using CS4). I plan to them export my main project into HD uncompressed
    We tried to batch of export:
    First one was done in CS5 with HDTV (rec.709) in export settings but the project settings wasn't set to HDTV (rec.709) by the VFXs guy.
    When I imported those clips in my CS4 main project there was difference in color (more golden) and blacks (more crushed).
    You can it with the blacks's difference on the girl's hair and the side planel of the plane and the golden is less ovious on the picture quality but you see it a bit on the woman's face.
    I then proceeded to check color space, and it was imported by default by AE in sRGB IEC611966-2.1.
    I then changed it to HDTV rec.709 using interpret footage; it was a closer match, but not quite.
    I then noticed that all my project's clips, including the HD uncompressed one that I rendered (under CS4) from work done by another VFX artist, were all in HDTV rec.709 YCrCb, but the the imported clips I was trying to match were in HDTV rec.709 only with no YCrCb mention afte them.
    I talked with film's colorist and VFXs artist that worked with those projct file from which all the problematic shots comes (because problem is isolated to project file this person worked on), because we both over our head in color space territory.
    We came up the the possible solution that the project setting might have been altered for quicker workflow and not set rigth again.
    We checked and color space wasn't set in setting; colorsit suggested that if it's not set in settings no mather if you set it in your export settings, AE won't allow it and that's why it might have forced RGB, hence the sRGB IEC611966-2.1. It was in 32bit float instead of 16 bit, so that's ok, we initialy suggestedthat it might have been reduced to 8bit for quicker workflow.
    After this, we proceded to re-render in CS5, bu we found a weird thing that we both don't realy grasp.
    After he did the 2nd render (in CS5 still), he tried importing clips with old ones, to compare them to my unafected originals clips, in my CS4 project that he converted in CS5.  It was worst. He then switched off the "blend color using 1.0 gamma"; which my project file didn't have on in CS4. The files are in 32bit float and color space was HDTV (rec.709), but since it's not embed in HD uncompressed files he set them manualy after importing them.
    The OLD render batch was matching, but not the NEW ones.
    Then he tried importing both render batch in the original project file he exported them from, and it was the NEW batch that now matched.
    He's now doing test in my main project file in CS4 which is were I'd ultimately like it to work in,
    but if anyone could gives us pointer as to why this is happening and how to make it match with no hassly tat would be great help.
    Thank you for your time and interest.
    Frédéric

    You've lost me, honestly, but obviously you seem to be close to the solution. Your colorist is mistaken, though, about how AE handles color profiles. It doesn't discard or enforce profiles, it really seems you just forgot to carry them somewhere. Also, since these are different machines, maybe a specific profile was not available. eitehr it was never installed or it is blocked due to permission issues...
    Mylenium

  • 1.4.1 corrupting the color space

    I submit images to Alamy, Photoshelter and others. As of last night I converted an image via LR as a b&w and exported it as a jpeg to my Photoshelter folder. Trying to upload it the Photoshelter system informed me that the jpeg had an unknown ICC space and the upload ground to a halt.
    Opened Photoshop and tried to open the same file and sure enough the ICC warning message appears. So, tried the same process with a colour image and it worked as usual - no problems.
    Anyone have any idea what's going on here?
    Thanks in advance.
    Paul

    That is really weird! This is not an RGB image, I get the same invalid message in Photoshop, but preview.app opens if normally and says it is in the Gray (instead of RGB) color space and has an adobeRGB profile (which is inconsistent indeed). Whenever I export a greyscale converted image (converted to greyscale in LR) it does the correct RGB color model with sRGB profile (or whatever I select) Definitely something is wrong here. It should not do this. Nothing else touched this file but Lightroom (so no plugins like LR/mogrify)? You exported as a jpeg, not "original"? No Photoshop droplet?

  • How to Get RGB Values from a CMYK Color in the DOM (CS5)

    (CS5, Actionscript)
    Hi all,
    I have an InDesign document containing TextFrames whose border colors are specified as a CMYK array.
    I would like to be able to get its color specification as its closest RGB equivalent.
    Does the InDesign DOM contain a method for doing this for me automatically?  If not, what workarounds are there?
    TIA,
    mlavie

    Here's how to convert RGB to CMYK:
    function rgb2CMYK (r,g,b){
        var color = app.documents[0].colors.add({space:ColorSpace.RGB,colorValue:[r,g,b]});
        color.space = ColorSpace.CMYK;
        var retVal = color.colorValue;
        color.remove();
        return retVal;
    The same idea for the reverse.
    For info on converting to grayscale, check out this:
    http://in-tools.com/article/scripts-blog/convert-colors-to-grayscal-in-indesign/
    HTH,
    Harbs

  • Lightroom's 4 color "spaces"

    I’m working on designing an advanced photography course. This course makes use of Lightroom and Photoshop in the photographic workflow.
    I’m learning and researching myself as I go along, and I feel I have reached a ceiling on what I can work out from the sources at my disposal thus far.
    So I am turning here for help.
    I am trying to clarify how tones and colours are affected from the actual scene through to the printed page. This might seem like overkill to some. However, there is a lot of misunderstanding and confusion, not to mention heated discussions amongst photographers about these issues. I’m experimenting with metering and colour / tone targets and my calculations are only meaningful if I understand how tones and colours are affected at every stage of the workflow.
    Here’s how I understand it:
    There are 4 (sort of) Colour “spaces” in Develop where a real-time dynamic preview of an image is rendered
    1.       The “viewing space” (ProPhotoRGB Chromaticity co-ordinates, sRGB gamma)
    2.       The “computational space” (ProPhotoRGB chromaticity co-ordinates, linear gamma – “MelissaRGB”)
    (Martin Evening’s Lightroom 3 book published by Adobe press - Appendix B, section on color space page 628-632)
    Below that, things get a little fuzzy. According to Jeff Schewe (Real World Camera RAW for CS5, page 32) there is a sort of
    3.            “Native Camera Space” and of course there is the
    4.            RAW data in the file on disk.
    So to generate the dynamically rendered preview, the image goes through the four “layers” as follows (from bottom to top). This is almost certainly flawed, but one has to start somewhere when trying to work things out :-)
    1. The RAW file is read from disk. Colorimetric interpretation is performed using a camera profile (e.g. Adobe Standard for whatever camera it is you are using). This process puts the image data into “Native camera space” (“Plotted” onto CIE XYZ with D50 white point)
    2. In “Native camera space, the scene white balance (as selected by user, guessed by Lightroom or reported by camera) as well as additional camera calibration panel matrix tweaks “informs” the colorimetric conversion into Lightroom’s “computational space” e.g. Melissa RGB. The colorimetric definition of camera RGB primaries and white is re-DEFINED. The demosaicing as well as chromatic aberration corrections are performed in “native camera space”
    3. Almost all image processing calculations occur computationally in the  “MelissaRGB Lightroom computational space”
    4. What is displayed on the screen, however, has an sRGB tone curve applied. This represents the “viewing” space. The histogram is generated from this and the RGB colour percentage readouts are generated from this as well. In addition, some slider controls from user input are weighted back through the tone curve into the computational space below.
    Could someone from Adobe kindly help me to clarify the steps? Eric are you reading this? :-)
    Thanks in advance

    Sandy - Thanks for the link. The spreadsheets you posted on your site is quite helpful.
    Jao – I think what you said goes to the heart of what I am trying to achieve here: “Photograph a grey target at the exact same exposure with the exact same lighting but with different cameras and you'll end up with different values in the raw files” Which is why I encourage photographers to experiment with their cameras in order to understand exactly how the camera will respond in the heat of a real shoot. Set up a scene; take a picture, open in Lightroom. What is clipped and why? Use a reflective spot meter. Repeat. Use a hand held incident meter. Repeat. How much can you reliably recover? Are you happy with what your meter considers the mid-point (and what you set your exposure for on the camera) or do you need to compensate? Just how much latitude do you have between what your camera histogram shows as a blown out highlight and what Lightroom shows as a blown out highlight. This relates to tone. I could go on with more examples, but by now, I am (hopefully) making more sense.
    I’m merely trying to clarify that which is already public in order to form a coherent mental picture. And by mental picture I do not mean an accurate representation of the minutiae and maths involved. Think of a subway map. It represents a bird’s eye view of a transportation system in a logical fashion, yet it bears almost no resemblance to the cartographical reality of the physical topography. I really don’t care where the tunnels go, how they were dug, how they are maintained or where they twist and turn. What I AM looking for is a logical (not physical) map. This map tells me where the different lines begin and end, and where I can change from one line to the other. The most important quality of the map as a whole is that it provides context. You can tell, at a glance, how different lines interact with each other and even how it links to other entities such as bus stations or public landmarks.
    As many have rightfully pointed out, I should not have to care about the maths/secret sauce/internal calculations. And I don’t. In addition, I am a very happy Lightroom user and I am very comfortable using it. I know what a user needs to know to get his picture from A to B. There is no shortage of information on how to accomplish that.
    It might help if I illustrate what I am trying to do below:
    Please excuse the low resolution, the maximum height allowed for upload is 600 pixels. The picture below goes on the bottom left of the "layer" picture above.
    Even though there are certainly many mistakes in my diagram, this is a helpful visualisation. I derived this diagram from publicly available information. As the subway map, this is a logical (not physical) representation that provides context in a visual form. With a little help from people like Eric I am sure I can correct and expand it. The net result is an enhanced understanding of Lightroom and ACR and where it fits into the photographic process, both in terms of tone and colour.
    I am not posting the entire chart here since I am not even certain that a 4 “layered” representation is an appropriate logical representation. I posted the spine of the chart with the 4 “layers” and one part that elaborates on the colorimetric interpretation between the two bottom layers. Comments and corrections are welcomed. And I am convinced that this can be accomplished without divulging anything confidential.

  • 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

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

  • Lightroom,Nik plugins and color spaces

    I'm having an issue and not sure who is holding the smoking gun.  I have the Nik ultimate collection installed which covers Lightroom and Photoshop CS5 extended. I work primarily in Lightroom and apply most corrections globally but occasionally i need to do localized adjustments so the photo gets shipped off to Photoshop.  Here's a typical scenario:
    1) From Lightroom edit in Dfine 2.0 for noise - as copy with Lightroom adjustments which gets copied as a tiff.
    2) From Lightroom edit in Viveza 2 - as original since we're now working with a tiff and I don't want a copy for every single thing I'm doing.
    3) Edit in Photoshop
    Now there's two issues at this point:
    1) The edits do not show up in the Lightroom history - it's like nothing happened.
    2) Photoshop will complain that the assigned profile is sRGB.  Really?
    #1 is a PITA because if I want to rewind I have to start all over since there's no history - what exactly is responbsible to set an edit as history?  Lightroom or the plugin?
    #2 is by far the most serious as it degrades the work in a seriously bad manner.  I mean, WTH - I'm moving along in ProPhoto Ferrarri space and all of a sudden - *boom* - I'm running in sRGB moped mode.
    I looked at edit->Preferences->External Editing -> Additional External Editor and indeed when I select the Nik plugins from the combo box  preferences the default for the plugins is sRGB.  I can change to ProPhoto and quit.  I repeated this for each plugin assuming that somewhere the setting was remembered.  Nope  LR acts dumb as a rock and shows sRGB as the defaults for all except the currently selected plugin.
    So my questions are:
    - who's gonna own up to the problem - LR or Nik?
    - how can I work around it?
    - how can I make LR remember the settings?  Not a registry key nor INI file in sight to set them - so where/how are the plugins tracked?
    Thanks for any help!
    Jon

    Jon,
    The User Interface for changing how external editors are invoked is about as smart as your average chunk of granite.
    After you change the Color Space to the one you want, you have to click on the Preset box and choose "Save current settings as new preset...". Not exactly intuitive, but there you are.
    Hal

  • Photoshop and Bridge Color Space Mismatches

    I've recently scanned a number of photos (.TIFF) using the Wide Gamut Color Space (Nikon AdobeWide 4.0.0.3000).
    Bridge shows:
    Color Mode = RGB
    Color Profile = Nikon AdobeWide 4.0.0.3000
    However when I open them using the embedded profile, Photoshop CS5 shows on the file Info/Camera Data Tab
    Color Space = sRGB, or
    Color Space = Uncalibrated.
    I opened the files in IDImager to see what it showed. It had under Technical Data
    Color Space = AdobeRGB
    Color Profile = Nikon AdobeWide 4.0.0.3000
    So, Bridge and IDImager seem fine; Photoshop seems to have some difficulty.
    The monitor is calibrated.
    Why would Photoshop behave in this way? Is there anything I should be concerned about in what PS may be doing.
    Dale

    Probably something to do with your Edit->Color Settings. Is the second RGB dropdown set to Convert to Working RGB?

  • Color space/profile name

    I have some pictures that don't show a thumbnail in iPhoto. The info dialog for them says the Color Space is "Gray" and the Profile name is "Gr?skala - gamma 2,2". If I double-click on of these the enlarged image seems somewhat faded. The picture looks fine if I just view it directly in Preview, or ColorSync Utility. It seems most pictures have a Color Space of RGB, how to I change the Color Space of these files to RGB?

    Justin:
    Download the Automator application "Embed sRGB Profile" from Toad's Cellar and unzip it. Then locate the original files for those problem images and drop them on it. Next launch iPhoto with the Command+Option keys depressed and follow the instructions to rebuild the library and select the first three options. This should get those images compatible with iPhoto.
    Do you Twango?
    TIP: For insurance against the iPhoto database corruption that many users have experienced I recommend making a backup copy of the Library6.iPhoto database file and keep it current. If problems crop up where iPhoto suddenly can't see any photos or thinks there are no photos in the library, replacing the working Library6.iPhoto file with the backup will often get the library back. By keeping it current I mean backup after each import and/or any serious editing or work on books, slideshows, calendars, cards, etc. That insures that if a problem pops up and you do need to replace the database file, you'll retain all those efforts. It doesn't take long to make the backup and it's good insurance.
    I've written an Automator workflow application (requires Tiger), iPhoto dB File Backup, that will copy the selected Library6.iPhoto file from your iPhoto Library folder to the Pictures folder, replacing any previous version of it. You can download it at Toad's Cellar. Be sure to read the Read Me pdf file.

  • Why Invalid Color Space Error?

    Hi Everyone,
    I am receiving numerous "invalid color space" errors when viewing PDF files in Acrobat Reader (v 11.0.10) on Windows 8, but have not received similar messages when using Acrobat Reader (v 11.0.10) on Mac OSX 10.9.5.  I will outline our environment and workflow below.
    The PDF file is created via the export of an InDesign CC 2014 document.  No errors show up on the preflight panel, and no warnings show up upon export.  The file can be opened fine in the Mac environment with both Acrobat Pro 11.0.10 and Acrobat Reader 11.0.10.  I can navigate through pages, print, and add comments in both applications.
    When this same file is opened on Windows 8 it initially loads, navigates pages, and will allow a few comments to be inserted before showing an "invalid color space" error.  If the error occurs during commenting, the comment will disappear, and I am no longer able to scroll through any other pages since the error reappears.
    I would think that if it was file corruption the problems would be on both Mac and Windows.  Any suggestions would be extremely helpful as all of my searches point to a non-Adobe product (as either the document source or PDF generator) as the culprit with this error.
    Thank you!

    Hi Racheal ,
    Please refer to the following link to see the actual cause for "invalid color space" error and the possible solutions to deal with it.
    http://blogs.adobe.com/dmcmahon/2011/05/17/acrobatreader-invalid-colorspace-error-opening- a-pdf/
    Regards
    Sukrit Dhingra

  • Why did Adobe get rid of 'No Color Management' option in CS5

    I use this option (in earlier CS verisons) when printing digital negatives on transparency film on my Epson 3880. There are a few work-arounds, including a printer utility from Adobe (which only works on tIff files, so it's limitied).
    But why, oh why did they get rid of this option in the first place. Did someone just decide, gee, I don't think that's a feature we want anymore in our program, so, puff, it's gone? I hate it when program 'updates' make my work harder instead of easier. 
    Regards, David

    Was DYP wrote:
    Can you prove this with a supporting document?
    Nope...I was told this by engineers familiar with the initiative...
    Was DYP wrote:
    ACPU and for that matter i1Profiler sends print image data (untagged I assume) through ColorSync and the print driver the exact same way as Lightroom and PSCS5 do when Application Manages Color is selected when printing. The only difference is that LR and PS do not allow you to send untagged image data.
    ACPU does send the untagged data through Colorsync, but the image data gets converted by Colorsync or ACPU to the printer profile chosen in the print driver as set up in the Print window of ACPU...so, since the document is in the final profile space of the printer, the print driver does nothing (null transform). Then you choose don't manage color in the driver. Exactly how ACPU works with Colorsync to avoid having Colorsync to an unwanted color transform isn't clear (would have to ask the engineer that wrote it), ACPU is clearly doing SOMETHING different than Photoshop and Lightroom when sending the image data to the printer.
    You can see what profile gets embedded when printing from ACPU by setting up the driver and saving a PDF and opening in Photoshop. When I printed to PDF from ACPU after setting up the driver to use Epson Glossy paper on an Epson R3000, the embedded profile in the PDF was SPR3000 Premium Glossy. Which if sent to the printer should result in a null transform. This is similar to the CS5 work around to tag an image with a color space and have that same color space set in Photoshop Manages Color and set the Printer Profile color space to be the same thus bypassing the Colorsync "generic RGB" transform. However, that work around no longer works with Photoshop CS6 (we were warned that this might happen BTW).
    I haven't tried it yet, but it's possible that you could still work around this in CS6 if you take an untagged target, assign the printer profile, then use Photoshop Manages Color with the profile being the same printer profile and then in the driver set do not color manage...actually, scratch that–I just tried that and CS6 pops a warning that "No Color Managment is not supported" when trying to print without the proper color management and to get ACPU with a link to download it. I guess Photoshop got pretty serious about disallowing this sort of printing. Heck, you can't even print to PDF.
    On the other hand, the simplest solution for me is to simply print out the target using i1Profiler...

  • Color spaces not sticking...?

    What's Confusing: I have a layered file, the color space assigned to it is sRGB. I save a png file via Save For Web, tick the option to convert export to sRGB. All looks good in the save for web 2-up preview. But when I open the new png file, it's color profile is set to Adobe RGB, and the color space looks off—not like it did in the SFW preview.
    Details: My default color space is Adobe RGB. Sync'd across all CS5 apps. I have the option ticked to warn me on profile mismatches when opening a file. So far so good.
    So it seems like my Working Space color (Adobe RGB) is overriding SFW settings as well as my document color space settings
    Same thing happens when saving as a jpg.
    Any thoughts?

    To erase, delete or reset Save For Web & Devices SFW preferences:
    Open a small .jpg in Photoshop (to ungray the File menu).
    Mac: Press and hold Option+Command keys, while File> Save For Web Devices (you will get a prompt confirming you want to erase all Save for Web preferences).
    Windows PC: Press and hold Control+Alt keys, while File> Save For Web Devices (you will get a prompt confirming you want to erase all Save for Web preferences).
    that should configure SFW default settings to CONVERT your Photoshop Source Space to sRGB and strip the ICC profile by default
    How to reset Photoshop's preferences using special key combinations (most Adobe apps use this method of keystrokes):
    First Quit Photoshop.
    Mac: Press and hold Command+Option+Shift keys, while opening Photoshop (you will get a prompt confirming you want to delete the Adobe Photoshop settings folder).
    Windows PC: Press and hold Alt+Control+Shift keys, while opening Photoshop (you will get a prompt confirming you want to delete the Adobe Photoshop settings folder).

  • Banding in broad color space????  grrr

    I'm on an old laptop, PS 5.5.  I have a properly exposed iso 1800 D600 jpg
    captured in adobe rgb color space.
    I use camera raw to open this picture in photopro space and 16 bits to
    avoid banding and yet if I lift the curve a tiny bit or any other brightening trick
    immediately there is banding.  What?

    Steve Zeeeee wrote:
    What else happens with this choice and how does it affect photo editing?
    As far as I know, with Photoshop CS5.5 Standard edition you'll have all GPU-dependent features, so you might just find the screen updates a hair slower - or not, modern processors are pretty fast, even in laptops.  The primary difference is that the Adobe Color Engine is executed in the CPU, rather than the GPU, and as such it produces more accurate results.
    With Photoshop Extended versions and/or CS6 I think there may be actual GPU-dependent features that are hobbled or disabled if you use Basic mode GPU operations, though to be honest I've lost track of all the permutations.
    Try it and let us know whether Basic mode supports all that you do, just with more accurate color.  It's what experts do when we need to use an alternate configuration setting to work around a problem.
    By the way, the issue does not present itself even in Normal or Advanced modes if you choose to make the Adobe RGB 1998 profile your working space.  Since few output devices provide gamuts larger than Adobe RGB it's a possible alternate workaround.
    -Noel

Maybe you are looking for