Adobe Lightroom 3.2: The Saga Continues.
I’ve been running the 3.2 version of Adobe’s Lightroom for many moons now. I can say that it’s not that much of an improvement over 3.0 and it has introduced some new problems as well. I’ll be building on the problems I covered in my review of Adobe Lightroom 3.0 so you might want to read that first. On to the fun.
1. Have you made a slideshow in LR and exported it as a mp4 file? When setting it up to play back on your website have you noticed that the whole file has to load before it starts to play. Even if you have the buffer set to something like 30 seconds (and assuming your slideshow is longer than 30 seconds). Are you annoyed by this? Me too. I found out why this is.
Lightroom is creating mp4 files that have the index at the end of the file, not at the beginning. The index has to load before the file can start playing. Why does LR put the index at the end? I have no idea, but it’s not cool. At least there is a cure. Download and install QTIndexSwapper from and use that to fix the problem. This is an Adobe Air program that will move the index to the front of the file. You must have or install Adobe Air in order to install QTIndexSwapper.
What’s really interesting is that the programmer who wrote QTIndexSwapper works for . . . wait for it . . . Adobe. And it appears he is writing this software on his time, not for Adobe. The Lightroom gang wrote bad software and other Adobe programmers have to fix it for free. Nice business model Adobe.
2. I still get the “file is offline or missing” message for files which are neither offline nor missing. I have to close and restart Lightroom for it to find the file which was there. Really it was. I’ve gone and looked. It’s there.
3. With Lightroom 3.0 I frequently has crashes upon starting the program. That problem has gone away with 3.2 however the program has crashed three times while I was in the middle of editing. Once I lost a few hundred star ratings and had to do all that again. So far I’ve lost no edits and now I save my metadata to the DNG file (ctrl+s on PC) after I finish editing an image. Just in case.
4. Lots of display problems still. It would be nice if Lightroom was capable of showing me the file I’m working on. That makes editing an image much easier. This seems to come in two flavours and both require that I exit LR and restart the program to make them go away.
Sometimes I will zoom in on an image and the image goes to black. I get nothing. I can zoom out and the image will return. Zoom in. Blackness. And no it’s not a photo of a black cat at night. But good question.
The other flavour is served up when I make edits to the image and the edits only appear on one screen and not the other. This statement needs some clarification. Usually when I am in develop module I have my second monitor in either grid or loupe mode and the primary monitor in loupe mode. I mean that when both displays are in loupe mode and I add noise reduction, adjust vibrancy, etc, only one monitor will reflect the changes.
5. Just as in LR 3.0 when moving files from one folder to another in the library module I get the following error for one of the files I’m trying to move when I move multiple files.
There was an error copying files to the destination you selected. The following files could not be copied:
File could not be moved to the selected destination. (1)
Once I hit “OK” (and no it’s still not ok) I can then move the file individually with no problem.
I’ve figured out a work-around (tho I shouldn’t have to find a work-around, the software I paid money for should work correctly) for the problem. The file that can’t be moved is always the “first” file selected. By first I mean this – when looking at the files in the grid mode and selecting a series of files to move the file most to the top and left is the “first”, the file most to the bottom and right is the “last”.
Got it? When I select a series of files by clicking on the first file, then holding down shift and clicking on the last file, I will subsequently get the error message about when moving the files. I’ve discovered however that if I first click on the last file, then hold down shift and click on the first file, the move process will execute without any errors.
Adobe? WTF? Fix it.
6. Lightroom 3.2 is still slow as hell on my system compared to 2.7 and 2.7 is actually a bit slower than 2.6. If you don’t need the features of LR 3.x and are having problems with it, try LR 2.6 if you can find it. I’ve been told by people trying to find LR 2 for purchase that it’s impossible to locate a copy. Good job Adobe. Make your past products impossible to obtain thus encouraging piracy of software which you will subsequently whine about. Nice business model you have there.
7. When exporting images LR sometimes runs out of memory (I have 3 gig or RAM) and can’t export some, but never all, of the files. I have to close LR and restart in order to fix this. Again I’m thinking this has something to do with memory management as I notice the longer I’ve been doing edits with LR the more likely it is for this error to occur.
In LR 3.0 when exporting it would sometimes tell me it couldn’t find the file, requiring a restart of LR. I have not seen that error so far with LR 3.2.
8. There are still way to many “an unknown error has occurred” messages in the develop module. Something is broken, but we don’t know what. Great . . .
9. This seems to be a new one, or at least I never noticed it in 3.0 if it was there. In library module, using the folder tree and adding subdirectories there is an annoying feature/bug. It goes like this:
My images are organized as such:
W:/lightroom images/2010/10/first friday
and so forth
I’m in library module using the folder tree to add a directory in the urban directory. As you would guess I have lightroom images, 2010, and 10 expanded. I use the “create folder inside “urban” . . .” to create a folder inside the directory urban. Upon doing so the folder 10 will collapse. Not only does that folder collapse but so will other random folder inside the 2010 directory which were expanded, but not all of the expanded folders under 2010.
Adobe? WTF? Fix it. This is bloody annoying as hell! Every time I create a folder I have to scroll up to find the folder I am working in and expand it again before I can create another folder.
I still have to wonder how things went so very wrong between Lightroom 2.6 and Lightroom 3.0. You also might be wondering why I use 3.x instead of 2.x. I’m suffering thru the problems with 3.x because it does have some good features.
The noise reduction is pretty amazing. The ability to export slideshows as mp4 files totally kicks butt. Automatic lens correction = awesomeness. I’ve discovered some improvements in the web module as well. There are many other little tweaks here and there that make 3.x an improvement over 2.x and therefore worth putting up with the problems.
Still it would be nice if Adobe would adopt a business model of making software that works. Just a thought.