I have just updated my Bridge and Photoshop to their latest versions (November 2019, see detailed version info below).

**** See also update below (Bridge may now use PNGs for thumbnail/preview files in the cache for certain layered PSD files!)

It seems that there are some problems with color management in the new Bridge.
The previous version which I have used until yesterday worked OK. Nothing changed in my system except new Adobe apps today. !!Except: Updated my graphics driver just before Adobe apps (see version info below).

I use Bridge/Photoshop for photography. In Bridge the previews and thumbnails Bridge looks OK for old photos (JPEG, PSD, Raw). However, when editing old PSD files or when creating new PSD documents, the preview for the new files will (often) be wrong. What I observe is about the same effect as I get when I view photos with an application that does not support color management. Since my monitor has a wide gamut LCD panel, the difference is quite pronounced, with oversaturated colors etc.

I have done some experiments and below is a description of a procedure that in my case is able to reproduce the problem with a few simple steps.
Also, when opening a Raw file with "Open Image" in ACR (yielding a flat image in the background layer), the preview in Bridge is OK.
When opening a Raw file with "Open Object" in ACR (yielding a smart object with no background layer), the preview in Bridge is wrong.

The problem can be demonstrated like this:

1) create a new document in Photoshop (try sRGB, color managed first)
2) fill the new document with a solid color (medium bright, medium saturation, I used green)
3) save the document
4) the preview in Bridge looks OK
5) create a new document in Photoshop (try sRGB, color managed first)
6) unlock the background layer
7) make a copy of the layer (yielding two identical layers with a solid color)
8) save the document
9) the preview in Bridge is now wrong (it is easy to see the oversaturated color)

Seems to have something to do with the use of layers?

**** UPDATE: I just found out that it seems that Bridge now erroneously
generates (non-color managed) PNG files for thumbnail and preview files in the cache for certain layered PSD files!!! More info in the posts below.
Have a look at the image files in the cache file location (Windows):

C:\Users\jjoha\AppData\Roaming\Adobe\Bridge\Cache\v36

I tried turning on "Use Software Rendering" in Bridge Preferences, but it did not seem to have any effect on this problem (PNG files still made for files with wrong looking previews).

Version numbers for software/hardware used:

• Adobe Photoshop Version: Adobe Photoshop 2020 Version: 21.0.0 20191018.r.37 2019/10/18 x64


• Bridge Version: Adobe Bridge 2020: 10.0.0.124 x64


• Adobe Camera Raw Version: 12.0.0.322


• Monitor: Eizo CG2730 (calibrated regularly with Xrite i1 Display)


• Windows 10 Pro x64 version: 1903 - Os build 18362.449


• Graphics driver: Driver version: 441.12 (GeForce GTX 1060 3GB)

Just double checked turning on/off "Use Software Rendering" (with Bridge restart/PC reboot). In my case this setting does not seem to have any effect on the problem. Turning on "Use Software Rendering" just makes 100% previews slower to show up.

Also, for the files in question, Bridge still generates PNG files in its cache (which are non-color managed and are shown with oversaturated colors etc. on a wide gamut monitor), for both thumbnails, standard previews and 100% previews. As far as I can see this is new (erroneous) behavior.

To the manager of this project. Please make everyone a favour and resign. Let someone else take over this project. Scratch last 2 years of coding and build on last stable working version from 2018.
I have made a mistake of installing Bridge 2020 after 2019 fiasco. I thought that maybe maybe after another year this version would be usable.
I could not believe my eyes - It is actually even worse!
100% preview is not working - changin photos (cursor) - back and forth - sometimes 100% preview is shows, sometimes some soft version in lower resolution. This applies to 2 files. Keep changing between them you get randomly soft and sharp version.
I worked as software engineer for 15 year. Never saw such incompetence.

I posted another thread under Batch Rename but another problem when batch renaming files is that the full screen image previews get wiped from the cache and I have to purge and and let Bridge render new ones.

My original posted is pasted below for reference.

//

When I batch rename files it gets the name right (ie Text and sequence number) but it leaves off the filename entirely. If I hit Preview before renaming it shows that it will be done correctly, but when I actually execute the batch rename the files just come out like Text0001 instead of Text0001.jpg or whatever. I have to manually add another line to the batch rename of New Extension for any extension to be put in the file at all. Fortunately I've only been renaming files of the same type.

Further, once the rename is completed all of the full screen preview images are gone from the cache and when you hit space bar it just shows what I suspect is the embedded preview from the raw file (in this case .ARW files). I have to purge the cache for the affected files for a new full screen preview to render.

Bridge 10.0.2.131
macOS 10.14.6

I really really would like to preview AE presets (in Bridge as in previous versions). It is ridiculous that this BUG has never been addressed. It makes Bridge useless for motion graphics.

As I have mentioned in previous posts, previews can be played in Bridge 2018. But not being able to use the current version obviously disrupts workflow and is stupidly inefficient. Is Adobe EVER going to attempt to restore AE preset previews? This issue has not been dealt with for years now. I had not encountered this problem before CC2019, but apparently it existed sporadically in numerous earlier versions of Bridge, too.

Tell the truth: is Bridge slated for extinction? If so, please get to work on a preset previewer for AE and its kin, preferably within the media browser panel. Using old versions of the software or jumping to a browser as an alternative is simply a waste of time.