After a few more hours of use - Lr3.2RC is definitely working better than Lr3.0 did for me, examples:
- Now that Lightroom is using the ACR cache properly, develop rendering times are down (since its not re-rendering unnecessarily) - dunno if this is an Lr3.2RC thing or if I would have gotten the same improvement by moving my ACR cache when I was running 3.0 - but in any case its not a problem anymore (although there is still a bug in there! - it just isn't biting me at the moment).
- Develop hasn't gotten part way through rendering, then blinked and decided to start over again - like it used to sometimes.
- Develop is showing a reasonable preview whilst rendering a "better" one, instead of just being all blurry.
- Develop hasn't refused to display rendered changes - sometimes it used to not update the rendered image on the display so I'd end up cranking the sharpening up & up until I realized it wasn't showing me the sharpening increases.
- Paint brush hasn't shown the "several second" delays that it used to sometimes (not always).
- Before / After develop view switching is much faster.
- The program hasn't slowed to a crawl, generally accompanied by excessive RAM consumption, yet.
- Lr3.2RC has only crashed once so far.
Summary: Its too soon to tell whether any of the problems I think are better will "re-emerge", but definitely some things are better than they were.
PS - I know software engineers sometimes either don't know or can't remember what all they've fixed as they've worked on things for X months. You can be sure that the list of "fixed bugs", wherever that was posted, is far from complete. And, you can be sure they've induced a few new ones while fixing the others...
==================
2010-08-11 Update #1:
-----------------------------
Part1 - Lr3.2RC still using ACR cache when it should, but has slowed down in develop mode switching between photos - takes several seconds for cached photo to be loaded - accompanied by a freezy-pause thing and/or a spinning blue ring, and sometimes a stutter... before it finishes its business... Restarting Lr did not help, nor did restarting my machine - which are the only things I tried. I did backup/optimize my catalog between the time it was working good, and the now not-so-good behavior - dunno if there's a connection...
Part 2 - After further testing, I've discovered that switching photos in develop mode is much faster at 1:1 than at fit size. I would have thought there would be some preview loadable as quickly, or more quickly than at 1:1, but thats not how its working for me at the moment. Its like its willing to load the 1:1 preview from the cache for developing, but insists on recomputing the image anew for fit view each time.
Part 3 - I could have sworn it was loading fit-size photos quickly in develop mode there for a while, but now its back to slow ~ 15 seconds (when already cached), at 1:1 its more like 3-4 seconds. Yep, its faster again. i.e. fit-size load times are usually slow (~15) but sometimes fast (for the same photos) ~5-6 seconds. So, there is an intermittent bug here - I will report.
Summary: As long as ACR cache is being employed properly (and there is a bug that was keeping it from being), 1:1 switching in develop mode is fast (3-4 seconds). Fit-size switching has a bug whose symptoms are significant lag in switching speed (~15 seconds).
Fit-size viewing in library has been quite perky once previews are built - less than one second. And 1:1 viewing in library is fairly perky (5-6 seconds once 1:1 preview is available). All stats are for non-cropped 12MP images from D300. - My system specs were given in a previous nearby post.
-------------------------
2010-08-11 Update #2:
-----------------------------
Library switching at 1:1 is now going much faster than it was - less than one second. Previously it was 5-6 seconds. (I'm talking about re-visiting after the preview has been created). It just occurred to me that sub-second timing is probably because photo is in RAM and is not being loaded from disk at all. Still begs the question of why is the behavior so inconsistent, and why is it so much slower to load a 1:1 view in library than develop. I assume in the later case Lightroom has to compute all the library stuff that it doesn't have to compute for develop, but 2-3 more seconds to initialize library panel views for a single photo seems excessive.
Summary: Lightroom has the potential to display 1:1 library previews very quickly, but there is still a bug or two that slow it down. - will report now.
-------------------------
================
Rob
200
Replies
AdChoices