Bridge doesn't recognize color profiles

Dear Adobe community,
I'm using Adobe Bridge CS5.1 (4.1.0.54) and Illustrator CS5.1 (15.1.0), and I'm experiencing a very confusing and disturbing color management problem between these two applications. In short, for some unknown reason Bridge doesn't seem to respect or simply cannot read CMYK color profiles that I've applied to an artwork within Illustrator, but rather labels the file as "Untagged" and displays it with clearly desaturated colors. To illustrate the problem I've created some screenshots having Bridge on the left hand side and Illustrator on the right displaying the same illustration with various color profiles applied. That is, in each case I assigned different color profile to the image in Illustrator, saved the file and took the screenshot of Bridge and Illustrator both displaying the image. Now if you look closely then perhaps you notice that the only time I got a visual match between these applications was when I switched the file to a RGB mode within Illustrator. But even then Bridge did not recognized the correct color profile but interpreted it as "Untagged". Here are the screens:
Bridge "Untagged" vs. Illustrator "U.S. Web Coated":
Bridge "Untagged" vs. Illustrator "Coated FOGRA39":
Bridge "Untagged" vs. Illustrator "Don't Color Manage This Document":
Bridge "Untagged" vs. Illustrator "Adobe RGB":
Hope you could see the difference from these tiny images. Looking from my monitor, I can tell you for sure that they are definitely off, except the RGB versions of the illustration. This made me surmise that perhaps Bridge can only display Working RGB profiles correctly and not anything else.
Here's also my color settings, just in case…
So... Why is that??? Why are these applications showing me different results while my color settings are supposed to be "Synchronized"? Is there a way to fix this? I have tried to play around with the settings and looked for a solution in the web but to no avail. Could you please help me to find a soulution to this disturbing problem?
All the best,
Juhani

You may have used the broken global Purge Cache command in Bridge Preferences, or the cache is otherwise corrupted. Try Purging the Cache through the Tools menu in Bridge for each folder. Tools > Cache > Purge cache for 'foldername'.

Similar Messages

  • Bridge doesn't recognize its own .xmp files

    Using Bridge CS3 on Mac OS 10.5.8. I edit RAW (.nef) files in ACR. When I click done, save, or open image, an .xmp sidecar file is generated and saved in the same folder as the .nef. However, changes made in ACR do not show in the preview thumbnail in Bridge, and when I re-open the file in ACR, my changes are lost. The .xmp file is still there, it's just not applied. It's like Bridge doesn't know the .xmp file is there. The icons in Bridge indicating altered develop settings or crops do not appear after adjudstments are made. Star ratings made in Bridge remain. When this issue began, it would ignore sidecar files for some images, but not others. It is increasing in frequency, or may now be consistent. (If I open the file into Photoshop or save an image file out of ACR, the changes are applied to the developed image file, they are simply ignored by Bridge in regards to the Raw file.)
    Files that were adjusted before the problem began still synchronize with their sidecar files. Looking at the sidecar files in a text editor shows that they contain the adjustments made.
    There were no changes in any installations/updates to software or OS at the time of the problem's onset.
    I've tried using a Camera Raw database instead of sidecar files, and the changes are still lost. I've tried purging caches for Bridge and for ACR. I've tried resetting and dumping preference (.plist) files.
    Anyone have ideas on what I can do to salvage this program as my RAW library manager?

    Matthew,
    Same problem here. But I'm using CS5 in Win7.
    Bridge cannot find its XMP files. Bridge does not see its XMP files. XMP files do not work. Camera Raw settings do not show in thumbnails. ACR settings lost.
    I just now figured out the problem/solution.
    In my case, the association between CR2 files and Bridge was usurped by Canon DPP (the Canon raw converter) which I just installed this afternoon. When I installed it, there was no immediate problem. But when I started a new work session tonight, Bridge acted as if the XMP files weren't even there.
    Solution: In Windows, to set a file association, you just right-click on a file (in this case the CR2 file) and select "Open With", and then navigate to Bridge (in my case Bridge CS5). That re-establishes the link between Bridge and its own XMP files. Then simply purge your cache and let Bridge rebuild it using its XMPs (which it can now find again) to rebuild the cache with the adjustments that are stored in the XMPs.
    I don't know how to do this on a Mac, but the principle is the same.
    I hope this solves your problem.
    Dave

  • Current CS4 Bridge doesn't recognize Olympus E-620 RAW.  Why?

    1.  I have updated everything via Adobe updater (AUG 2009) and yet Bridge doesn't render the Olympus E620 RAW files as a thumbnail.    Does anyone know what in the world is going on? 
        This shouldn't be the case because adobe does support the Olympus E620 RAW files;  I'm able to use DNG to convert the E-620 RAW files to DNG.   The current version of ACR also is able to open up the E620 RAW files.    Thus, there is just some strange thing going on with Bridge in which it can't render a preview of the RAW file. 
    2.  Any help much appreciated because this is really driving me nuts. 
    Thanks.  Harry Shin

    Have you already tried to purge the cache. Point bridge to the folder with
    the icon files and go to the menu tools / cache / purge cache for folder.
    some strange thing going on with Bridge in which it can't render a preview of
    the RAW file.

  • Bridge CS3 doesn't show color profiles althought they are there

    I have a folder with various TIFF files, some are in CMYK (Fogra27), some in RGB but none show the profile in Bridge, although I turned it on in the settings. I can see that they have profiles in PsCS3.
    What may be the cause?
    Thanks!

    You may have used the broken global Purge Cache command in Bridge Preferences, or the cache is otherwise corrupted. Try Purging the Cache through the Tools menu in Bridge for each folder. Tools > Cache > Purge cache for 'foldername'.

  • Is there a way to Uninstall ACR 5.5 and reinstall 5.4? Bridge doesn't recognize this version.

    Hey there. Running Mac os x 10.5.8 on a MacBook Pro...
    I had to reinstall my whole CS4 Master Creative Suite because a couple of the programs went missing.
    First step was uninstalling all the other programs and preferences through Adobe unistaller, then reinstalled and did all the updates. (Photoshop is 11.0.1 now).  All updates finished loading successfully except that it was having trouble with the camera raw 5.4 update. It would say it was installed but when I checked the version in photoshop it would say it is the 5.0.0.178 version. So I updated the camera raw to 5.5 (because I use a Nikon D5000).
    5.5 plugin now works fine in Photoshop but in Bridge, the camera raw preferences is "greyed out" and I can't read any NEFs.
    Don't know where to go from here. The plugins folder in the root Library shows one plugin in the cs4 folder and that is the 5.5.
    When I try to install the 5.4 version again, it reads that it can't install because I am running a newer version.
    Thanks for your help. Got some NEF editing to do and this is a major obstacle....
    Johnny G

    Thanks Jeff. The full path is HD/Library/Application Support/Adobe/Plugins/CS4. It was automatically installed.
    Also, the programs went missing because my computer froze and when I rebooted, any programs that were running at the time were no where to be seen, in the apps folder, in spotlight, the trash, etc. It's a mystery to me and I was a IT tech for quite a few years until recent. (Perhaps aliens abducted my programs.) That's the best I could figure out. Even my Entourage went missing and I needed to reinstall this and import an archived folder of mail - lost the most recent email...
    I bought this computer new a few months ago and have updated to 10.5.8 by the normal "software update" function.
    Purging the folders did not work because Bridge still does not recognize that there is a camera raw plugin installed. The "camera raw preferences" still remains "greyed out" when you click on the Adobe Bridge CS4 tab in Bridge.
    Also, when I go to the Adobe uninstaller, I'm not able to uncheck mark the box for the camera raw....
    Perhaps there is a link to just the 5.4 plugin (standalone?) that I can exchange for the 5.5? The camera raw folder in Application Support/Adobe has all the latest camera preferences including the D5000 which just was updated in ACR. So maybe just making a switch? Or is that too old school?
    Oh yes, created another user account, repaired permissions and any disk issues - yet, same problem.
    Thanks again!
    Johnny

  • Elements 7 (Trial) doesn't recognize ICC profiles in computer

    I downloaded Elements 7 for a 30 day trial to see whether it does better than Elements 5 for my purposes.  I have Windows XP.  While trying to do a test print, in the Print Window I set Photoshop Manages Color under Color Handling. I then clicked the drop down menu for Printer Profile and that menu does not contain any of the ICC profiles in the Colors folder in my computer, but only has those profiles that must come with Elements 7.  Do I need to do something to get this to work? Is it a problem with the trial version?  Adobe Support will not answer questions over the phone for the trial version, although I asked.  Any help would be appreciated.  Thanks.

    Dear John - You graciously replied to our thread last week about ICC profile
    list in Elements 7.  We were wondering whether you could help with another
    more general problem we're having.  We have not been able to get what we see
    on our monitor and what we get out of our printer to reasonably match - the
    prints are always significantly darker than the monitor.  It makes working
    on Photoshop Elements virtually worthless, as we can't rely on getting out
    what we see after making adjustments to our photos.  We bought a Colormunki
    to calibrate the monitor and create paper profiles, but that didn't solve
    the problem and we have worked with the Colormunki people for weeks and
    haven't made any progress.  We have an Epson Stylus Photo R2400 printer and
    a Samsung SyncMaster 2253BW monitor.  We think, at this point, that the
    monitor maybe the problem - apparently it is known for its excessive
    brightness - as even with the calibration set for very low brightness, the
    problem remains.  Anyway, our question is whether you can recommend a
    monitor more likely to give us a reliable match to the printer - what
    photographers/photoshop  users use??  alternatively, any ideas where we can
    contact people who might be able to help????  Thanks in advance for your
    help.

  • ACR 5.5 doesn't show color profiles...

    ...although they are installed and were installed a few times :/
    When I open a RAW from sony alpha 350, it only shows Adobe Standard, Adobe Standard beta 2 and Adobe 4.4 profiles I don't even know how the list of profiles should look because it NEVER showed me any other profiles than these 3
    I am using CS4 with ACR 5.5 on 32 bit windows XP sp3
    HELP!!!
    p.s. I did most of the tricks i found here incl. manual installation and updates :/
    i can't find the profiles on my disk either, although i have installed them many times :/
    seems like if they install somewhere, but i can't find them anywhere on the pc
    another edit:
    The FAQ says the profiles should be saved to :
    C:\Documents and Settings\All Users\Application Data\Adobe\CameraRaw\CameraProfiles
    after installation i still DON'T have that folder on my pc although it says it installed OK...

    You say you're having issues with all colors using with ACR 5.5 but didn’t have issues, previously.  What is the most recent previous version of ACR that you used when the colors appeared to be ok?  Was it ACR 5.4 or ACR 5.1 or ACR 4.6 or ACR 4.4?  I think there have been a couple different revisions of the camera profiles (Adobe Standard for your Sony) but nothing recently.  So I wonder if the issues you're seeing have been there all along and something is different with the photos or the processing where you're noticing the colors being off.
    Also, a monitor profile could make things look different.

  • Bridge doesn't recognize CS5 products

    I recently installed CS5. Shortly after I noticed CS4 was still also residing on my hard drive, so I uninstalled CS4. Now Adobe Bridge CS5 does not recognize that the other cs5 products are installed. It won't open .psd with photoshop or .ai with illustrator, etc. Even if I right click and select "open with" I do not get the option to select the appropriate cs5 product. What's going on here?

    It is not a problem to have different version on the same computer, they are all seperate products even if labeled upgrades.
    Sometimes problems occur when the old version is uninstalled after the new version is installed.
    I would go to Bridge edit/preferences/file type associations.  Look at what is has listed for defaults.  If it is not CS5 go down to the bottom of page and press radio button to reset to factory defaults.
    Hope this clears it up.

  • Since recent CC upgrade, Bridge doesn't show colors of labels. What gives?

    Hi All,
    Just upgraded CC and all of a sudden all the thumbnalls in Bridge show white bars instead of labels on the thumbnails. When I go to the Filter I can select to view only those with green, red, or whatever, so the information on what the color is is there. Is this just my problem or is it a bug? This is the Mac version running Mountain Lion on a 13" retina display.
    Thanks,
    Ed Merrin

    Thanks, Omke. You helped lead me to a trail that solved the problem, although how it came to be is not too clear. I thought it would be good for me to describe the specifics in case someone else encounters this.
    Briefly, I have used the label colors for years, through multiple versions of Bridge, to help organize and sort through images. It has become second nature to me. I recently went traveling and came back and began sorting through and labeling my new images. Everything seemed fine, but in retrospect I was paying attention to the color of the label and not the name attached to each color.
    Eventually the time came to do something with older files, and that's when the problem surfaced. All the labiels were white. When I looked at the filter panel, the thumbnails in the browser would be correctly identified by the text name of the color,but no colors would be displayed. For instance, if I selected the word red (but with a white circle next to it), only the "red" thmbnails would be in the browser, and the same for any other "color." So they could be identified, even thought here was no way to tell them apart visually by label, since they were all white. On the other hand, the newer files, although they had red or green etc under the thumbnail,were identified as something else. Specifically, red was "Selected," and other colors had other terms I can't remember. The transition was easy to find. All files labeled from October of this year to the present had the new monikers and showed colors, whereas everything before (back to 2006) were white.
    So I went to the preferences, and lo and behold each color had a word next to it (as I mentioned above red was "Selected") instead of the name of the color, as it had been before.
    It was much easier to change the newer files than thousands of old ones, obviously, so I changed the preference panel by typing the color names in to replace the other categorie names that some greater authority had apparently invented. Bingo, all the old files now had color labels and it was the new ones that were white! That was easily fixed by changing labels of the new files in the drop down menu to the appropriate color name  (the colors names were unavailable until I changed the preferences).
    Apparently, around the end of September or early October my preferences were changed, probably after an update, and I never noticed. Previously, whenever I  updated Phtotshop/Bridge the preferences were carried over without any intervention from me.
    So go figure.
    Ed Merrin

  • Bridge doesn't recognize Oly E-620 files with ACR 5.4 Beta

    hi:
    1.  the good news--> ACR 5.4 is working well as well as DNG. 
    2.  problem:  when i open up bridge (CS4), the new RAW files (example:  olympus E-620) don't show up as thumbnails.    i looked around in the preferences, but couldn't see anything that would fix this situation.   any help appreciated.
    thanks.  harry shin

    hi:
    1.  thanks for the reply--> but purging the cache didn't help. 
    2.  in re: installation, perhaps there is a different way to install ACR 5.4, but all i did was run the installer.  ACR is certainly working within photoshop CS4 and thus i'm assuming that it should be working in bridge (?)
    3.  any further ideas appreciated.
    harry

  • Bridge doesn't recognize Quad Processor

    When I bring up adobe bridge I get a warning:
    "This application requires a Pentium 4, Celeron, Core Duo or Core 2 compatible processor. 0/6/5898."
    I have a brand new Dell 32-bit Vista with Intel Core 2 Quad CPU Q9400 @ 2.66 GHz with 8 GB Memory RAM. What could be the problem? Any guesses?

    To save you the trouble:
    Adobe has stated that this message appears in error and can be ignored.

  • Bridge doesn't recognize processor

    Hello,
    I'm using Bridge CS3 2.1.1.9 under MS Vista Home Premium, Processor is a Intel Dual Core E8200.
    After starting Bridge, I get the message (copied from a different thread):
    Adobe Bridge
    This application requires an Intel Pentium 4, Intel Celeron, Intel Core Duo or Intel Core 2 compatible processor. (0/6/5894)
    This application may perform poorly. Are you sure you want to continue?
    Thank you for your help
    Jürgen

    I am convinced that Bridge is the "Red-Headed Step Child" in Adobe's arsenal. So I doubt that Adobe is listening to anyone here. If you just purchased your CS3 application for your new machine, I'd call Adobe for tech support as an installation issue and see if that gets you anywhere.
    The current version of bridge is so unstable and slow on my system that I was beginning to think that maybe the people who don't have any issues with Bridge and suggested that my system was to blame might have some merit afterall. But after installing the Lightroom Beta preview and using it on this system for over 3 weeks, I am convinced that there is nothing significantly wrong with my system. Lightroom 2 is "lightning" fast and rock stable on this system doing the same sorts of tasks that bridge bombs or chokes on. The performance is simply night and day between the two applications on the same system. And we are talking about a beta version compared to a production version piece of software. Functionally, there are several aspects where I prefer Bridge over Lightroom. But if Bridge is so slow that it fails to function, its advantages are worthless. While Bridge bombs off constantly, LR beta has NEVER bombed off once.
    So my user suggestion is to dump Bridge altogether and buy Lightroom. I was really frustrated with Adobe's decision not to include Lightroom in the so called "Master Collection" of all of their CS3 programs. But now I am just giving in to Adobe's strategy for everyone to purchase LR as an add on to the collection. Each point version of Bridge has produced more and more instability on all of my systems without adding significant functionality. So I have come to the conclusion that Adobe wants Bridge to die an unnatural death so they can make more sales with LR. And honestly, their strategy here is working with me. Bridge is just so unstable for me that the time-loss I suffer in continuing to use it outweighs the cost of purchasing LR.
    Again, my user suggestion to all who are having problems is to download and try the demo or beta version of LR and switch to using it instead of Bridge.

  • Why is Bridge reporting color profiles incorrectly?

    Why is Bridge seeing this image as an Adobe RGB when it is really Colormatch RGB?
    I am using CS5 on Windows 7 64bit. I have purged the cache and did a full restart of the OS.
    1.       The top dialog is Bridge and it is reporting the image as Adobe RGB (1998) in three places.
    2.       Next, with Photoshop’s rgb color setting is set to Adobe RGB and I get an Embedded Profile Mismatch.
    3.       I reset the color setting to Colormatch an opened the file without a mismatch. The status bar Document Profile confirms Colormatch
    4.       In the convert to Profile dialog, the source profile is Colormatch. (Is this a reflection of the working space setting?)
    5.       In file Info Raw Data Colormatch is reported.
    6.       I then opened the image as a TXT file and found a tag for Colormatch. There is no reference in the TXT file or Raw Data to Adobe RGB (1998).
    Why does Bridge report this image as Adobe RGB (1998) when the file seems to have no reference to Adobe RGB?

    I am assuming that some remnant of a former state of these files is causing Bridge to report the color profile incorrectly.
    I made a workaround to fix these files by creating a Droplet (With 'Save on Close' and 'Override Action "Save As" Commands.)  to run an action with the following steps:
    Convert color to Lab.
    Convert color back to RGB. (Working space:Colormatch RGB)
    Assign Profile to Colormatch RGB.
    Save As. (With ICC Profile: Colormatch RGB checked.)
    Close.
    With Profile Mismatch Warning set to' Ask When Opening', the droplet stops on any images that are not Colormatch and resumes after making a selection.
    This is correcting the files and they are now reading correctly in Bridge.

  • Bridge doesn't load files to layers in Photoshop

    I recently uninstalled Photoshop CC 2014 and loaded Bridge CC 14.0 because of a known bug that ca
    uses focus stacking to not work in Photoshop CC 2014. Now Bridge doesn't recognize Photoshop. Adobe help told me to update my Photoshop, but that would bring me to v. 14.2.1 which has the focus stacking bug. Any ideas?

    Yep if I zoom in like 1000% I can clearly see which layer is too big.  It's like when I'm using the marquee tool to select the area, snapping to the grid of guides, some times it's selecting 1 row or column of pixels too many.  I can then fix it but I basically have to redo it those sections (bring back in the original bg elements etc).
    The margin of error has to be what it is.  The buttons are not just floating in space, they are on a background that I want to be a part of the popup menu.  So the background becomes part of the button on the popup.  If it's not perfect it is noticable.
    On some occassions the highlight is the culprit, it's too big or needs to be moved a tad to fit within the rectangle.
    If there was a slice to layer option it seems it would solve everything.
    thanks

  • Confused about color profile support in PNG

    NOTE -- you have to hover over the image to see the real images.  The images embedded in the webpage have their profiles stripped -- just like photoshop does!  Interesting.
    I ask a similar question on this before, but couldn't give a satisfactory demonstration of how photoshop doesn't support color profiles in png's.
    But now I have a great one.
    Picture A: this is with the correct color profile and displays correctly in firefox and probably other browsers -- also displays correctly on windows desktop and in large-icon view. 
    Ok, anyone who doesn't believe me, grab that image and try to read it into photoshop...
    I do, and get no warning on profile mismatch like I do on jpg's or tiff's:
    photoshop strips the existing profile and adds sRGB which isn't the correct profile.
    This is how photoshop transforms good colors into bad:
    Completly screwed up.
    I have had multiple people notice how my png saved images from photoshop had "off" or bad colors -- usually washed out in comparison w/my monitor profile.
    I can get 'ok' results if I flatten the image and *convert* my existing profile to sRGB -- and I usually get
    something that looks 'acceptable'...though the jpg's render in accurate color.
    Basically, photoshop can't read or write png web images. and maintain color fidelity unless they have no profile.  Even if they have an sRGB profile, I usually get washed out looking pics if I don't strip it but let adobe convert it.
    In googling for my own problem, I found references to this problem in Adobe Photoshop going back to 2002.
    Why does adobe refuse to fix this?  It's horrible.
    They could fix it with a file plugin for existing CS5-6 users, but it really needs to get fixed and Adobe needs to stop ignoring this problem.
    :-(  I find this extra depressing because I prefer to distribute my pictures losslessly in png,  but with photoshop, I'm left with lossy jpegs to get accurate color reproduction.

    How did the SFW thing even come up??  When I embed profiles in jpg and tiff, I do it as part of the File Save or File Save As dialog.  I can choose what profile to save it with -- and I usually save it with my currently calibrated monitor profile -- as that color profile is what was used to create the picture.  Why would I want to convert them to some other profile??  Only thing I have needed to convert have been PNG's because it doesn't embed my monitor profile in the PNG the same way jpg and tiff do.
    If it did, png's would look the same as jpgs and tiffs... but the jpgs and tiffs have the full depth of color and look the same as they do in PS.  png's look washed out because -- it's been my belief that PS is not storing my profile in the png, but setting a bit in the file to use the sRGB profile. 
    AFAIK, PNG provided for a sRGB profile-compat bit -- so images that were compat w/that profile could just set a bit rather than including a profile.  I see no evidence that PS is saving my monitor profile with the PNG.
    My 'settings' for RGB are to convert to working RGB profile which is my monitor profile.
    I do have it set to ask me abou profile mismatches on opening or pasting.
    Since I don't get a 'this document has a different color profile than the working space'
    message when I edit most png's, I assume it has none.  Thus from my settings
    it should autoconvert it to my monitor profile and save that on save -- which seems to be what happens when I save as jpg or tiff (or I can check off the box to save profile...but I usually don't).

Maybe you are looking for