Adobe Bridge Cs4

0 views

Skip to first unread message

Bran Bast

unread,

Aug 3, 2024, 4:42:08 PM8/3/24

to rouvatemy

I use Adobe Bridge in my daily workflow and after the Mac update I can't get dropbox to show up at all. I tried making an alias, reinstalling, showing hidden folders. Nothing works. Please help. I'm running Ventura 13.2.1 with the latest Adobe bridge software.

You mentioned that you updated your Dropbox app, do you use the new macOS update on your device? If so, have you taken a look at this Help Center article, in order to allow access to your Dropbox files?

I would like for you to locate your Dropbox icon. It would be on the menu bar, next to your WiFi and hover your mouse there. That should give you the version of the Dropbox app that you use on your end.

Did this post help you? If so, give it a Like below to let us know.
Need help with something else? Ask me a question!
Find Tips & Tricks Discover more ways to use Dropbox here!
Interested in Community Groups? Click here to join!

I'm really in a bind. I can no longer view any Dropbox folders or files with Adobe Bridge. I CAN view an external drive (which is in the same location as Dropbox in Finder) but cannot view Dropbox at all.

Must be some new setting I don't know about...please tell me that is what it is I've loved Dropbox from very early in it's introduction but use it only to sync stuff between Macs...not interested in any of the fancy stuff, but now just view is "fancy"

As a first thing, can you clarify the version of the Dropbox app that's installed on your device? You should be able to see this, by hovering your mouse over the little Dropbox icon, on the menu bar.

To be clear. I CAN view all files via Finder but Adobe Bridge does not show any Dropbox location. I Finder, I see Dropbox now under locations but Finder also shows Dropbox as one of my user folders. I can find the Dropbox "user" folder with another file viewer but it does not show it as a location.

Have you tried dragging the folder or file you would like to open onto the Bridge icon in your dock? It should open and show you the location along the top, which on my computer is: /Users/[username]/Library/CloudStorage/Dropbox/...

I'm seeing extraordinarily high CPU usage on Adobe Bridge, especially when "idling" - no active process are being run after several hours on the same folder. Attached is a screenshot with relevant information. Any insight would be appreciated.

OK, so I just found a WEIRD solution for Adobe Bridge 2023... it works and not sure why. If I start up on Bridge in the Essentals view, the CPU hits 50% and temps go to 85C (Win 11 Pro, 12th gen proc). SO, at the bottom of the Bridge window, grab the slider that changes the view percentage, and drag it all the way left, so your thumbnails are super tiny. Your CPU should drop to 0.2% or so. Seriously. Then for me, I dragged the slider back up to about 40% which works for me size-wise, and it's ho

"The memory leak is a new thing that came up this week. Nothing special that I haven't done for years on prevoius versions of Bridge. In both instances, no active processses were being run, the system was "idle" - Bridge was open to about 4-5 content tabs showing thumbnails JPGs, PNGs, and PSD files. Again, nothing crazy that I haven't done for the past 15 years of using Bridge."

Do you have raw files? is ACR set to develop all jpegs? there was an update this week, so the issue might not be constrained to Bridge, just trying to find relevant info. (asking this as another user reported issues when developing 1000s of NEF files from a Z9 (45MPX camera)

Absolutely no RAW files being used - just run of the mill graphic design files and proceses. Lots of PSDs/PSBs/JPGs/AI. Only caveat maybe that I do utlize Cloud Storage, in this case Google Drive being set to "Stream" so lots of files being downloaded from the cloud on demand. Thanks!

The issue persists with and without Google Drive being active. I've noticed that this happens when I leave Bridge 2023 running and leave my comptuer for an extended period of time. Also, this conincides with massive amounts of memory being used. Attached are 2 screens from this week. If I leave Bridge running long enough my disk space will wittle down to 5gb and I'll get a system warning.

These are the answers that drive me nuts, I'm sorry. We haven't changed anything in our environments, and Bridge started doing this last version, but changing Thumbnails to Embedded would work. Now it DOESN'T in 2023. Adobe programmers borking the code again, just like when they destroyed Print Preview in Photoshop and it took TWO YEARS to get it back. So please don't start asking what we have going on with our machines, Bridge in Windows is a nightmare, rattling my CPU just sitting idle. And I see other stuff that shows the programmers are messing up (and since I AM one I can call them out on this). I opened Preferences, went to Media Cache, and under Location the button always said "Show in Folder". What's it say now? "Show in Finder". The Mac app, and I'm running Windows. What on earth are these guys doing? My fans are pegged at 100% and in Windows laptops are loud, for a reason. SO tired of this.

In case it helps. This seems to happen when the folder includes JPGs or MP4s from my Pixel Cell Phone. If the folder only has images or video from my CANON camera, there is no problem.

Also, if I use the Light Table workspace, the Bridge CPU usaage goes to 0%.

I also used the recomended tumbnail resize workaround, and that helped a lot.

As someone who's on these boards every day, looking at just about every message, it's very hard to understand why this bizarre issue hits some folks while I have never had even a smidgen of the problem. Ever.

But that is probably because I favor small thumbnails and have a large Preview Panel to really SEE the image. This screenshot shows my primary working space. FWIW, I never understood Adobe's desire to put the Preview panel as a small region off to the side. If I want to look at an image preview, I want to see it.

What would be very handy for everyone here and Adobe is to let others know if you have had this issue and how large your thumbnails are. The hard part is that there is no accurate measurement for the thumbnail size in Bridge. I suppose using "small," "medium," or "large" might be all that can be done.

It was weird, I was just playing around and stumbled onto it. Nonetheless, somebody at Adobe listened because the beta version that's out has fixed the problem. I'm not loading beta onto my PC at the moment because I can do the thumbnail workaround but at least we know the next version will have it fixed for good. Squeaky wheel gets the oil, lol!

This trick did not work for me. Since updating to current version of Bridge 13.0.3 (unsure of version I updated from) about 10 days ago, it is making my MacBook Pro nearly unusable without being plugged in because of massive CPU usage (2019 MBP with 64 GB RAM, on Ventura 13.4.1). I tried purging my cache and resetting preferences to defaults per the recommendations on this troubleshooting page ( -errors-freezes-bridge.html) with zero improvement--if anything, problem got worse. And resizing the previews in a folder with about 500 images (approx 1800 images, 1300 hidden) does nothing. It just reopened and demanded 200% of CPU time, now 1,019% of CPU time while in the background with me having done nothing but open it and hide it. My battery health is good and I can run this machine for hours unplugged while using web browser, video, citrix VDI sessions for work.

Our authors are creating assets and adding metadata (Keywords) in Adobe bridge and after they are uploading assets in AEM manually. We are not using connector between Bridge and AEM. I can see there are multiple Keywords added in Bridge but those are not reflecting in AEM upon asset upload.

It says that Keywords will be mapped into AEM. But I do not see those metadata automatically extracted by AEM. When I see those image details property in Windows explorer then it does not show "Keywords" metadata either.

If you are not seeing Keywords in windows explorer that means metadata in not write back in asset. Hence AEM not able to extract. Make sure you are importing asset properly from bridge [1] so that asset has all metadata.

While downloading an asset from bridge, metadata property 'Copyright' for asset is sent as String[] array type. (Once I uploaded this asset in DAM, I checked metadata properties and found property named as 'dc:rights' is set as String[] type in AEM for such assets, coming from photoshop.)