Adobe Employee

Question

Lightroom 3.3 Performance Feedback

Forum|Forum|15 years ago
December 2, 2010
62 replies
144126 views

Please use this discussion topic for your feedback on Lightroom 3.3 RC and the final Lightroom 3.3 release when it becomes available. The Lightroom team has tried very hard to extract useful feedback from the following discussion topic but due to the length and amount of chatter we need to start a new, more focused thread. Please post specifics about your experience and be sure to include information about your hardware configuration.

Regards,

Tom Hogarty

Lightroom Product Manager

This topic has been closed for replies.

Show previous replies

A

appcoop1

Participant

Tom,

Aside from trying to analyze everyone's individual issues and system configurations, can we agree that many of us are using the Same systems with Lightroom3.x as we were using with 2.x and are now having varyied performance issues?

I trust you are looking at coding changes that have been made since 2.x as well as additional features added to 3.x ? That would seem a likely starting point.

Regards,

Karl

L

Lee_Jay-ZyZk56

Participating Frequently

appcoop1 wrote:
Tom,
Aside from trying to analyze everyone's individual issues and system configurations, can we agree that many of us are using the Same systems with Lightroom3.x as we were using with 2.x and are now having varyied performance issues?
I trust you are looking at coding changes that have been made since 2.x as well as additional features added to 3.x ? That would seem a likely starting point.

The basic demosaicing algorithms have been changed in LR3 from prior versions. There are two basic results of this change - superior image quality and slower conversions of raw data. While other portions of the application are faster than in LR2, image processing (and therefore preview generation, time for the "loading" indicator to go away, and exporting) are slower. The only real way around this is more powerful hardware, specifically CPU and memory speed. One thing the LR team has done to help alleviate this problem somewhat for some people is to expand the maximum size of the Camera Raw cache. If you have the space available, using a large cache can help with some of these issues, especially in cases where all the images you are working on fit inside the cache and the cache has been populated by, for example, rendering previews.

A

Anonymous

Lee Jay wrote:
The basic demosaicing algorithms have been changed in LR3 from prior versions. There are two basic results of this change - superior image quality and slower conversions of raw data. While other portions of the application are faster than in LR2, image processing (and therefore preview generation, time for the "loading" indicator to go away, and exporting) are slower. The only real way around this is more powerful hardware, specifically CPU and memory speed. One thing the LR team has done to help alleviate this problem somewhat for some people is to expand the maximum size of the Camera Raw cache. If you have the space available, using a large cache can help with some of these issues, especially in cases where all the images you are working on fit inside the cache and the cache has been populated by, for example, rendering previews.

Lee:

I hope this hasn't been answered elsewhere already - are you talking about the setting for Camera Raw Cache on the File handling tab of Preferences?

How large do you recommend setting this (I have PLENTY of HD space available.) Should I put this on the root drive (C:) or on a separate partition of the same HD?

I have some externals, but I don't think they are fast enough for cache - they are prob only 5400RPM.

L

Lee_Jay-ZyZk56

Participating Frequently

Area of interest: The "blur" tool (local adjustments, sharpness from -51 to -100).

Specific issue: It's slow - really slow. I'm not so worried that it's application is slow as this is a processor-intensive operation by nature, but I am worried that it slows down the application of all the other adjustments. I find it especially odd that it slows down cropping, which shouldn't be forcing a re-calculation of the pixels, at the very least until closing the crop tool. Opening, changing aspect ratio, flipping or closing the crop tool is very slow. Curiously, draging around the borders once the tool is active and in the desired ratio is not slow.

Noticed on: Windows XP, Windows 7 64 bit, all versions of Lightroom 3 including 3.3 RC.

Notes: It's easiest to see if you apply several applications of the tool, such as several gradients or several brush adjustments. I'm not sure if overlapping adjustments make it worse or not as it's so slow it's difficult for me to test.

Workarounds: None that I can find short of not using the tool. Even shutting off the local adjustment panel doesn't bring things back up to normal speed.

S

Sharpis

Participating Frequently

I have recently upgraded from LR2.x to LR3.3. When opening an image edited in LR3.3 in CS4 (with lightroom editing) using photo/edit in photoshop the resultant image on screen is a very poor worse than the original nikon raw image. So this has dramatically affected my ability to print as the colours I get are incorrect once I do the work in CS4 to correct the poor quality image from LR3.3. This has only just started and the process I employed without problems with LR2.x and the same CS4 software produced prints (printing from CS4) that were good.

I have separately listed this problem on this forum but no-one has provided a solution or suggested solution.

I also lost many of the enhancement files resident in Lightroom when I upgraded from LR2 to LR3. Maybe they are still there maybe no but so far no-one has offered a possible solution for that problem either.

H

H_D_

Participating Frequently

Sorry guys for interrupting this very interesting thread

But I think this topic should be handeled in a different thread (not in the performane section).

I think I did not make myself clear in my original post about Spot Removal tool. My point was that I can't simply switch between LR and Bridge (there is no problem with the Spot Removal tool and jpgs) because the "Beschriftung" (I do not know the english wording for this feature therefore I used the term "color encoding", meaning you can use red or green to mark your image) is lost (I have a solution for this now).

I think nebosphere then got me wrong and thought I was talking about color garmuts.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded