I use Bridge to import the photos from the cards to the desktop computer, and yes, into a single directory location. Over two days I might use three different cameras, and shoot up to 12,000 RAW images. Okay, perhaps I should outline how I go about using Bridge to give readers/commenters some background info.Īmongst other events, I shoot motocross meetings. I also switched back to the 2018 version since the new "update" is a pain in the butt. I'm still in the process of typing down all the bugs and irritations of the latest version of Photoshop. It's nevertheless annoying, that these things keep popping up. Since bridge kept reducing features with every iteration instead of adding usability, this is not that big a deal. In the meantime I will "solve the problem" by not using bridge after Version 2017 anymore. An image organizer should under no circumstances get in the way of other programs running at the same time. This is clearly a problem on adobe's side and has to be fixed. The CPU Load is nothing compared to the usage of the recent iterations of the program. This screenshot was taken while Bridge is calculating the thumbnails for the recursive display of a whole file structure containing 13.154 images. I tested the 2017 Version of Bridge and the CPU Load does not go over 10% even with folders containing thousands of images. This is more a workaround than a solution:) Its only going to get worse and camera file sizes keep increasing I solved that problem by putting no more then 1000 images in a folder. Even Bridge Version CS6 handles the same folder with a cpu load of around 20%-30% (having purged the cache for all of the 6000 images and letting Bridge CS6 recreate all previews). No other image-organizer that I tested (Thumbs Plus, Xnview, XnviewMP, Faststone, Irfanview, Zoomviewer) uses this amount of ressources. I would appreciate a more balanced solution for this kind of task. 32-bit workflow is still a mess., most of the filters have never been updated since the stone age, etc)Īnyway. I still have the impression, that the whole adobe app range has become more and more sloppy since they discovered the generation instagram as their main customer base, neglecting the needs of power users (e.g. Creating this kind of load seems not be optimized at all.īridge has never been a very ressource friendly program in the first place. ![]() I don't understand why adobe does not use the GPU for tasks like this. 6000 Images and the cpu load immediately went up to 99%-100% on ALL cores. It seems, that Bridge uses the CPU cores for the creation of Thumbnail-Previews. I did some more testing on the cpu load issue with bridge.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |