Adobe has Firefly and all sorts of crazy stuff going on recently – but Search and Filtering in Bridge still give me 2003 Pentium 2 vibes. I find Search / Filter performance and filtered data presentation equally lacking.
Great performance does not need a database
Some might reflexively state that a file browser for tasks like searching cannot compete with database-driven programs – but I call this nonsense for moderate data volumes (some thousands or ten thousand files). You don't believe me? Just download apps like Everything or Listary* and have a play. Both apps have small, yet blazing fast indexes and support Algolia style Search As You Type – any instance of a file you have on your system is retrieved in milliseconds.
In the mentioned tools, you may interact with search results right away. And search result lists remain live. As soon as new file versions arrive, they are immediately added to the results list. No, there are no big enterprises involved to make this kind of interactive performance happen. Both mentioned apps were written by just one developer.
Insanely ineffective: The Bridge Index
Example: We have an output folder that holds all images we use in a web-project – about 4000 PNGs. This folder is known to Bridge and indexed. For performance reasons, we use the fastest display option, embedded thumbnails. Bridge does not have to create thumbnails – it only needs to display what's there already. The machine uses fast NVMe drives and has 64 GB RAM, it runs on Win 10.
Bridge knows the folder (normal local folder) and may work with existing file-miniatures. Even with this minimal setup, the program fails to deliver a snappy interactive performance. Thumbnail render speed, scroll performance – there are many forum threads on this topic alone. I also shared some hints, how to improve the user-experience when things are a bit slow, unfortunately this input got disregarded as well.
Pictures speak louder than words. Here's a little clip which demonstrates why its static Search / Filter implementation severely limits Bridge's usefulness as a file manager. Considering the latest forum feedback (Bridge Search not finding anything at all...) your team might take the chance and solve the problem properly.
👀@nikunj.m Mods please leave this Employee-Ping put (that forum handle is public anyway).
Both Windows and Mac have file-system APIs to track files. I've been working with large folders recently, still using Bridge 2022 because thew two newer releases are useless, and both performance and stability are terrible. I've had to write numerous scripts to get basic functionality that I need. All in all, pretty sad. These apps could be SO much better, it amazes me what they ship.
Amen. What really amazes me is that the Bridge Team still asks for details when people report performance problems, as if one would be looking at rare edge cases. Indeed, you can completely screw a fresh Bridge 14 installation – at least on Windows – with just a few large folders. All the Bridge Team needed was a single person who actually uses the program…
We can't run Bridge 14 without having Everything running side by side. That way, we at least know what's really going on.
We depend on the latest Bridge though, as Br 12 is mapped to Photoshop 2022 with no way exposed to change this… There might be some trick to call batch-processing in PS 2024 from Bridge 12, but I haven't figured how to script that.
I use a script to batch from Bridge 2022 to Photoshop 2024.
Batch is part of the Utility Script Pack. Not everything works under Bridge 14 yet, but its fully functional with Bridge 2022.
Thanks, @Lumigraphics for making your scripts available! I just wished you would unbundle them for sharing – it's super unlikely that fellow users need all of them too 🙂.
I had to install all the scripts and go through a two-level submenu, just to access batch (a command that I have many times a day). Good thing in Br 14: One can set a keyboard-shortcut! A while ago, I had looked into the script, but could not get the Target Photoshop and Register Context Menu entry thing (likely named slightly differently) to work.
My scripts are open source and Apache-licensed, feel free to modify them as needed. The main reason I bundle them is shared settings including saved preferences.