Lake Crescent
I purchased Adobe Lightroom 3 about 6-8 weeks ago. I have used Adobe Bridge and Adobe Camera Raw for viewing and converting my images for six years, so was obviously not overly impressed with Lightroom before. In fact, I have downloaded trial copies of both previous versions of Lightroom and uninstalled them from my computer after one week. I didn’t just not like them, I actively hated them.
Then I made the mistake of watching some of Scott Kelby and Matt Kloskowskis videos on 100 Ways Lightroom Kicks Bridges A**. They actually made a separate video for each of the 100 reasons (must be nice to have that kind of time on your hands. And why do they hate Bridge so much?). I watched the first thirty and had found only four of them relevant in any way to my work flow. But the four reasons were good ones, so when Lightroom went on sale for about half of its usual price I bought it (does a sale on Lightroom 3 mean Lightroom 4 is imminent?).
I’m kind of regretting the purchase now because Lightroom does four things really well and for the rest of it I still need to have Bridge open to get anything accomplished, and now I have one more program to worry about because now that my images load faster and are sharper on full screen preview I can’t live without it. At times I have Lightroom, Bridge, Photoshop, and Capture NX (There are some Nikon RAW files that just do not convert well in Adobe) all running at the same time. Oy Vay!.
The four reasons I bought Lightroom, in order of importance, are:
1. Speed – My biggest complaint about Bridge, and the reason I finally gave up on it is that it seems to be loading images slower as time goes on. Lightroom is faster. Not FAST. But faster. Breezebrowser still kicks its butt on speed, if that is the only thing you are worried about (which makes you wonder how Adobe, with all of its money and brain power, can’t match other programs, seemingly ANY other programs, on speed). Huge advantage to Lightroom.
2. Full Screen Image Preview Sharpness – The first thing I do after uploading new images is to edit them in full screen mode and in Bridge I can’t delete images based on marginal sharpness because the previews are all unsharp. Of course, I often do that first edit in the field on my laptop and I am not able to judge sharpness on my laptop and have no intention yet of loading Lightroom on the laptop, anyway. But, for the images I upload at home I hope to be able to edit more viciously on the first pass with Lightroom. Marginal advantage to Lightroom.
3. Keywords on upload – The Lightroom upload utility is, disappointingly, slower than Bridge’s, but I console myself that it is adding keywords while it uploads (it is more likely slower because it is having to ‘import’ every file). Bridge does not allow you to add keywords on import, but I usually just select all of the images (Ctrl A) and do it immediately afterward, so a marginal advantage to Lightroom that is lost due to the slowness of uploading. A draw.
4. Contact Sheets – Adobe took the contact sheet function out of Photoshop with CS5. Some editors still want a printed contact sheet with DVD submissions so they have a quick visual reference to what is on the DVD without having to open it. Advantage Lightroom by virtue of an unexplainable loss of a useful function in Photoshop.
Tie-down Horse
I wish I could end there, short and sweet and positive. At the risk of ranting, it is only fair to give a few of the 100 ways that Bridge is, indeed, better than Lightroom, and why I now have to use both programs to accomplish anything.
1. Lightroom is a catalog, Bridge is a browser. I don’t need a catalog. I think. It must be a necessary evil to allow putting the Develop module inside of the program because Apple’s Aperture employs it as well. Bridge (any browser) will happily show me every image on my computer. Lightroom will snootily ignore every image on my computer until it has been properly introduced via an ‘import’. But that’s not the worse of it. Oh no. If I open an image in Photoshop from Lightroom and work on it, it will faithfully save the psd file right there next to the RAW file. Good boy. Bridge will put the psd file any old place it feels like putting it, but almost never next to the RAW file with the same name. Do people in the Lightroom and Bridge divisions at Adobe even talk to each other? BUT, if I then make a jpg file for the blog, Flickr, etc, as well, it will not be in Lightroom, I have to import it back in. ARGH! Second problem. Somewhere around CS4 I stopped having that Maximize Compatability box checked when I saved a psd file in Photoshop. The result of that is that Lightroom refuses to show me about half of my psd files. It knows they are there. If I try to synchronize files it will tell me the name of each and every one of them, along with a snooty message about what I have to do before it will be willing to consider befriending them. To see them in Lightroom I have to find them (in Bridge) and open them in Photoshop and do a Save As with the maximize comparability clicked on – THEN import them into Lightroom. One of the major reasons I have to have Bridge open to find files.
2. Filter Tab (or the lack thereof) – The other reason I have Bridge open to find files is that there is a heavenly, elegant, perfect tab called Filter in Bridge. If I just want to see the psd files, I click on psd. If I want to see five star files with a red tag, I click those two. If I click on a keyword it shows all of the files with that keyword. Lightroom, inexplicably, does not have the Filter tab that its FREE cousin has. It has what amounts to a Find or Search function that is so onerous I will never use it as long as I can just go to Bridge and find the image in half the time. Like I said, these guys at Adobe obviously don’t talk.
3 Develop – One of the things Scott and Matt repeatedly brought up in their videos was how with Lightroom you have it all in ONE program. Not really, but even then, going from the Library module in Lightroom to the Develop module is every bit as cumbersome as double clicking an image in Bridge and having Adobe Camera Raw open. You still have to go back to the Library module to open a different folder. Back and forth, back and forth. I am used to ACR and have yet to like the Develop module. They do the same things, but in the Develop module you have to scroll constantly to go from one tool to the next if you don’t know all of the keyboard shortcuts (none of which make any sense so depend on rote memory and repetition to learn). In ACR the tools are in tabs up top. No scrolling.
4. Folders – I will end my educational dialog (not rant) with folders. In Bridge folder hierarchies are maintained. I have an Africa folder with 18 subfolders and several sub sub folders. I also threw images in the Africa folder itself that were the touristy photos, or photos that were too few in number to warrant a sub folder of their own. I know where they are. Works great – in Bridge. In Bridge when I click on the Africa folder to find my touristy photos I see 19 sub folders and few image files. In Lightroom, oh my my, when I click on the Africa folder I weep. I weep because there are 3,029 unorganized images in random order. Lightroom displays the sub folders in the side bar, but ignores their existence otherwise. Scott Kelby highly recommends using Collections in Lightroom instead of folders. I see why. I don’t want to use Collections. I have a system that has worked for me for six years. Another reason to have Bridge open. Sigh.
American Flag
It must be frustrating to work on Bridge development at Adobe. They give it away free with the purchase of Photoshop. If they made it really excel, built up the speed of image loading, sharpened up the full screen previews, and added keywording to the uploading utility, then people like me wouldn’t buy their expensive product – Lightroom. So, Bridge’s goal seems to be to offer a useable program for the casual user, but to remain mediocre enough that there is an incentive to buy Lightroom. What is harder to understand is why Lightroom hasn’t employed the concepts that really work well in Bridge and ACR, like the Filter tab and putting the Develop tools in tabs at the top so you don’t have to constantly scroll to find them. Maybe they will in Lightroom 4. Maybe I’ll download the beta version whenever it is available and try making some constructive suggestions to make it better.
I am obviously struggling to adapt to Lightroom after using Bridge for six years. I am sure starting out with it early on would be easier. Without something to compare it to some of its obvious flaws might not be so obvious. One could start out building collections instead of clinging to a file system that doesn’t seem to work in a catalog. On the other hand, I remember using Bridge for the first time was a bit rough. But then I was going from editing slides on a light table and storing them in files in a file cabinet to designing a whole new digital system then. This whole digital world is a wild ride.
What would work best for me is if Adobe offered an upgrade from Bridge for which they charged, maybe, $50. It would be faster and have sharper full screen previews. Maybe you could even add keywords on upload. It wouldn’t need a Develop module because we have ACR a double-click away. Just a lightning fast browser with a Filter tab. We could call it Light Bridge or Bridge Room. Or, they could name it Bridge and re-name the current free version Bridge Lite. I think the engineers at Lightroom and Bridge ought to trade places for three months, just long enough to become familiar with the other program and see what works better than what they have been doing.