CS3 + ID CS4 - Color management Iussues in Bridge CS4

I have CS3 WEB PREMIUM edition and recently added InDesign CS4. While trying to get the color management right for all Suite applications I get an error in Bridge CS4.
"Suite Color Management is not enabled. Suite Color Management requires that a qualifying product has been launched at least once to enable this feature."
So, I DO have a Creative Suite, only different Versions of its applications. Where is the problem, and if Bridge CS4 keeps on thinking I have no Suite at all, am I supposed to reinstall Bridge CS3?

Pascal.
I see you are a new Mac user. In case you're not aware...
On the Mac, new installations of Adobe (and much other) software do not overwrite and/or replace older versions when doing full version upgrades. Older and current software versions coexist and you can still use either -- particularly useful when learning a new version, but you still need to get work done now. Or if there is a favorite feature that was not included in the new version (such as no ImageReady included with Photoshop).
Be aware, though, double-clicking on a file will launch the latest version unless the older version was previously launched.
For those apps or (more likely) utilities that do overwrite or remove older versions, you're given a heads-up before you commit to an install.
Neil

Similar Messages

Preview panel loses Color Management after Minimize Bridge CS5

Whenever I minimize the Bridge CS5 application window to the Windows taskbar, upon restoring or maximizing the Bridge application window the image(s) currently showing in the Preview panel no longer appear color managed (they look exactly as they would appear from a non-color-managed app.) In order to see them as color managed again, I have to either de/re-select their thumbnails or double click the Preview panel twice (once to minimize it, and once again to restore it.) Otherwise resizing the Preview panel has no impact on the color. The thumbnails in the Content panel are fine. This did NOT occur in CS4 or earlier versions of Bridge - otherwise the same environment.
I have a wide-gamut monitor, which causes many non-color-managed images to look super saturated, especially reds & greens, so it is probably much easier to notice this behavior in this environment than from a typical-gamut monitor.
Windows 7, x64, ATI Radeon HD 4850 graphics card, Bridge v4.0.3.9
Anyone else notice this annoyance?

Thanks Curt,
I doubt this is a video issue as no other versions of Bridge behave this way on this system. I have the same preference settings in Bridge CS5 as for Bridge CS4 - which works fine. Nor does Photoshop exhibit this behavior post-minimizing, & Photoshop behaves perfectly for all the OpenGL Drawing settings (which I have set to Advanced in PS.) Bridge just seems to poorly manage the Preview panel color post-minimizing the application window, but otherwise everything displays fine during operation. I'd be surprised if it was just me but if it is, it's an easy enough annoyance to work around. I'd imagine that this isn't too observable on a normal-gamut monitor.
I tried your suggestion of "use software rendering", just in case, but it made no difference. Appreciate the idea though...
One more observation:
While thumbnails are being generated for the first time on large images, they also have the non-color-managed appearance until they complete their generating, at which time they take the managed appearance - but I just consider that a processing-timing final step & it hasn't changed behavior from previous versions of Bridge.

Color Management Discrepencies Between Bridge, ACR & Photoshop

Hi - I've had a color management issue I can't wrap my head around which is similar to this infamous thread: http://forums.adobe.com/message/3235601#3235601
I'm hoping with a little more information provided I can get this figured out. The basic problem is that Bridge displays images markedly differently than either ACR or Photoshop. The most common issue is as follows:
With the external monitor as the primary display (and the laptop monitor as a secondary), I start Bridge. Photos will seem to be in the correct gamut for a moment, but it almost immediately desaturates them as if switching gamuts. Opening the image in ACR or Photoshop shows the correct color. See the below:
(Note: on my wide-gamut monitor, there's no clipping on the ACR version - that's how it should look)
There are various permuations to this problem depending on which monitor I have on when I start Bridge, but the above is my general workflow.
Some background:
Lenovo ThinkPad T430s w/ integrated Intel HD4000 graphics
ASUS ProArt Series PA246Q (Wide Gamut)
Photoshop CS6 (using 16-bit ProPhotoRGB as the standard workspace)
Datacolor Spyder4 calibrating both monitors
My settings:
I know there are a bunch of variables, but does anybody see any glaring issues which might explain my problem?
Thanks!

No problem, thanks for the help! On my PC, screen capture using the Prnt Scrn button must be pasted into a program or taken/saved using the snipping tool. Either way the result appears to be untagged.
Here are a few more examples if you get a chance to look in the future. I'm making sure the proper profiles are embedded correctly (you can confirm in both Photoshop [lower left] and Bridge [upper right]):
Primary, wide-gamut monitor (sample includes embedded profile) - Viewing PSD w/ embedded ProPhoto RGB:
Secondary, laptop monitor (sample includes embedded profile) - Viewing PSD w/ embedded ProPhoto RGB:
Primary, wide-gamut monitor (sample includes embedded profile) - Viewing WhackedRGB Sample w/ embedded profile:
Secondary, laptop monitor (sample includes embedded profile) - Viewing WhackedRGB Sample w/ embedded profile:
Primary, wide-gamut monitor (sample includes embedded profile) - Viewing Sample Lowrez ProPhotoRGB w/ embedded profile:
Secondary, laptop monitor (sample includes embedded profile) - Viewing Sample Lowrez ProPhotoRGB w/ embedded profile:
So the WhackedRGB sample looks ok and the ProPhotoRGB samples look ok here, but it doesn't look like the WhackedRGB or ProPhoto samples have anything outside the sRGB range.
Note what happens when I edit the WhackedRGB and ProPhoto samples simply by adding colors on the extremes of the gamut...
Primary, wide-gamut monitor (sample includes embedded profile) - Viewing WhackedRGB Sample w/ embedded profile EDITED with gamut extremes:
Primary, wide-gamut monitor (sample includes embedded profile) - Viewing Sample Lowrez ProPhotoRGB w/ embedded profile EDITED with gamut extremes:
The issue is back - the colors are very different! At this point, it's probably a bug, right...?
Thanks again!

CS3 color management won't match prints

Okay, I know there are a lot of boneheds who can't figure out how to set up color in Bridge and CS3 but I am at my wits end on this so bear me out.
Windows XP and CS3
Bridge is set to; Enable color management in Bridge
RAW conversion is SRGB
CS3 color settings/working space set to SRGB
Print color management is set to SRGB and Photoshop manages colors
Printer is set to "application manages colors" (HP B9180)(btw, I have also tried it set to SRGB)
Image looks the same on Bridge, RAW conversion, CS3 and print screen (dark)Image looks LIGHTER when viewed with any other program (including windows picture and fax viewer, HP print program, Paint Shop Pro and online) and prints to match the lighter image both on my HP and from my lab!
The closest I have been able to get to a total sync is to set Photoshop's color settings to "Monitor color," and uncheck the box in Bridge that says "apply color management settings in Bridge." In that case, Bridge and CS3 produce a lighter image but RAW conversion is still darker. Plus, who the hell wants to use monitor color in Photoshop!?

That's pretty much it David... I could get Photoshop to match my prints but then any other program would show the prints as being waaaay off-color.
Today I bought a spider2express and color balanced my monitor. Now everything seems to look in sync and my prints match very close (a little warm for my tastes..). Tech support at Photoshop told me it was a calibration issue but I thought that was bull... i mean, how can calibration make an image that looks different in two different programs look the same? Well, it does. As far as I understand it now (layman's terms)when you look at an image in windows viewer ot explorer or any other non-color management program you are looking at the image based on your monitor profile. When you look at the same image in photoshop the program uses it's own color management which then gets filtered through your monitor program to your eyes (but not to the printer). If your monitor profile is bad, the image looks bad.
Or something like that :)

Color Management in Bridge CS6

Hello,
I'm having a strange color management issue in Bridge (64 bit). Essentially, Bridge is not displaying images in either the thumbnails or preview pane using the correct color profile.
Background: I'm on Windows using a dual monitor setup (both independantly calibrated) but I have the issue even when I use only one monitor. Photoshop has no issues with color settings. I've tried resetting all settings (hitting Ctrl as Bridge starts). I've tried purging my cache and having Bridge generate monitor-size previews.
The weirdest part is when I start Bridge, for a split second images appear to be in the correct profile, and then Bridge adjusts everything to the wrong color profile.
Any thoughts?
Thanks!

Omke Oudeman wrote:
about A:
I don't get that, I have a custom made monitor profile based on D65 and with or without this profile the only difference one would spot would be in the total picture, this screenshot shows what I see and that is not as much difference between the Bridge thumb and preview (and in the metadata placard you can see they are 16 bit ProPhoto with on top of it the floating PS panel with the same image. It is one picture of one screen, without my monitor profile (and without knowing what happens during the adding process to the Adobe site) or with, the difference between both applications would not change, only the total picture. (or I really don't understand anything anymore about color management )
The first threshold question is whether you're using a wide gamut monitor. I'm going to assume the answer is yes. The reason it's essential to embed your monitor profile in your screenshot is if you do not have a wide gamut monitor, someone looking at your image who does will be able to tell since the gamut will be smaller than it should be. If you are not using a wide gamut monitor, that would explain why you cannot see the difference. Additionally, whether you have a wide-gamut monitor or not, if you do not embed a profile, the untagged image will appear way oversaturated when brought into Photoshop (this is happening for me) unless I can guess the approximate color space of your monitor.
Admittedly, if you are using a wide-gamut monitor, then although the image will be way oversatured without a profile (until I assign one), both the Photoshop portion and Bridge portion should be way oversatured by the same amount. However it's not particularly helpful to use guesswork and approximation when trying to narrow down a problem like this. You say "this screenshot shows what I see," but you have to keep in mind you are looking at it on your monitor. Even though your screenshot will obviously look right to you on your monitor, someone looking at it on a smaller gamut monitor won't see what you're talking about.
about B:
There you have a point but this was a current project at hand and at this moment there is a bit over saturation in the wood. In real life I also almost never have to deal with the bright colors of your example. I don't want to go again messing my workspaces to create a screenshot for the files you provided but I can assure you I have less to none difference between both files in both Bridge and PS, like I never have seen your problem on my current computer (Mac Pro, 2 x 2,4 6 core intel Xeon mid 2012 and a lot of RAM and SSD etc including ATI Radeon HD 5770 1024 MB VRAM running OSX 10.8.3) as well as my former MacPro with same graphic card - and two others - that I used since 2008 during OSX 10.5 to 10.7 with all used versions of CS.
Yea, I understand why you don't want to mess with your workflow. I wouldn't either if I were in the middle of a project. But (assuming you have a wide-gamut monitor) if you finish a project and do get the chance, I encourage you to try the ProPhotoRGB color patch in Photoshop versus Bridge. When you really stray from sRGB, you, like me and Yammer, should see a major difference. I suppose there's the possibility that the Mac version of Bridge works differently, but that doesn't seem likely. It's possible you've never noticed the difference before because (again, assuming you have a wide-gamut monitor) you've never been looking for it, or you don't shoot many subjects with colors vastly outside sRGB - things like flowers, dyes, clothing, bright lights, etc.
And as for the quote, I also never make my choices based on colors for DNG in Bridge, in fact, I always shoot with manual WB set to 5500 K, whether in daylight or artificial light, I just don't bother because I want my colors to be adjusted in ACR and refined the way I want them in PS. The plus side of manual WB is that all colors are off in the same way and can be adjusted in the correct direction in one go for a series
That's an interesting idea and really illustrates the beauty of shooting RAW - tons on flexibility. And in fact, whether you use manual white balance, or don't, with RAW everything can be corrected or adjusted from a certain baseline by the same amount after the fact anyway.

Bridge CS4 color management only works with GPU active

When I turn hardware acceleration off (by selecting software rendering in Bridge advanced preferences) Bridge color management disappears and on my wide gamut display I get cartoon color thumbnails indicating that CM isn't working. With GPU rendering on and Bridge restarted, CM works as it should.
It seems that Photoshop requires hardware acceleration with the "color compensation" option checked under the Performance/Enable OpenGL Drawing/Advanced settings preference.
Is color management now only functional with OpenGL acceleration enabled? I can find no help documentation for the advanced OpenGL Drawing settings. What a huge can of hardware worms this is turning out to be.

I wouldn't think that Bridge needed the GPU for CM, yet bypassing the GPU turns off CM in this installation.
I'm still confused about what you indicate in the Photoshop CS4 thread on OpenGL.
Chris Cox, "A few questions about OpenGl acceleration" #14, 11 Nov 2008 7:31 pm
I interpret your comment as suggesting that disabling color compensation in the PS CS4 GPU debugging features should disable CM in Photoshop, but it doesn't, it just makes it unreliable in displaying images post profile conversion in my tests. I'm probably missing some nuance here.

Vista color management & CS3

Two weeks ago I wrongly faulted my new Dell 2707WFP monitor for its high contrast and saturation after many failed profiling attempts using the Spyder2Pro with the updated Vista software. I'm still at a loss as to why images are dark and overly saturated in Photoshop, Bridge and Lightroom. They were all fine on an older Dell system running XP home and CS2. I've gone so far as to purposely inflict various gamma curve settings in Spyder to bump up the low end luminance but resulting profiles still show images clipped in the low end and overall saturated even as the desktop and the PS interface turn a sickly pale.
I'm new to CS3 and Lightroom and so I'm not sure if the following is normal. When I view a NEW batch of images that were not previously viewed in Bridge, they are normal looking, however when I click on a thumbnail, it then reverts to the same garish contrasty version that I see full size in the above adobe software when opened. The same thing happens in the WINDOWS PHOTO GALLERY viewer but NOT in WINDOWS EXPLORER. In Explorer the thumbs are as they should be...normal, and if I open them in Microsoft OFFICE PICTURE MANAGER or in Quicktime PICTUREVIEWER, they open as normal images.
All this sounds like a profile issue of some kind, but as far as I know, everything appears to be set correctly in both PS and the profiling software. However, Im not sure about the system settings regarding profiles. In the Windows COLOR folder all the profiles are where they should be and I can select which one to load using the Spyder Profile Chooser. And again, I do restart PS when I change a profile. Could this be some kind of Vista bug??
Other notes:
If I do a screen shot and paste it back into PS, it turns DARKER than the original file.
When I do additional calibrations I restart PS to load the latest profile.
All files tagged sRGB and in sRGB workspace. PS shows this correct space and likewise the correct monitor profile in COLOR SETTINGS
ATI CATALYST CONTROL CENTER fails to run on bootup so windows shuts it down. No fix that I can find for this.
Running Vista Home Premium on a Dell Inspiron 530 E6550, 4GB memory, Radeon HD2600XT
Thanks again for your help!

Found this on the DATACOLOR site in their SUPPORT CENTER:
Incorrect Color outside Photoshop on Wide Gamut Display
Solution >>I just purchased a Dell 2407 HC display, considered wide gamut and the spyder 3 elite. I've used the spyder 3 to calibrate the monitor. In photoshop whenever I "Save for Web" or "Save as" in the sRGB color space, I wind up with over saturated oranges and reds. I'm needing to save in the sRGB for web work. My working color space is set to sRGB which looks fine when editting in photoshop, but as soon as I save it out of photoshop the reds and oranges are over saturated. I purchased the spyder 3 because of the wide gamut support, is there something I'm missing in calibration?
The display profile is not at fault here. The ICC profile for the display tells any application that uses color management what the color values for the display are. Thus Photoshop, which is using the profile, corrects for the colors on screen, giving correct results. A non-color managed application (such as Internet Explorer for Windows) would not use the profile and thus the colors would be oversaturated on your wide gamut screen. This is not the fault of the profile (that would make the color look wrong in Photoshop, where the profile is being used), but the lack of a profile (which makes the color look wrong in non-color managed applications).
This is the problem with using a Wide Gamut display for viewing in non-color managed applications. A typical gamut display is not color correct in such applications, but is at least approximately correct; a wide gamut display is noticably oversatured in some colors. On the Mac many applications, including web browsers and OS utilities, are color managed, so it is less of an issue than on Windows.
Article Details
Article ID: 723
Created On: 10 Jan 2008 07:31 PM
So if the color is off outside PS, then its not the fault of the profile. My problem is the image is off INSIDE PS, and by the same reasoning, then the profile is at fault. If the profile is to blame, is this a Spyder issue or Vista issue? So far noone seems to know anything including Adobe tech support and Dell. Been waiting 2 wks to hear from the Spyder people.
Would really appreciate some input on this. thanks.

Color management issues with Flash CS3, please help?

Hello everyone.
I am having issues with color from a Jpeg image produced in Photoshop CS4
after importing onto the stage in Flash CS3. The color in Flash changes the image to a lighter less saturated state. Yuk.
Here is a link to a screen capture to show you what's happening (for a bigger view):
http://www.rudytorres.com/color/weirdcolor.png
As you can see the front image is the Photoshop image showing the sRGB color profile embedded but Flash (behind) changes that color.
This client is quite picky and she will notice this difference.
If any one can help, please.
- Rudy
P.S. It's a button somewhere, Right?

Dougfly,
Only an hour wasted? Lucky you. Color is an incredibly complex subject. First, forget matching anything to the small LCD on the back of your camera. That's there as a basic guide and is affected by the internal jpg algorithm of your camera.
2nd, you're not really takeing a color photo with your digital camera, but three separate B&W images in a mosaic pattern, exposed thru separate red, green and blue filters. Actual color doesn't happen until that matrix is demosaiced in either your raw converter, or the in-camera processor (which relies heavily on camera settings, saturation, contrast, mode, etc.)
Having said the above, you can still get very good, predictable results in your workflow. I have a few color management articles on my website that you might find very helpful. Check out the Introduction to Color Management and Monitor and Printer Profiling. In my opinion, a monitor calibration device is the minimum entry fee if you want decent color.
http://www.dinagraphics.com/color_management.php
Lou

Colors are different in PS CS3 Vs CS4, Why ?

Hi.
I just found out that colors of a photo in CS3 is not looking the same in CS4 ?
I have a G5 with Geforce 6600 card in and i had to turn of OpenGL because it was so slow when it was enabled.
Then i tried to open both Photoshop CS3 and CS4 at the same time to check a picture and saw for my suprice that the colors was not identical.. Weird.
It is lighter in PS CS4 that in CS3
Also from Bridge CS4 to Photoshop CS4 it was different.
Is that normal. I woulden say.
In my Suite CS3 all colors looks the same in Bridge and PS. OFCAUSE.
I did check my color settings first. They are the same all over (Adobe 98)
Is it a bug or is it because i turned of the open GL settings in PS CS4 ?
If it is because i turned of the Open GL settings in PS CS4, that would be a very bad
thing to do because many people have older computers where the GPU dosent work
well with the Open GL settings ON and you can at least work when its OFF.
But not if the colors are not right.
Please. If someone could replay on this matter. I'm sure more people will like to know
this. I'm not even sure many people noticed this, so everybody.
If you have Creative Suite CS3 and CS4 on your Mac.
Try uncheck the Open GL settings in PS CS4 and restart PS.
Then compare the picture in PS CS3 and CS4 at the same time !!!
Hope someone have some answers ?
Thanks you
Photographer
Erik S.

Hi Chris.
Good news. I cant tell you how happy i am for all your help ;-) and you other guys.
The latest Eizo 5.2.1 software fixed the problem on all 3 Eizo monitors.. Weeee
I'm back to normal.
Now i just have another damn problem started not long ago ;(
My Photoshop CS3 and CS4 keeps crashing on me after a wile of work ???
I tried everything. Deleted preffs etc. etc.
It have been working for long long time but suddenly it keeps crashing all the time.
I tried to remove some new plug-ins, but it was not that.
Only thing i did also was to install new ram.
Upgraded from 10GB to 14GB in all our Mac Pro.
So after i tried to switch the ram around to check if some was bad.
Also run some memory software but everything came out right.
So now the only thing left is that Photoshop dosent like ram between 14GB & 16GB.
Under was fine and i never tried over 16 gigs.. weird
Any ide what could corse this ?

CS4 - Color Management - Multiple Users

All,
Here is what I hope to be a question that some of you have encountered and solved already. I've tried dealing with Adobe on this, and even went as far as to purchase a pricey Gold Support Program, but that has turned out to be a waste of money so far (response times are horrible, and the "engineers" cannot seem to provide anything more than basic application usage support).
I am running CS4 on Windows 7 and I am looking to set up a custom CSF file for standardizing our color management policies across all of our CS4 apps. The workstations will be used by multiple users, so we configure the default account as we would like, and have new accounts replicate off of that.
The problem we are having is that the CS4 apps, and especially Acrobat, what CSF files in:
C:\Users\USERNAME\AppData\Roaming\Adobe\Color\Settings
When I place the CSF file there when I am customizing the default user account, the file would then reside in:
C:\Users\Default\AppData\Roaming\Adobe\Color\Settings
The problem with this is that when new user profiles replicate off of the default account, the CS4 apps prefs point it to that folder for their CSF file, and I get errors, because the new profiles will not have privs to read from that directory.
So, in response to this, I have created a folder in the root of C and stored the CSF there. In Photoshop, Illustrator and InDesign I can load the CSF file from that location manually. Unfortunately, Bridge doesn't see's only the current users color settings folder, so it cannot see it, but if I set the three apps above before I launch Bridge, Bridge recognizes the CSF. The issue is Acrobat, which seems only to see "Custom" for color settings.
Further, when new profiles are replicated off of this setup, it breaks entirely.
So, what I'm hoping is that someone here has had to configure color management for CS4 in a mutliuse environment, and that you may have a strategy for this.
Is there a way to specify the CSF file for each of the apps with a registry key? This would be easiest...
Please, any thoughts are welcomed.
Matt

Further testing yields these clarifications:
Putting the CSF file in a folder in the root of C seems to work well for Photoshop, Illustrator and InDesign. They are happy to have it there and work well in the Default account, and in user profiles that are replicated from there.
Acrobat still displays "Custom" in the list of drop downs for CSF files in Color Setup. The settings look to be configured properly, but the name of the CSF file is not shown, which makes us nervous.
Bridge does not like this at all. Previously I had seen it show the CSF file in the list if all the other apps had that CSF file specified, but I cannot recreate that condition. Currently is says that the suite is not synchronized, and it wants to apply one of the standard CSF files supplied with the suite.
Please help! This should be easy!
Matt

Photoshop CS3 on Snow Leopard color management

I have CS3 on Snow Leopard and an Epson R1900. If I let Photoshop manage the colors the print is dark and on the red side. If I let the printer manage the colors and use the same profile it looks much better. I found this old thread:
http://forums.adobe.com/message/2313020#2313020
Which says it is a known problem with Snow Leopard and Adobe is working on it. Does anyone know if this has been resolved?

Was DYP wrote:
There are a bunch of different ways to attack this problem. Here was a good thread.
http://forums.adobe.com/thread/369773?start=150&tstart=0
I would add two things to your list.
a. Snow Leopard seems to use sRGB as the default profile so I would use that as the assigning profile.
b. You should convert to Edit - Convert to Profile choosing your Printer/Paper profile (for printing color managed output) in PS before you do #1.
that thread is rather busy... its hard to pick out the good information. It seems mostly concerned with CS4. Do you know what issues apply to CS4 only and which issues apply to CS3/Snow Leopard?
I am not sure what you are saying in point a. If I have a custom profile for a particular ink/paper combination I need to assign that profile, right? Using sRGB is only useful if I want no color control at all I believe.
b. Seems to permanently convert the image to that profile, which I would think you would not want to do in general since you generally want to keep the image in its original format.

Print with no color management CS4 + Snow Leopard broken

I have seen comments in this forum about problems with printing with CS4, but wasn't sure that they were going to apply to me. They do, big time.
I print to an Epson 9800, I convert the image to the Epson profile for that paper, and then print using no color management. With CS4 + Mac OS 10.6 the colors are completely off, and the results unusable, and I could not resolve it by printing from CS3 instead. I finally ended up installing 10.5 on a new partition, deactivating CS3 on the 10.6 partition and installing on the 10.5 partition (because Adobe's licensing treats the same program running on the same computer with different boot partitions as two different "installations"!), and then actually going back one generation in the drivers for the printer. Basically this resurrects my computer as it was in 2007, and I can now print flawlessly. I'm not sure whether the latest printer drivers introduce problems or not, and got tired printing test images.
Of course, this means that I edit the photo in 10.6 + CS4, then reboot to 10.5, print in CS3, then reboot back into 10.6. And of course I can't use CS4 while printing from CS3. Very frustrating.
My questions are: (1) is there an Adobe document that discusses this problem, (2) are Adobe aware of this problem, and (3) are there any other work-arounds that people know of other than reverting to CS3 + OS 10.5?
A

Thanks Chris,
I didn't try older Epson drivers + 10.6. I wasn't quite sure if I was getting the exact same colors with the newest Epson drivers + 10.5, so I reverted to the previous version drivers + 10.5 and am able to print perfectly with that.
I must say that Adobe's licensing really gets in the way when there are problems like this. I only updated to 10.6 (yes, perhaps a little prematurely) after reading Adobe's reports on compatibility and searching these forums for any news of problems. But now that I have updated to 10.6, I really don't want to go back to 10.5 permanently. And, as I said, you can't run the same version of Photoshop on the same computer on two different boot systems, without using up the two licenses. This is very frustrating, and violates my understanding of the license that Adobe gives its users: the ability to run the software on either of 2 computers, as long as you don't run on both at the same time.
I hope you figure this out, let us know as soon as you can.
A

Help please. Vista / CS3 Color Managment issue. Going nuts...

Hi all.
I'm in desperate need for some assistance since time is running out on a project that needs Powerpoint.
If I use color management in Bridge and look at my NEF and Jpegs they look somewhat desaturated and lacking vibrance as in comparison to another program, like AcdSee.
When i open up in Camera Raw, and then Photoshop, it looks the same. But hwen I copy to Powerpoint - it looks very vibrant and with a lot of saturation, luminance and hue. But it looks much better "eyecatching".
If I shut of color correction in Bridge, then the picture looks just as vibrant and nice as the end result in powerpoint and it looks just as good as in AcdSee! But the steps in between, that is Camera Raw and Adobe looks awful, and I'm supposed to make some color adjustments etc, making it absolutely impossible to know what the end resutl will be, since the color management is ON in Camera Raw and Photoshop.
I've callibrated my monitor, spyder3, I've set Adobe Bridge to use CS3 for monitor. I've tried alternating between Adobe RGB and sRGB. I've tried everything there is, but the colors in Camera Raw and Phtoshop are very wrong in relation to the end result. Can I shut down color management in Photoshop? Change it to Vista's? I know Adobe is right at the end of the day, it just doesn't work with the end result!
To add on to this, I've tried AcdSee and colors are correct in the RAW format. Thus, they don't have the same color correction and this looks exactly like the end result in the powerpoint.

>> the colors in Camera Raw and Phtoshop are very wrong in relation to the end result
Then you need to Photoshop> Convert to profile> Save As to the profile based on the end result because the end result sounds like an unmanaged application.
This is likely sRGB -- have you tried this?
What monitor, what did you profile it to (2.2 gamma/6500)?
http://www.gballard.net/psd/assignconvert.html

CS4 color management not working

Running under WinXP, 4GB RAM, nVIDIA GeForce 7600 GT with latest drivers:
The image display in CS4 is acting as if it were not color-aware.
Example: I open a file in which is in the ProPhoto RGB color space (and has that profile embedded) and the colors are not displayed correctly (muted and low contrast) -- the same appearance as opening such a file in a non-ICC-aware app like a browser.
Soft-proofing to sRGB does not change the appearance: colors are still wrong.
Converting to sRGB does not change the appearance while still in the dialog box -- even with Preview toggled on.
But upon executing the conversion to sRGB, the colors then appear correct -- again, as would be expected from a non-ICC-aware app.
CS3 running on the same system does not have this problem.

to Chris Cox:
>"Tony - then you'll need to contact NVidia and ask them to fix the driver.."
I'll be happy to do so -- but to be effective in getting nVIDIA to accept responsibility for this problem, may I ask where you believe nVIDIA has done something which needs fixing?
a) Is there a relevant industry standard to which you believe nVIDIA is failing to comply?
b) Is there some specification published by nVIDIA to which you believe nVIDIA is failing to comply?
c) Is there any documentation published by Adobe (e.g., design guidelines for graphics cards manufacturers to assist them in making Photoshop-compatible products) to which you believe nVIDIA is failing to comply?
d) Are there specific generally-accepted good software engineering practices to which you believe nVIDIA is failing to comply?
>"As for your display color management: we haven't seen that. That sounds a lot like your display profile is wrong, but I'm not sure why it differs from CS3. Could you check your color settings in Photoshop and for the display again?"
These look right to me. Are there any specific settings you'd like me to report?

Vista 64 bit and CS4 and color management

This is a question about Vista 64 bit and CS4 and color management. I scan 4x5 film and sometimes end up with up to or even bigger than 1 GB files. Obviously that needs as much memory as possible. Windows XP is limited in this regard and I am in the market for a new speedy computer which won't force me to stay at a snail's pace. In this month's Shutterbug, David Brooks in his Q&A column says to avoid Vista for color management reasons, but offers no explanation or support for his opinion. He implies one should wait for Windows 7 for some unstated reason. With a calibrated monitor and printer and Photoshop controlling color files sent to the printer, why would Vista be any different or worse than XP? Is he on to something or just pontificating? Does anyone know any reliable info about Windows 7 that would make it worth waiting for?
Thanks.

Zeno Bokor wrote:
Photoshop has direct access to max 3.2gb
On Mac OS X, PS CS4 can use up to 8 GB of RAM, but only directly accesses up to 3.5 GB. (Figures quoted from kb404440.) In using PS CS4 on Mac OS, though, direct Memory Usage maxes out at 3 GB even. If you set usage to 100% (3 GB), then plug-ins (including Camera Raw and filters), as well as actions and scripts, can access RAM above that 3 GB to between about 512 MB and about 768 MB total (seems to vary depending on which filters et al that you are using), leaving the rest up to 4 GB for the Mac OS. If you have more than 4 GB, then the amount of RAM above 4 GB is used by PS as a scratch disk. This increases performance significantly for most things because writing to and reading from the hard drive is much slower than doing so with RAM.
I haven't done the testing for actual RAM usage and such for PS CS4 on Vista 64, and Adobe's documentation is very much lacking in detail, but, based on the statement "If you use files large enough to need more than 4 GB of RAM, and you have enough RAM, all the processing you perform on your large images can be done in RAM, instead of swapping out to the hard disk." from kb404439, it seems that PS would be using RAM in very much the same way as I described above for Mac OS, except that the scratch disk usage in RAM wouldn't be limited to 8 GB (instead to how much you have installed). Has anyone done any performance/load testing to know for sure? I didn't see any such studies published, but I am curious if one has been done.
I will agree that there is a definite performance advantage when using PS CS4 (64-bit) on Vista 64, which I've experienced, especially when working very large compositions.
My initial recommendation to the OP to use Mac was based upon reading those articles about bad color management. As I stated before, I have never experienced that problem, and clearly the views of all that have posted here so far indicate that the problem may not be a real issue. (Perhaps this David Brooks fellow and Steve Upton both like to mess with their computers and broke something in Windows?)

CS3 + ID CS4 - Color management Iussues in Bridge CS4

Similar Messages

Maybe you are looking for