Raptor wrote:
Im at photo workshop in Maine. Im learning to use PS. One of the participants, very accomplished, feels the same way about LR catalog system as I do. My workflow is very simple and I have a good organizational system on my external drive. I want to ditch LR and use Bridge (browser capability) and Adobe Camera Raw. I understand It can do most of what LR can do. I don't batch edit. I also use Luminar 4 and am learning PS. Also I won't have to worry about LR losing photos or not recognizing a drive. Your thoughts? In an earlier post I thought my master photo disk was corrupted. It was an LR issue. I don't want this ajada.
Im at photo workshop in Maine. Im learning to use... (
show quote)
The LR catalog is NOT a browser. A browser is NOT a great substitute for a solid database/catalog. What seems like a good organizational system rarely is, once you understand the way LR (and other catalog based DAMs work). DAM is an acronym for digital asset manager. The idea for Lightroom's catalog comes, no doubt, from the industrial strength DAMs used in corporations for years to organize and manage all paper and media within a corporation, for multiple users.
LR's power is the rub. To be honest, I was accustomed to using browsers and OS file and folder systems when I first looked at LR 2.0. It sat on my system for almost a year simply because I "expected" it to work like every other software product I had ever used - find the file in the browser, using a right click on the filename to open it and select the application to open it with, and edit away. LR was not that software, and my expectations blinded me to its benefits. I suspect that this is what is happening to you and the "very accomplished participant" who is influencing your decision.
I was completely baffled by how LR worked, and where things were saved, etc etc etc. But I refused to be defeated by a software product that many around me seemed to have figured it out.
So one weekend I opened a nice claret, put a do not disturb sign on the door to my office, and planned not to emerge until either the bottle was empty or I had figured it out. The "ahah" moment came about halfway through the bottle.
Now here is the thing. The very efficient file/folder/keyword system I had relied on for 10 years was ok, but it lacked the second level organizational capability that an indexed relational database could provide. LR was that. Being able to organize my images using many-to-one and one-to-many relationships between files/virtual collections finally allowed me to have a single file be part of multiple "collections" instead of making and tracking multiple copies of my images. One picture of a waterfall taken while vacationing could be part of a small collection for that trip, another collection including waterfalls, another collection including family vacations, another collection that aggregates images for a gallery submission, etc. This organization is absolutely not possible with a simple file/folder/keyword scheme. The indexed database is also blindly fast. Because what you are seeing and editing are previews stored in a catalog, rather than editing an entire, often huge, raster file, means that editing is also efficient and fast.
The best part is that I could continue storing my files in the same manner as I had done for 10 yrs. All I did when I started using LR was tell it to "add" the existing files to the database and voila! there they were.
Taking the time to wrap your head around LR's data management model is worth the investment - I can only say this because I was entirely in your shoes until I did, and after "getting it" I can't even think about how I would manage my 200,000+ images.
BTW, you CAN batch edit in ACR - it's just not as slick and fast as doing it in LR - which has a user interface that is decluttered and optimized for fast and efficient editing of multiple files. And you can use LR and Bridge together if you'd like, as long as you are religious about updating the LR catalog with any changes that you make outside of LR. But for my workflow, there is nothing that Bridge offers me that I can't do in LR. Which is why I rarely use it anymore.
After import my basic workflow is simple and file clutter minimal. I open the raw file, edit to optimize it, then use "edit in" to open the file as a 16 bit psd raster file in ProPhoto colorspace. I use this as my master working file to finish the image to my liking. Upon saving, the "edit in" option is set up to place the edited (and finished) psd file in the catalog, alongside the original raw file. From that point forward, I have defined a number of export presets for different destinations - several low res ones for social media and email, a couple of high-res ones for printing, higher quality high res ones for clients (for viewing and printing), etc. - and these are grouped by destination and saved to their corresponding folders unde the master folder with the source raw files. Most of the time, once the images have reached their destination, I delete them. There is no reason in my workflow to keep my jpegs - since if have to recreate them all I need to do is export them again using the appropriate export preset. This is very basically what I do.