-
1. Re: LR3 "Develop Module" slowing related to noise removal
JayS In CT Jun 30, 2010 7:19 AM (in response to KulorDS)Kulor,
It's been discussed in a number of the "slow" threads, amongst a number of other things. Simpler way to test is to just turn the detail tab on and off and the difference is noticeable and immediate. As someone else mentioned though, you can't go completely without seeing what effect your NR is going to have while editing. Somewhat of a catch 22. The new NR is great, but I think it may be one of the areas Adobe may have to look at as far as overall performance. Comparitely with LR 2.7 there is a huge difference to the UI impact.
Jay S.
-
2. Re: LR3 "Develop Module" slowing related to noise removal
TK2142 Jun 30, 2010 2:01 PM (in response to KulorDS)Thanks a lot for sharing. I've yet to confirm this myself but it could very well be the case that LR starts to behave like molasses as soon as I start using the "Details" tab.
Often performance in the develop module is acceptable (not immediate as it should be on today's hardware, but acceptable) but after a while the lack of responsiveness becomes ridiculous. Previously, I assumed LR cannot handle a high number of brush strokes and/or edits in general. I'll have to monitor whether the slowing down is related to the use of the "Details" tab.
I hope this forum hasn't turned to a self-support group. I don't see the usual professionals post anymore. Hopefully they are just all on a well-deserved break but will return in due course.
It is frustrating to be left with bugs like the Flickr republishing bug and not even get an acknowledgement that it has been added to the list of things to fix.
-
3. Re: LR3 "Develop Module" slowing related to noise removal
JayS In CT Jun 30, 2010 2:14 PM (in response to TK2142)TK2142 wrote:
Thanks a lot for sharing. I've yet to confirm this myself but it could very well be the case that LR starts to behave like molasses as soon as I start using the "Details" tab.
Often performance in the develop module is acceptable (not immediate as it should be on today's hardware, but acceptable) but after a while the lack of responsiveness becomes ridiculous. Previously, I assumed LR cannot handle a high number of brush strokes and/or edits in general. I'll have to monitor whether the slowing down is related to the use of the "Details" tab.
I hope this forum hasn't turned to a self-support group. I don't see the usual professionals post anymore. Hopefully they are just all on a well-deserved break but will return in due course.
It is frustrating to be left with bugs like the Flickr republishing bug and not even get an acknowledgement that it has been added to the list of things to fix.
TK,
No problem.. would be interested in what you find turning it on and off on your machine. As for the Flickr issue, did you let Adobe know formally? There are Adobe who are here, but since this is user to user, you can't always depend on them getting the word from here. I wouldn't want to be on the end of trying to prioritize some of the issues that have to be looked at. Having spent a fair number of years coding, you try to find that elusive "common" module that may be impacting a number of things.
Jay S.
-
4. Re: LR3 "Develop Module" slowing related to noise removal
PIRose Jun 30, 2010 3:15 PM (in response to TK2142)TK2142 wrote:
I hope this forum hasn't turned to a self-support group. I don't see the usual professionals post anymore. Hopefully they are just all on a well-deserved break but will return in due course.
But let's not forget (despite the fact that Adobe staff has helped here in the past--and hopefully will continue to do so) that this is a user-to-user forum. IOW, it is a self-support group. To cite Adobe's description (of these forums): "...where Adobe users exchange questions, offer ideas and suggestions, and share tips and tricks."
Phil
-
5. Re: LR3 "Develop Module" slowing related to noise removal
TK2142 Jun 30, 2010 5:57 PM (in response to JayS In CT)JayS In CT wrote:
No problem.. would be interested in what you find turning it on and off on your machine.
Sadly, turning it off doesn't help me. I haven't tried to not use it instead of using it and turning it off afterwards yet, but I suspect that won't make a difference either.
I'm experiencing terrible lag with the adjustment brush on images where I have done lots of edits already. I create a stroke and 2 seconds afterwards it is actually drawn.
Playing with your suggestion, I discovered that I can address the lag by reducing the image size. Either exiting "full screen" mode and making the program window rather small or by adding the film strip back to the Develop view, I can reduce the lag to the standard "not ideal since not immediate but acceptably fast" speed.
I've read elsewhere that reducing the displayed image size addressed performance issues.
I haven't tried to use "1:1 previews" whether these may make the perfomance image display size independent.
I hope this issue will be fixed in the future. It is so nice to be able to switch off the top and bottom panel (sometimes even the left side panel) in Develop mode. It would be bad to be forced to have them all in -- or even exist "full screen" mode -- just to address the performance issue.
As for the Flickr issue, did you let Adobe know formally?
I have just submitted an official bug report.
During the BETA forum days that didn't seem to be necessary as Community Professionals would try to reproduce bugs and then forward them on to the programmers. They also confirmed that they did it. That was really nice.

