Lightroom 3.3 – The Suckage Gets Worse
I’ve been driving Adobe Lightroom 3.3 for a while now. You may have read my past reviews of LR 3.0 and 3.2. Or maybe you haven’t . . . and should that be the case you are slacking. I’m gonna heavily reference my Lightroom 3.2 review here so you might wanna reference that before reading this.
In fact, first I’ll address each of the issues I brought up in my LR 3.2 review in the order I brought them up there.
By the numbers.
1. Lightroom 3.2 places the index file of the MP4 files exported from the slideshow module at the end of the file not the beginning. I actually have not tested the MP4 files from LR 3.3 to see if they finally changed this or not. If they haven’t – the solution is still the same. QTIndexSwapper from http://renaun.com/blog/code/qtindexswapper/ will fix the files for you. Send Adobe a bill for your wasted time fixing their mistake.
2. Lightroom has not been unable to find files lately. That’s another way of saying Lightroom has been finding all of my files which is nice since the files are there. Maybe this has been fixed.
3. I was going to be able to write that LR hadn’t crashed in a long time. Then yesterday Lightroom crashed while I was editing. Thanks to saving meta data to DNG files I didn’t lose the edit I was on. When I restarted Lightroom it informed me there was a mismatch between the meta data in the DNG file and the LR catalogue. I synced to the data in the DNG file and all was good.
4. I still get the zoom in on an image and get a black screen problem – but at less often. This could be called an improvement of sorts.
5. The file moving error seems to be solved in Lightroom 3.3.
6. Lightroom 3.2 was slow as hell. LR 3.3 is even slower. Simply switching from develop to library module gives me ~20 seconds to go refill my coffee cup.
7. I’m gonna come back to this one later. That’s should be a clue to you that I have something very nasty to say about Adobe.
8. Still many many occurrences of “an unknown error has occurred” when in the develop module. It would be nice to know what kind of error. I have to select another file then go back to the file on which the mysterious “unknown error” occurred and all is good.
9. The automatic collapsing of the folder tree when I create a new folder is still happening and still just as annoying. I am still amazing that something this simple is beyond the grasp of the Adobe programming crew.
I’m not alone in this.
I found out that at least one other person is having similar problems. Follow this link: http://www.gaijinriders.com/showthread.php?6901-Apple-Aperture-only-79-Woe-is-PC
Here is a quote from the original post:
Lightroom returns an “out of memory” error on almost any photo export when extensive work has been done on the photo.
The photo display in Lightroom turns black when making adjustments with the image zoomed in. Zoom out and the image comes back, zoom back in and the image turns black again (no, it’s not a photo of the inside of a darkroom).
Lightroom returns a “file is offline or missing” error message when trying to edit a file that is clearly there. I can open the file in any other application, but not Lightroom
Lightroom gets slower with each modification done to a picture. All 8 of my CPU threads are working at single digit utilization levels, there’s plenty of free memory, but it just gets slower and slower until it crashes, or the display turns black.
These errors can usually be corrected by shutting down and re-starting Lightroom, but often multiple re-starts are required to get things going correctly.
I also hear about a case of similar problems from someone else running an i7 processor. I posted on the LinkedIn Lightroom forum to see if others using an i7 had any problems (without specifying the problems as I wanted a blind response) and a number of people reported using an i7 with no issues. I don’t dare say these problems can’t be related to hardware (specifically my processor), but it does seem less likely.
Major unforgivable screw-up.
Now – let’s talk about issue #7 from the Lightroom 3.2 review. When exporting images Lightroom often runs out of memory. I thought this had mostly been fixed as I was hardly ever seeing the problem any more. And then I hit the roof.
One day I exported 9 files. When I went to the folder there were only 6 files. What the fuck? I began some testing. Exporting a slew of files and the final discovery comes to this. Lightroom 3.3 still fails to export all the files I select for exporting – but I don’t get an error message any more telling me they were not exported.
On a lameness scale of 1 to 10 this is an 11.5. Now every time I export files I have to go to the folder after the export and make sure the number of files written is the number of files I exported. This pisses me off beyond words. How many exports have I made where the client receiving the files didn’t get all the images? I have no way of knowing. Thank you Adobe for charging me money for a product that further wastes my time.
Lightroom is such a good product in so many ways. Really it is. It’s taken my digital photography to a whole new level. Yet all the awesomeness can be so easily undone by this sort of major failure. Here is a hint for programmers around the world. When your software has an error or fails to do what it’s suppose to do – have it display an error message. This should not be optional. Nor should I need to tell you to do this.
On a positive note (in so much as this is positive) there are no new issues that I’ve found with Lightroom 3.3 other than the lack of error message on file export that didn’t exist in 3.2. This is good because the existing issues are enough to keep me busy. With all the restarting of Lightroom because it’s running slow and having to count my exported files I think that’s work enough for me.
Adobe, who do I send the bill for my time to?