Lightroom 3.2 Release Candidate Available on Adobe Labs

Is there any new ifnormation on Lightroom 3.2 official? I'm still dying for a cure here. I've all but given up on Adobe. Clients have all but given up on me.

I have to say that compared to the original v0 download version that this 3.2rc is an exponential

improvement.

There are still some issues with rendering, and rerendering .. and rerendering.. but it's been mentioned in previous posts, and I'm sure it'll get fixed prior to the official upgrade.

Thanks Adobe.  (everything I had been P _ _ _ ed off about has been given a sizable speed increase)

Good Work!

Well, chaps, I am going to have to hang my head in shame and eat humble pie here. I have been horribly guilty of making subjective judgements not based on proper scientific data.

Last night I purged the ACR Cache and did some testing in the Develop Module loading files, timing everything just using the second hand on my wrist watch. The ACR cache is working properly, and it does make a significant difference. The results are -

Load uncached, unedited image - 15 secs

Load same image, with cache - 10 secs

This is consistent, and is 30% faster. So why didn't I notice this? Well, the reason is simple. I always work on one photograph at a time, and never do any sort of batch processing - every image has different edits. The only reason I ever load a file into the develop module is to edit it, so I never load it again cached and without edits. Editing the file makes the load slower, so that even with the cache it takes 12-13 secs, which is so similar that I perceived it as the same.

The next horrible error was to think that LR 2.7 was faster. I thought it was, but running the same test the load results were the same - 15s with no cache and 10s with the cache. So why did it seem faster? Once again, the reason is subjective. In Win 7, LR2 just displays a "Loading" notice. LR3 displays the "spinning circle" as well. Because the spinning circle sort of hesitates and freezes at intervals during the load, it made it seem to me that LR3 was slower.

So to sum up - the ACR cache makes a 30% reduction in load time with an unedited image. But once the image is edited, the difference is much less, about 10%. When this represents either 15s or 13.5s, you really hardly notice. I think that for me, at any rate, once a process of any sort on the PC goes above 10 sec it just seems slow. Slight differences of 2 or 3 secs above this are of little consequence.

John

After running about 10,000 new photos through 3.2, addiding to a bloated 217,000 image catalog, I see definate improvements. Thanks Adobe for killing some bugs. I am sure the next version will be better still.

Better

* Brush performance improved

* Program opens and default catalog loads more quickly

* Simultaneous preview rendering and import from card reader no longer freezing program

* Herky-jerky "move folders within LR" issues gone

Don't like

* No default keyword option on import

I am puzzled about what the ACR cache really does, quite frankly. I get pretty much the same delay loading an image into the Develop module whether it is in the cache or not. The only thing which actually seems to affect the load time is how many edits have been made to the image, specifically perspective correction and local brush edits. They really slow things down. But I can purge the ACR Cache and afterwards I see no real difference in performance, either faster or slower. Mind you, I have probably have the worst-case scenario (or close to it) with 39MP files from a Hasselblad back, which expand to a 230MB 16-bit rendered image.

John

In general I'm so pleased with 3.2 RC (64 Bit on Windows 7 Ultimate) that I use it for my production work. One issue very annoying for me hasn't been resolved yet: Like many I'm using keywords to organize my photos. Normally I work on a collection of photos with a given keyword like "event xyz" (so I filter my photos by this keyword). When I edit an image in Photoshop CS5 (64 Bit), save it and return to Lightroom the edited photo isn't shown (in Lightroom 2.x it was).

Two "workarounds": Exit Lightroom, Reopen it, Photo is there! Alternatively, deactivate Filter, locate edited image, remove keyword from image, add keyword to image ...

Please, Adobe, get this fixed for LR 3.2 Final!

Tom Hogarty wrote: This release includes camera support, bug fixes and new features.  Details here: http://blogs.adobe.com/lightroomjournal/2010/08/lightroom-3-2-and-came ra-raw-6-2-available-on-adobe-labs.html Regards, Tom Hogarty Lightroom, Camera Raw and DNG Product Manager

All,

I noted no "export" related fixes listed in Tom's note references above.  I am still experiencing a signficant difference in export times between LR 2.7 and LR 3.x.  Timings are consistently double for the exact same images, exported exactly the same way, to exactly the same location.  I have attempted to match all settings as much as possible (given 2003 vs. 2010 process model).  I have not tried an export of the same images under 2003 un LR 3.x yet.  Is anyone else seeing major differences in export and have you reported it?  I just did, but just checking with the group.

Jay S.

Just a postscript to the above.  Reverting to 2003 Process model and unchecking Lens correction brought export times "closer" to 2.7.  The bigger offender (at least here) was the Lens Correction module.  Process 2010 added only about 2 seconds to export.  The bulk came from the lens correction added to the images to be exported.  Would be curious if others see similar results. Jay S.

Error when adding Date/Time to filename on import: This is a frequently reported bug in LR3 but is not mentioned as a fix in 3.2. When will this be addressed?? I sent a report several weeks ago and I know others have as well. When renaming on import, the time in the filename is shifted back by 4 hours. Problem occurs on both the desktop and laptop installations. I now import without renaming and need to remember to rename all files AFTER import to get an accurate time in the filename. My son, also on 2 computers, on a separate license in a distant city has the same bug. Others have complained as well. This is a big pain in the neck and seems like it should be a pretty simple fix. Please help us out!

I have tried several times to install the release candidate.  However, I do not think it is actually being installed. I see no publishing option for facebook and the version still says 3.0.

Any thoughts on how I can know for certain and if it is not installing, what I may be able to do?

Running on Mac, in case it matters.

Thanks

One thing thats faster in 3.2RC than 3.0 for me is the before/after switching in develop mode. In 3.0 it was sometimes fairly fast, and sometimes very slow. So far in 3.2RC it has always been fast. And, since I use it way too much it's great that its working better - .

Rob