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.

Similar Messages

Realtime Ram Preview Fail in Color Management is on

Hi. I m work with Ari Alexa footage as shown VIDEO: After Effects and Alexa - The Expurgated Version by ChrisZwar And I enebled mercury transmit in video preview preferences. When I want to ram preview After effects does not preview in real time. In info window appearce red text fps: 0,6/25 (NOT realtime) Note: project working color space is on
What should I do in this case

BeraT, if you disable Display Color Management (View menu > Use Display Color Management) and Mercury Transmit, do you get real-time playback during RAM preview?
Display color management and video preview in After Effects both impose a processing burden. As each frame is sent for display, additional work must be done to apply a color transformation or a dimensional transformation, respectively. If you have both color management and video preview enabled, both transformations are applied, plus an additional color transformation for the Mercury Transmit monitor. None of these transformations are cached, they are done live, on-the-fly and require additional processing at playback time.
The net result is that both color management and video preview require more processing power during playback. Larger frames, higher frame rates, and higher color bit depth increase the amount of processing power required, due to the increased memory requirements of the frames.
A faster processor would help give real-time playback more often, but you can also increase playback speed by lowering the memory requirements of the RAM preview frames: reduce the resolution in the Composition panel or the playback resolution in the Preview panel, reduce the project's color bit depth setting, or reduce the Frame Rate or increase the Skip rate in the Preview panel. Disabling the Use Display Color Management option will also help, as it removes one of the processing steps.
All of that aside, if you aren't able to achieve real-time playback when both Display Color Management and Mercury Transmit are disabled, that tells you the problem is coming from somewhere else. You'll need to provide more information about what's happening in your comp.

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 + 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

Color manager bug in illustrator cs5

i try to change objects colors via the color manager with a cmyk code for the new color. the color of layers i changed already changes while i'm changing the other layers. It takes 5-6 time before the right color stay. why? is it a bug? i would like to set the same color for all layers ...thanks

Confirmed this is being generated entirely in CS5. I opened the font Sabon. I created a text box. I pasted in some generic type I had just made in text edit. I changed the font to Sabon and the paragraph to justify. I saved and closed the document and closed Illustrator. I closed Sabon and opened Sabon from another foundry. I opened Illustrator and opened the document. All looked good. I duplicated the text box over and outlined the type. I went into the font manager and closed Sabon. I opened the original Sabon. DING! Type reflow. I saved as a second document. I copied the outlined type and closed the document. I opened the original document (note the original font is open). No problems. I paste the outlined type (type outlined with the wrong version of the font active) and it lands exactly in place. I open the second document. The type that reflowed now gives me the stupid message about another version of Illustrator screwing it up. I hit OK and the type reflows back to the way it is supposed to be.
This proves that the kerning changes weren't due to differences between the fonts. This proves that Illustrator CS5 has a MAJOR type engine bug that could easily spell disaster in production.

Adobe Updater ask me to update to Bridge CS5 4.0.2 after applying Bridge CS5 4.0.3 Update

Downloaded the Bridge CS5 4.0.3 updates from Macupdate and Adobe Download Update site, and have installed it. The installation process went fine, and Adobe CS5 4.0.3.9 as shown in the About dialog, run fine.
However, when I hit "Updates" from Bridge CS5 Menu, the Adobe Auto Updater started and prompted me to upgrade to Adobe Bridge CS5 4.0.2.
Version 4.0.2 is the prior version on my Mac before applying the new upgrade to 4.0.3.
If I hit Update, Adobe Auto Updater will download Bridge CS5 4.0.2 and install fail.
I think 4.0.3 update is not yet integrated into Adobe Auto Updater.
Please fix this! Or I'm the only one who have this problem?

FranNStein wrote:
… I can't believe that Adobe is ignoring this. There must be a fix for this problem...
You need to understand that Adobe is a huge, inefficient and unresponsive bureaucracy.
Not only are the engineering teams for the various applications in the creative suite in different cities but in different states. The installer and updater teams are also separate entities.
Even Adobe program managers have lamented publicly that the installers and updaters are a huge embarrassment to them. Privately, some of them regret that they can't say publicly what they would like to do to members of the installer and updater teams.
The false-positives have been showing up intermittently for many years. At other times, the updater fails to inform you of available updates, or the installation through the updater will fail or be incomplete.
As I said earlier, I just ignore the auto updaters and perform all my downloads and installs manually—for all my Adobe applications. I've been doing this for at least six years, possibly even longer, and I've never had a problem this way.
Wo Tai Lao Le
我太老了

Lightroom 3 sliders lose color shading after upgrade to Mavericks...any help?

Just recently upgraded to Mavericks OS on Mac, but now finding that the coloring of the sliders (for example in the Hue, Saturation, Luminance module) is gone. This is really annoying as I cannot see what the color will look like unless I actually move the sliders. Does anyone know how to fix this?
Thanks

Known issue with LR on OS X Mavericks
http://helpx.adobe.com/lightroom/kb/sliders-lightroom-all-white-look.html
Only solution Adobe currently offer is to upgrade the LR5.2 where it is fixed (but not in earlier versions).

The white color become blue in Bridge CS5

the same photo I open in Photoshop and Bridge
but inside Bridge it become so blue tone~!
is it the ICC profile or any color preview setting not correct?
Pls. advice., where the manual set up??
thx

It's jpg file,
I check in my colleague computer, seem haven't happen in her .
just my computer. not sure am I set up something by mistake

The what color become blue in Bridge CS5

the same photo I open in Photoshop and Bridge
but inside Bridge it become so blue tone~!
is it the ICC profile or any color preview setting not correct?
Pls. advice., where the manual set up??
thx

It's jpg file,
I check in my colleague computer, seem haven't happen in her .
just my computer. not sure am I set up something by mistake

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.

Wrong print preview and printed color from Lightroom 1.3

I am running Vista Ultimate and i just installed the driver for my Canon PIXMA Pro9000.
When i try to print from Lightroom 1.3 the colors are very muted, even when i do print preview the colors are wrong in the print preview screen.
No matter what i do i cant seem to get lightroom to Print Preview AND print with the right colors.
The image on this link http://www.pbase.com/charld/image/94711330
(on the left) is what i see and get when i do a print preview and print and my monitor image is on the right.
If i use Canon DPP the colors are not that bad, its a bit dark but that was easily fixed and i can get it quite close to what i see on the screen. My monitor is not calibrated..The images were all shot in RAW and converted to DNG...Do i need to re-install Lightroom as i don't think print preview has anything to do with the printer i have attached....
Thanks

I got the solution from another forum:
http://www.lightroomforums.net/showthread.php?t=1613
1. in the Print module, clicking on the Print Settings button ...
2. Choose your media type
3. Under Print Quality choose High
4. Under Color Intensity choose Manual. In the subsequent dialogue box choose None.
5. In the Print right hand panel under Color Management choose your print media - PR1 for Photo Paper Pro, SG1 for semi-gloss &c
6. Rendering intent Perceptual.
7. Hit Print and OK.
this resolved my issue!!

No MPEG preview or playback in Bridge CS5

After doing a clean install of CS5, everything seems to work well except for Bridge.
HDV mpeg clips will not display a visual thumbnail
or playback in preview window of Bridge. When double-click
ing icon, I get an error "Windows
cannot find '%ProgramFiles(x86
)%Windows Media Player
\wmplayer.exe'.
When I double-click an AVI file, Bridge finds and uses Windows Media Player just fine.
Need MPEG preview badly!!!!
MPEG clips are working fine in Premiere Pro CS5 and AME rendering is awesome!!!
Thanks, rg

Hi Rick,
Regarding br asc's reply:
can you purge the video file in thumbnail panel to get new thumbnail?
I can playback mpeg video in bridge on my windows 7 64bit machine.
I am not sure what you did or what exactly did br asc meant.... Anyhow, let me describe my problem and what I did to overcome it:
My Problem:
In Bridge CS5 version 4.0.2.1, I am having problem previewing .MOV files. My .MOV files are from various source such as iPhone, 5DII, 7D, 550D and a few camcoders. The funny thing is some .MOV files preview ok while others not. It is not source dependent either as I've checked, by that I mean something like I have two .MOV files from say, the 5DII, with exact same settings when recorded, why does one preview ok and the other not in Bridge CS5???
What I did:
(1) In Bridge, go to menu
Edit > Preferences (or Crtl K for Wins), go to the File Type Associations (on left pan) and make sure QuickTime (.mov) is associated with your QuickTime Player on the right pan.
(2) In Bridge, go to menu
Edit > Preferences (or Crtl K for Wins), go to the Cache (on left pan) and click the [Purge Cache] button on the right pan to Purge All Cached Thumbnails and Previews.
After doing (1) & (2), I am able to preview every .MOV in Bridge CS5.
Not sure what I have done different to anyone else, but it seems to work for me. Hope it helps...

Color Managment and CS3 Confusion - new LCD

Please help, I'm just learning about how Ps handles color and this is driving me nuts.
I'm using Ps CS3 in Vista 32-bit. Just got a new Dell 2408wfp LCD monitor. I'm using the default color profile it installed with monitor (specific to the monitor, not a "generic monitor" profile). Picture colors look great in Ps workspace. When go to "save for web" the images look way oversaturated (more orangish). In the save for web options, it's currently set to "uncompensated". If I change it to "Use document profile" or "standard windows color", it looks correct in "Save for web" preview. However, if I save it with either of these 2 settings and open it in IE, it looks bad again. In Ps, under "edit", my "color setting" is set to "North American General Purpose 2" with the workspace set to sRGV IEC61966-2.1. If I got to view -> proof setup -> and select "monitor RGB", the Ps workspace looks just like the "save for web" preview. My "Color Management" in the Vista Control Panel has the following settings:
Devices tab, ICC profile = Dell 240WFT color profile, D6500 default.
Advanced tab, device profile = system default (sRGB IEC61966-2.1)
Advanced tab, viewing conditions profile = WCS profile for sRGB viewing conditions.
What is going on here? From the forums it seems like either Ps is wrong or my monitor is. Which version is truly in the image? What I see in Ps workspace or in the "save for web" preview? In this scenario what version would my website visitors see (bad or good image color)? Could Ps be "correct" and saving without a color profile when "save for web" and then IE is using my monitor profile and therefore looking bad? How can I fix?
Thanks in advance!

"What was confusing to me is ON MY MONITOR it looks good in Ps. "
What's confusing about this. Of course it looks good on your screen. Ps is using your monitor profile in conjunction with the workspace profile to display correctly. As soon as you view that sRGB image in Monitor RGB, which is what your other apps are doing, the on screen view goes to hell.
"If I then follow that logic, I should just ignore the SFW and final visualized output on my monitor in my workflow and hope my end users visiting my website don't have wide gamut monitors with goofy color profiles?"
Yes, that's about the best you can do. Actually embedding the profile and pushing for profile aware applications like Safari to become more widespread.
"Seems like this approach doesn't correct the problem for me or visitors to my website with a similar monitors. And if the issue is just my monitors color profile, why don't all images on the web also look color shifted on my monitor?"
How far off images look depends a lot on the image in question. Some types of images don't shift very much at all while others look hugely different. Also, if you're looking at images other than your own, you have no idea under what conditions (viewing and calibration) those images were adjusted. There are so many people, even professionals, who don't yet understand color spaces and calibration that you can't take anything for granted unless you do it yourself. For instance, I work with a lot of stock images from agencies like Getty and even though most of the files have embedded profiles, almost all of them were corrected by people who had no idea of how to properly do color and tonal correction, yet, somehow, you have to assume they thought the images looked great on their systems.

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 help - exporting JPEG

The attached image was shot in RAW (Nikon D70 NEF) and imported to Lightroom 1.3.1 for some contrast and toning tweaks. The image on the right is shown as LR displays it. When I export it as a JPG, however, and open the image in Photoshop or InDesign the image (as shown on the left) is much more red. I'm using sRGB as the exported colorspace and the same as the working space in PS and ID. I've also tried exporting using AdobeRGB and ProPhoto RGB with similar results. What's going on? I'm using a MacBook Pro with OS 10.4.11.

What are you using to calibrate your monitor? And how are you calibrating? Does the jpeg look wrong in preview.app (a color managed app that cannot be wrongly configured, contrary to Photoshop) too? We have seen some cases here of certain calibration devices creating bad monitor profiles. Sometimes it helps to simply select the default color profile (Color LCD on most Macs) to see if the difference disappears or to try another calibrator. Make sure your calibration software only creates a single rendering intent. Differences between Photoshop and Lightroom are usually caused by the calibration software creating a perceptual intent next to a relative rendering intent. Lightroom uses perceptual if available, while Photoshop uses relative. You can check whether this is your problem by softproofing in Photoshop to the monitor profile. Do not check preserve RGB numbers and select perceptual as the intent. If it looks the same as Lightroom, this is your problem.

Preview panel loses Color Management after Minimize Bridge CS5

Similar Messages

Maybe you are looking for