Luminous Landscape Forum
Raw & Post Processing, Printing => Adobe Lightroom Q&A => Topic started by: NikosR on August 06, 2008, 06:15:15 pm
-
Anybody else experiences interminent hungs working with LR2.0 (Win)? I experience strange behaviour very often. Usually that shows as LR stopping responding completely while no I/O is being done and one of my 4 processors being 100% utilised. Additionally in task manager 2 LR applications come up showing....
One common issue I experience is just entering the Develop module from Library and often I can repeat this behaviour with specific files. 'Loading...' message comes up (strangely even if I have pre-rendered 1:1 previews) and then nothing.
All in all, I'm testing the trial version at this moment and I'm 100% sure I will not be buying until a subsequent release fixes these stability problems. It is a pity really because I love the new colour profiles and colour output and I was seriously considering making LR my main raw converter. As it is I will have to wait.
PS. It is the second such experience I have had this year. First was the very painfull experience of working with the initial releases of DxO V5.... now this. What has happened to raw converter developer companies out there? Is competition making them too sloppy and hasty to bring out release versions before they are ready?
-
Yeah. The odd thing is that if I kill firefox it responds.
-
Nah! No such luck. No other app is running, clean system etc...
Funnilly, for the cases where this issue is repeatable, it happens with the same files over and over again. Removing and re-importing the files does not solve the problem. No problems working with those same files in other apps so there should be nothing wrong with the files themselves. I will try to delete the files and restore them from backup to see if behaviour changes. In any case this makes LR2 not reliable enough for me.
-
Anybody else experiences interminent hungs working with LR2.0 (Win)? I experience strange behaviour very often. Usually that shows as LR stopping responding completely while no I/O is being done and one of my 4 processors being 100% utilised.
I have been re-organizing keywords on a new LR2 catalog with 35K images. I am using the Library module only so far. I have frequent lags as I try to assign new keywords to a dozen to a few hundred images, or if I try to move a keyword to some other location in the hierarchy. LR simply stops responding and stops painting the screen; occasionally the window goes completely white. I haven't checked the Task Manager yet to see if it is chewing up one of the two cores.
Guy
-
I have been re-organizing keywords on a new LR2 catalog with 35K images. I am using the Library module only so far. I have frequent lags as I try to assign new keywords to a dozen to a few hundred images, or if I try to move a keyword to some other location in the hierarchy. LR simply stops responding and stops painting the screen; occasionally the window goes completely white. I haven't checked the Task Manager yet to see if it is chewing up one of the two cores.
Guy
[a href=\"index.php?act=findpost&pid=213561\"][{POST_SNAPBACK}][/a]
Those lags I have them too. I can live with them. What I can't live with is the program completely stopping, obviously looping or something and the only way to get out of that is kill the app from the task manager. Additionally not being able too edit some of my images is unacceptable.
-
i am having the opposite experience.
I DL'd v 1.4 and had all manner of problems such as you describe, and repeatable too. Since adobe provide no 'support' for trial versions, i was about to give up and abandon it.
then V2.0 went live. i re DL'd and voila, inexplicably, all of those issues seem gone (7 days and counting) with the exception of LR abandoning a synch operation midway w/o a message.
if it remains this stable for another 2 weeks, it's a winner.
my library is ~ 15,000 images. and this is on an xp sp2 box.
Those lags I have them too. I can live with them. What I can't live with is the program completely stopping, obviously looping or something and the only way to get out of that is kill the app from the task manager. Additionally not being able too edit some of my images is unacceptable.
[a href=\"index.php?act=findpost&pid=213595\"][{POST_SNAPBACK}][/a]
-
Now, I tested LR on the Mac. With the same images but a newly created catalog there appears to be no problem. Next things to test:
1. Newly created catalog on Win with the offending images I have identified
2. Export original catalog from Win and import on Mac
3. LR on a different Win computer.
Hope these will help me pinpoint the problem although with no support provided by Adobe for trial I'm not sure what pinpointing will accomplish.
-
Anybody else experiences interminent hungs working with LR2.0 (Win)? I experience strange behaviour very often. Usually that shows as LR stopping responding completely while no I/O is being done and one of my 4 processors being 100% utilised. Additionally in task manager 2 LR applications come up showing....
One common issue I experience is just entering the Develop module from Library and often I can repeat this behaviour with specific files. 'Loading...' message comes up (strangely even if I have pre-rendered 1:1 previews) and then nothing.
All in all, I'm testing the trial version at this moment and I'm 100% sure I will not be buying until a subsequent release fixes these stability problems. It is a pity really because I love the new colour profiles and colour output and I was seriously considering making LR my main raw converter. As it is I will have to wait.
PS. It is the second such experience I have had this year. First was the very painfull experience of working with the initial releases of DxO V5.... now this. What has happened to raw converter developer companies out there? Is competition making them too sloppy and hasty to bring out release versions before they are ready?
[a href=\"index.php?act=findpost&pid=213517\"][{POST_SNAPBACK}][/a]
I've been experiencing such incredibly long hung times, that I've stopped using Lightroom 2.0. I checked on the Adobe Lightroom user forum, and this seems to be a fairly common problem on Windows. I've talked to Adobe about it and they don't have an answer yet. I'll give them a few days, but if nothing comes of it, I'll ask for a refund. I don't have time to be fooling around with my computer, trying to get a program to work. Very disappointing.
-
I have been re-organizing keywords on a new LR2 catalog with 35K images. I am using the Library module only so far. I have frequent lags as I try to assign new keywords to a dozen to a few hundred images, or if I try to move a keyword to some other location in the hierarchy. LR simply stops responding and stops painting the screen; occasionally the window goes completely white. I haven't checked the Task Manager yet to see if it is chewing up one of the two cores.
Guy
[a href=\"index.php?act=findpost&pid=213561\"][{POST_SNAPBACK}][/a]
I was having the same issue and found that uninstalling LR 1.4.1 has resolved much if not all of the delays.
Win XP Pro SP2 P4 3GHz 2 GB RAM
I was watching the process monitor with LR2 and LR14 installed and the RAM would constantly reach 500MB plus and not drop back down. There was constant disk activity cpu usage that hovered around 25%. With LR14 uninstalled the RAM usage will spike up into the 400MB range but always drop back to the 160-200 MB range. Seemingly unnecessary disk activity has subsided.
Hopefully someone else can confirm this. Its changed my impression of LR2, I was ready to go back to LR141.
-
Thanks. I do have LR1.4 installed. I will take your suggestion and, temporarily, remove it and see what happens.
In the meantime I have taken Adobe suggestion and removed the prefs file, losing of course my prefs so I had to set them up again, to no avail. Ditto when deleting all previews together with the related disk files.
-
My PC has only 512 megs of RAM and LR runs smooth for me. Not lightning quick, but no hang ups.
Anybody else experiences interminent hungs working with LR2.0 (Win)? I experience strange behaviour very often. Usually that shows as LR stopping responding completely while no I/O is being done and one of my 4 processors being 100% utilised. Additionally in task manager 2 LR applications come up showing....
One common issue I experience is just entering the Develop module from Library and often I can repeat this behaviour with specific files. 'Loading...' message comes up (strangely even if I have pre-rendered 1:1 previews) and then nothing.
All in all, I'm testing the trial version at this moment and I'm 100% sure I will not be buying until a subsequent release fixes these stability problems. It is a pity really because I love the new colour profiles and colour output and I was seriously considering making LR my main raw converter. As it is I will have to wait.
PS. It is the second such experience I have had this year. First was the very painfull experience of working with the initial releases of DxO V5.... now this. What has happened to raw converter developer companies out there? Is competition making them too sloppy and hasty to bring out release versions before they are ready?
[a href=\"index.php?act=findpost&pid=213517\"][{POST_SNAPBACK}][/a]
-
LR 2 has run well for me from a performance standpoint but has occasionally hung on my PC with XP Pro 32 bit SP3 - dual core with 4 GB RAM. In every case Windows has reported that LR 2 must close and reports the problems to MS.
-
I started with LR 1.1 and LR2 since beta and 1.0. After starting the LR2 tutorial, I decided to "bite the bullet" and organize a master file with heirarchial keywording. I built a "master.lrcat without problems but the database has "lost" my images when I select multiple "throw aways" and deleat them from the disc. When I reopen edited .lrcat, all of the previews have a "?". This behavior never happened with LR 1.1 > 1.4.1. Am I doing something wrong or is this a bug? It is getting irritating..should have left well enough alone. I was always told that "perfection is the enemy of good" maybe this is an example.
Steve
-
Anybody else experiences interminent hungs working with LR2.0 (Win)?
I'm on a Mac, so my experiences may not be relevant. That said, I'm thinking of uninstalling 2.0 and going back to 1.4.1. Version 2 seems slower in processing my Nikon files, and becomes totally unbearable when processing my P45+ files. Things just grind to a halt.
One thing I noticed is that I was getting some weird functional errors with my P45+ files UNTIL I optimized the library. Optimizing cleared up the functional errors, but didn't really do much for the slowdown I'm seeing. Anyway, run optimization on your library - it might help with the problems you're seeing.
-
On the Fred Miranda forum PP a guy said he talked to Adobe and that a fix was gonna have to be made on LR2 and Adobe will be releasing one soon.
-
On the Fred Miranda forum PP a guy said he talked to Adobe and that a fix was gonna have to be made on LR2 and Adobe will be releasing one soon.
[a href=\"index.php?act=findpost&pid=214193\"][{POST_SNAPBACK}][/a]
Uh huh. . .and I got a bridge in the desert I'll sell ya...
Look, there are a "few" know issues with the GM release of LR 2. I'm not at liberty to sya what and when any sort of fix will be coming but I will say that the VAST majority of people's issues seem to come from sloppy machines with other problems besides Lightroom, corrupted registries or preferences, bad catalog upgrades and lack of optimizations or a whole list of potential local machine issues.
If you want to contribute to the discussion, it would be useful to supply the basic troubleshooting info and what you've already done by yourself to troubleshoot;
Basic things such as uninstall, reinstall
Trashing the preferences
Testing a new catalog vs an updated catalog
Whether or not you've optimized the catalog
Where the catalog is relative to the image storage.
What admin privileges your user account has
Trying Lightroom in a new user account
The size of your captures and whether you are using native raw, DNG or TIFF/JPEG/PSD
Unless you give the basics of the information required to reliably review your situation, all you are doing is adding chaos and white noise to the situation...which will do nobody any good at all.
-
Uh huh. . .and I got a bridge in the desert I'll sell ya...
Look, there are a "few" know issues with the GM release of LR 2. I'm not at liberty to sya what and when any sort of fix will be coming but I will say that the VAST majority of people's issues seem to come from sloppy machines with other problems besides Lightroom, corrupted registries or preferences, bad catalog upgrades and lack of optimizations or a whole list of potential local machine issues.
If you want to contribute to the discussion, it would be useful to supply the basic troubleshooting info and what you've already done by yourself to troubleshoot;
Basic things such as uninstall, reinstall
Trashing the preferences
Testing a new catalog vs an updated catalog
Whether or not you've optimized the catalog
Where the catalog is relative to the image storage.
What admin privileges your user account has
Trying Lightroom in a new user account
The size of your captures and whether you are using native raw, DNG or TIFF/JPEG/PSD
Unless you give the basics of the information required to reliably review your situation, all you are doing is adding chaos and white noise to the situation...which will do nobody any good at all.
[a href=\"index.php?act=findpost&pid=214267\"][{POST_SNAPBACK}][/a]
"Look, there are a "few" know issues with the GM release of LR 2. I'm not at liberty to sya what and when any sort of fix will be coming but I will say that the VAST majority of people's issues seem to come from sloppy machines with other problems besides Lightroom, corrupted registries or preferences, bad catalog upgrades and lack of optimizations or a whole list of potential local machine issues."
That would probably be me...I think. Thanks for some of the suggestions.
Steve
-
Uh huh. . .and I got a bridge in the desert I'll sell ya...
Look, there are a "few" know issues with the GM release of LR 2. I'm not at liberty to sya what and when any sort of fix will be coming but I will say that the VAST majority of people's issues seem to come from sloppy machines with other problems besides Lightroom, corrupted registries or preferences, bad catalog upgrades and lack of optimizations or a whole list of potential local machine issues.
If you want to contribute to the discussion, it would be useful to supply the basic troubleshooting info and what you've already done by yourself to troubleshoot;
Basic things such as uninstall, reinstall
Trashing the preferences
Testing a new catalog vs an updated catalog
Whether or not you've optimized the catalog
Where the catalog is relative to the image storage.
What admin privileges your user account has
Trying Lightroom in a new user account
The size of your captures and whether you are using native raw, DNG or TIFF/JPEG/PSD
Unless you give the basics of the information required to reliably review your situation, all you are doing is adding chaos and white noise to the situation...which will do nobody any good at all.
[a href=\"index.php?act=findpost&pid=214267\"][{POST_SNAPBACK}][/a]
I was just saying I saw that posted on FM and I am glad to see you admit there is a problem with LR 2 because when some people over there that are a lot more computer literate then me that have fast as hell machines with over 8GB and LR2 is gumming up it ain't good Its clear Adobe released it premature .
Don
-
Its clear Adobe released it premature .
[a href=\"index.php?act=findpost&pid=214304\"][{POST_SNAPBACK}][/a]
I don't think that's a fair assessment. Windoze is a fairly open platform and its very difficult to test for all possible configurations and potential corruptions. That's why public beta programs have become popular.
-
Its clear Adobe released it premature .
[a href=\"index.php?act=findpost&pid=214304\"][{POST_SNAPBACK}][/a]
I don't think that's a fair assessment. Windoze is a fairly open platform and its very difficult to test for all possible configurations and potential corruptions. That's why public beta programs have become popular.
-
Its clear Adobe released it premature .
[a href=\"index.php?act=findpost&pid=214304\"][{POST_SNAPBACK}][/a]
I don't think that's a fair assessment. Windoze is a fairly open platform and its very difficult to test for all possible configurations and potential corruptions. That's why public beta programs have become popular.
-
I had a similar problem. Every time I selected a specific image and clicked the drop-down WB list, it would hang up right after that. I tried removing and re-importing, deleting the file and re-importing, recreating a DNG and re-importing. Nothing worked. What DID work was relauch and optimize.
Note I have removed LR 1.4 and 2.0beta.
Vista32, 4 gb ram (yeah, I know, it doesn't really use it...)
BTW, it was a particularly bad photo. Perhaps LR knows this and was protecting me from myself.
Dave Chew
-
"BTW, it was a particularly bad photo. Perhaps LR knows this and was protecting me from myself. "
Now that is real AI!! LOL
Cheers....
Todd
I had a similar problem. Every time I selected a specific image and clicked the drop-down WB list, it would hang up right after that. I tried removing and re-importing, deleting the file and re-importing, recreating a DNG and re-importing. Nothing worked. What DID work was relauch and optimize.
Note I have removed LR 1.4 and 2.0beta.
Vista32, 4 gb ram (yeah, I know, it doesn't really use it...)
BTW, it was a particularly bad photo. Perhaps LR knows this and was protecting me from myself.
Dave Chew
[a href=\"index.php?act=findpost&pid=214519\"][{POST_SNAPBACK}][/a]
-
I had a *ton* of problems with the 2.0 beta.
So far the 2.0 final release is rock solid. PC with Win XP 2.0 Both a laptop and desktop.
Best,
Michael
-
I don't think that's a fair assessment. Windoze is a fairly open platform and its very difficult to test for all possible configurations and potential corruptions. That's why public beta programs have become popular.
[a href=\"index.php?act=findpost&pid=214331\"][{POST_SNAPBACK}][/a]
''FWIW, the slow sliders that some are experiencing is a reproducible bug that was accidentally introduced just before release, and should be fixed in the next dot release''
From Victoria Queen of LR on Fred Miranda so I think I believe her
-
''FWIW, the slow sliders that some are experiencing is a reproducible bug that was accidentally introduced just before release, and should be fixed in the next dot release''
From Victoria Queen of LR on Fred Miranda so I think I believe her
[a href=\"index.php?act=findpost&pid=214677\"][{POST_SNAPBACK}][/a]
I don't doubt that in the least. Doesn't seem like it relates to a premature release on Adobe's part though.
I think you'd be thoroughly disappointed in how long it would take to fix every bug in software. It would never get released. All software gets shipped with a known list of bugs. Perhaps you'd be surprised to see the errata sheet for all the bugs in your Intel processor.
-
As I work events in LR 2 I've been keeping closer tabs on when it hangs or dies. I now run with Windoze Task Manager open and I was surprised to see that when LR 2 hangs it has started a second instance of LR2. I have no idea what that's about but its a behavior I've observed about 3-4 times today. Sometimes after a few minutes the second instance of LR goes away and it recovers, sometimes not.
-
Same thing happens to me - two instances of LR in the task manager when it hangs.
Dual opteron, dual core, winXP SP2, 3 gigs ram. No other program I have used in the last two years has crashed as often as LR2 does.
With all due respect to a response earlier in this thread about optimization, catalog backup/comparing, testing... My system is VERY stable and has been since I bought it 2 years ago or so... Photoshop runs without a hitch, bridge crashes every once in awhile, other software does crash - but very infrequently... there is something going on in LR2 to make it crash five times in one session of editing. I am still using the trial version, but I will tell you that I will NOT buy the software if it is going to be like this all the time...
*steve
As I work events in LR 2 I've been keeping closer tabs on when it hangs or dies. I now run with Windoze Task Manager open and I was surprised to see that when LR 2 hangs it has started a second instance of LR2. I have no idea what that's about but its a behavior I've observed about 3-4 times today. Sometimes after a few minutes the second instance of LR goes away and it recovers, sometimes not.
[a href=\"index.php?act=findpost&pid=215318\"][{POST_SNAPBACK}][/a]
-
Using MAC with TIGER,
When assigning keywords by selecting files, then dragging the files over the chosen keyword always causes a hangup. When I select the files, then highlight the keyword, right click on the keyword, then select assign to selected files, no hangup occurs.
All in all, 2.0 seems to be slower. Only have 3 GB RAM on MacBook Pro 17"
I have not uninstalled 1.4 yet. Will be upgrading to LEOPARD this week-end. Worried about how my Epson R2400 will work with LEOPARD.
-
I was having the same issue and found that uninstalling LR 1.4.1 has resolved much if not all of the delays.
I also found that LR 2.0 performance improved considerably after I uninstalled LR 1.4. I certainly wasn't running both at the same time, and I have no explanation other than that maybe there was some issue with the Common Files and the two versions.
I'm running WinXP Pro, SP2, with a Intel Core 2 Duo @ 2.0 GHz, 2 GB RAM.
Anecdotal evidence to be sure, but now I have very few issues with the new version. I notice that the Adjustment Brush can be pretty CPU intensive. My guess it takes a while for the program to update the SVG-type code that describes the gradient mesh to parametrically apply the adjustment. As I recall from the LL tutorial, Jeff recommends keeping the strokes as simple as possible.
Bill J
-
Reference: PC, XP Pro, 4 gigs ram, 32 bit mode, CPU = AMD Athlon 64 FX-53 (Socket 939) @ 2.4 GHz
LR 2.0 is slow, buggy, and hangs (requires close and loss of recent work). There is no configuration fix. The problem is Lightroom. This is not an open question. Ask anybody, including Adobe.
It may run fine on other machines. But on the reference PC it’s not worth the trouble. Waiting for next dot release.
p
btw, Photoshop CS3 and LR 1.4 run fast and smooth on the reference PC.
btw-2, I think Lightroom has a very bright future. Conceptually the best photo managment & minor edit tool in the world. Most intuitive (best) UI, period.
-
I find this very interesting; the # of problems being reported regarding Lightroom.
Maybe I'm not a heavy enough user to run into these.
I run LR 2.0 on a Windows Vista system (32 bit) with 4 GB RAM (only uses 3) and some sort of Intel Duo core processor. Although sometimes it will slowdown and "think" for a moment; I don't believe I have ever had it crash or slowdown more than 2 or 3 seconds.
I must be lucky! I guess it should be noted that my computer in general NEVER crashes (I'm very VERY careful about loading cr*p on my system) and that I have uninstalled all prior versions of Lightroom even before installing 2.0.
Todd in Chicago
Reference: PC, XP Pro, 4 gigs ram, 32 bit mode, CPU = AMD Athlon 64 FX-53 (Socket 939) @ 2.4 GHz
LR 2.0 is slow, buggy, and hangs (requires close and loss of recent work). There is no configuration fix. The problem is Lightroom. This is not an open question. Ask anybody, including Adobe.
It may run fine on other machines. But on the reference PC it’s not worth the trouble. Waiting for next dot release.
p
btw, Photoshop CS3 and LR 1.4 run fast and smooth on the reference PC.
btw-2, I think Lightroom has a very bright future. Conceptually the best photo managment & minor edit tool in the world. Most intuitive (best) UI, period.
[a href=\"index.php?act=findpost&pid=217190\"][{POST_SNAPBACK}][/a]
-
I am having a somewhat different problem, but I think it is related. Using key words, adding, removing, changing is very slow on my Win XP SP2 system.
Using 3 ghz dual core, 4 gm ram, SATA 3G hard drive
I tried optimizing database, defragmenting hard drive which has 24 gb space open.
To delete one of two key words from a photo using LR2 stops the program for 25 seconds (before you can do anything with Lr). Doing anything with the keyword list takes the same 25 seconds. This includes creating new key words, deleting or moving key words, or adding a keyword to a photos.
When I open the same photo in LR 1.4, I deleted the same keyword (different database) and LR never slowed down. Response was instantaneous.
Both catalogs have the same number of photos and are large. (about 50,000 pictures)
Could this be the same problem?
David Gardner
-
... When I open the same photo in LR 1.4 ...
David Gardner
[a href=\"index.php?act=findpost&pid=217346\"][{POST_SNAPBACK}][/a]
Dave,
Just for grins, try uninstalling LR 1.4.1 and do some testing. On my windows PC this alleviated much of the slowness. Certain areas are still slow, but keywording is much better, my experience was similar to yours.
Your timing of 25 seconds caught my eye. After doing all of the optimizations steps I still have a persistent lag of 25 seconds from the time that I delete (from disk as well as from the catalog) an image and lightroom completes the delete and returns control to me. I'd be curious if you experience the same lag when deleting images.
- Morey
-
Dave,
Just for grins, try uninstalling LR 1.4.1 and do some testing. On my windows PC this alleviated much of the slowness. Certain areas are still slow, but keywording is much better, my experience was similar to yours.
Your timing of 25 seconds caught my eye. After doing all of the optimizations steps I still have a persistent lag of 25 seconds from the time that I delete (from disk as well as from the catalog) an image and lightroom completes the delete and returns control to me. I'd be curious if you experience the same lag when deleting images.
- Morey
[a href=\"index.php?act=findpost&pid=217487\"][{POST_SNAPBACK}][/a]
I have the feeling that, at least on Win platform, many of the long delays or hangups (not crashes mind you) experienced both by me and other users, in quite high-end rigs I might add, have to do with Lightroom's task synchronisation. I am convinced by now that there are serious bugs in the program that I hope will get addressed in a dot release. The sooner the better.
-
Dave,
Just for grins, try uninstalling LR 1.4.1 and do some testing. On my windows PC this alleviated much of the slowness. Certain areas are still slow, but keywording is much better, my experience was similar to yours.
Your timing of 25 seconds caught my eye. After doing all of the optimizations steps I still have a persistent lag of 25 seconds from the time that I delete (from disk as well as from the catalog) an image and lightroom completes the delete and returns control to me. I'd be curious if you experience the same lag when deleting images.
- Morey
[a href=\"index.php?act=findpost&pid=217487\"][{POST_SNAPBACK}][/a]
Thanks for the suggestion. At the present time I am more inclined to remove LR2! If I remove LR1, will it leave the catalog?
I have done some testing with task manager. When a add a key word, Task manager shows two LR programs running, both non responding. CPU usage goes up to >80%. After about 25 seconds, CPU usage goes down, only one of the LR programs is present and it says it is running!
When I delete a photo it takes 20 seconds before the system is functional again.
Dave
-
I have the feeling that, at least on Win platform, many of the long delays or hangups (not crashes mind you) experienced both by me and other users, in quite high-end rigs I might add, have to do with Lightroom's task synchronisation. I am convinced by now that there are serious bugs in the program that I hope will get addressed in a dot release. The sooner the better.
[a href=\"index.php?act=findpost&pid=217516\"][{POST_SNAPBACK}][/a]
I am very much in agreement with you!
Dave
-
... If I remove LR1, will it leave the catalog?
I have done some testing with task manager. When a add a key word, Task manager shows two LR programs running, both non responding. CPU usage goes up to >80%. After about 25 seconds, CPU usage goes down, only one of the LR programs is present and it says it is running!
When I delete a photo it takes 20 seconds before the system is functional again.
[a href=\"index.php?act=findpost&pid=217541\"][{POST_SNAPBACK}][/a]
Uninstalling LR1 will not effect your LR1 catalogs and can be easily reinstalled if need be.
Interesting that you see the same delay in deleting. My guess is the file management (reading writing files) is broken in LR2. Any kind of disk activity is taking a long time.
- Morey
-
After reading all the posts here, and on other sites, decided to upgrade my computer.
Some LR-2 speed improvement accomplished by upgrading the MBP HD to a larger and faster (7500 RPM), upgraded to max memory (4GB), upgraded to Leopard. This allowed 64 bit operation. Also moved the library off my external disk where my photos are to the default location where LR puts it in my user location. The results are amazing. Also deleted the preferences file and reset the preferences.
I think the location of the LR library was key here. Everything else helped. LR now runs without hangups.
Hope this helps others with similar slow working LR-2.
Adrian
-
Dave....funny you should mention that. I had a similar weird thing happen.
If I right-click (PC) on an image in the filmstrip, delete, remove from disk, it will take way longer than I would expect for such a simple operation. However, if I click on the image in the main viewing area (let's say in loupe mode) the delete happens at normal speed (pretty quickly). This has fairly easy to reproduce. Anyone else see this same exact specific "odd" behaviour?
Cheers.....
Todd in Chicago
Thanks for the suggestion. At the present time I am more inclined to remove LR2! If I remove LR1, will it leave the catalog?
I have done some testing with task manager. When a add a key word, Task manager shows two LR programs running, both non responding. CPU usage goes up to >80%. After about 25 seconds, CPU usage goes down, only one of the LR programs is present and it says it is running!
When I delete a photo it takes 20 seconds before the system is functional again.
Dave
[a href=\"index.php?act=findpost&pid=217541\"][{POST_SNAPBACK}][/a]
-
It appears I have solved the problems with delays when adding key words to pictures.. I deleted LR 1.4 but this did not help. In My Pitures, Lightroom2 folder, there were two catalogs one used by LR2, but the other was being used by LR 1.4. When I changed the extension of the LR 1.4 so it was no longer recognized as a catalog, my keywording became instantaneous.
I suspect the LR 2 is updating both catalogs and may be calling a LR 1.4 module. That would explain why task manager sees two LR programs running when it slows down.
I would be interested if any one else finds this as a fix
Dave
-
Dave,
Thanks for the neat idea. I'm testing it now. No problems since moving the LR1 catalog I had. If I get a hang I'll check Task Mgr again.
-
It appears I have solved the problems with delays when adding key words to pictures.. I deleted LR 1.4 but this did not help. In My Pitures, Lightroom2 folder, there were two catalogs one used by LR2, but the other was being used by LR 1.4. When I changed the extension of the LR 1.4 so it was no longer recognized as a catalog, my keywording became instantaneous.
I suspect the LR 2 is updating both catalogs and may be calling a LR 1.4 module. That would explain why task manager sees two LR programs running when it slows down.
I would be interested if any one else finds this as a fix
Dave
[a href=\"index.php?act=findpost&pid=218479\"][{POST_SNAPBACK}][/a]
If LR2 is updating a LR1.4 catalog that in any case was not defined as a working catalog to the program, then this is a MAJOR screwup. I find it hard to believe that this is the case.
Two instances of LR being shown sometimes on the task manager is true though. I notice that when I get these (sometimes terminal) hangups but I can't say if this behaviour (two instances of the app being shown) is normal or not. I suspect it is normal.
-
If LR2 is updating a LR1.4 catalog that in any case was not defined as a working catalog to the program, then this is a MAJOR screwup. I find it hard to believe that this is the case.
Two instances of LR being shown sometimes on the task manager is true though. I notice that when I get these (sometimes terminal) hangups but I can't say if this behaviour (two instances of the app being shown) is normal or not. I suspect it is normal.
[a href=\"index.php?act=findpost&pid=218642\"][{POST_SNAPBACK}][/a]
I am only speculating. It is clear that changing the extension of the LR 1.4 catalog (which is in the LR 2 directory) does eliminate the problem.
Rather than being a screw up, I wonder if it does it so both catalogs are kept up to date so you can continue to use LR 1.4 and have the same information.
Once again I am only speculating.
Dave
-
If LR2 is updating a LR1.4 catalog that in any case was not defined as a working catalog to the program, then this is a MAJOR screwup. I find it hard to believe that this is the case.
Two instances of LR being shown sometimes on the task manager is true though. I notice that when I get these (sometimes terminal) hangups but I can't say if this behaviour (two instances of the app being shown) is normal or not. I suspect it is normal.
[a href=\"index.php?act=findpost&pid=218642\"][{POST_SNAPBACK}][/a]
I just checked task manager and when I add a keyword to a photo, LR 2 no longer opens two instances.
Dave
-
I just checked task manager and when I add a keyword to a photo, LR 2 no longer opens two instances.
Dave
[a href=\"index.php?act=findpost&pid=218679\"][{POST_SNAPBACK}][/a]
Well after working great all day, the problem developed again so I guess that was not the problem.
At present I am stumped.
Any suggestions would be welcome.
I do not understand why the problem is intermittent.
Dave
-
Dave,
I think at this point the only suggestion is to wait for Lightroom 2.1
I hope we don't have a long wait. There are a number of bugs that need squashing.
-
Dave,
I think at this point the only suggestion is to wait for Lightroom 2.1
I hope we don't have a long wait. There are a number of bugs that need squashing.
[a href=\"index.php?act=findpost&pid=218744\"][{POST_SNAPBACK}][/a]
A 2.1 update will probably follow pretty soon. First of all, they have to add support for the latest cameras like EOS 50D, Nikon D90, the upcoming Sony A900 and EOS 5D successor.
The 2.1 will also contain bug fixes for everything users found so far. I am sure of that.
Markus
-
I've been using 2.0 since it came out. The only problems that I have experienced on my MacPro 8-core are as follows:
1 - The random spinning beach ball during some operations that is annoying.
2 - When using the Tone Curve Target Button, the cursor does not revert back to a normal cursor. The only way that I found to turn the Target Button off is to click on another function like crop or clone and then click again on the same function. This restores the cursor that clicking on the image in the Develop module zooms in and out. I think that this is a bug.
3 - Not a problem with design, but a missing feature is soft proofing. With the cost of ink and media, soft proofing is an important feature to get an idea of what your print is going to look like when combining the selected paper profile and output sharpening.
Other than that, LR 2.0 is a great improvement over 1.4. Now I find myself using Photoshop CS3 less than 5% of the time for final prints.
Bud James
North Wales, PA
budjamesphotography.com (http://www.budjamesphotography.com)
-
Bud,
1. Will be fixed soon.
2. Not a bug. The TAT tool stays active by design, so you can do multiple operations with it. Click the Done button in the toolbar below the image when you're done with it, or switch to another tool.
3. Agree, it's missing, and it won't be part of any LR 2.x version.
-
I have to report that today I started using release candidate 2.1. So far, I have not been able to reproduce the problems I had and the program feels smoother. That's good news.
For those still trying out the program, be aware that RC1 will extend your trial period for another 30 days. Good one Adobe.
-
Nikos, thanks for the report. Its great to hear that they're making headway on the bugs. What OS are you running on?
-
Nikos, thanks for the report. Its great to hear that they're making headway on the bugs. What OS are you running on?
[a href=\"index.php?act=findpost&pid=222868\"][{POST_SNAPBACK}][/a]
Both XP SP3 and OSX. Most of my problems were evident on XP SP3 but that doesn't mean a thing since it's XP that I make heavy use of LR on. My Mac is underpowered so sometimes I can't distinguish a problem from general sluggishness.
-
I just loaded the LR 2.1 release candidate and, at least on my MacPro, LR is much better behaved. I use to see the "spinning wheel of death" all the time with 2.0; 2.1 much, much better.
Steve
-
I have had some hangs too. Mostly when working on high res film scans, big files. It just sometimes sits there and dies!
Even pre rendering 1:1 previews didnt help.
-
I have had some hangs too. Mostly when working on high res film scans, big files. It just sometimes sits there and dies!
Even pre rendering 1:1 previews didnt help.
The hangs haven't gone away for me either. I had 1,000 images from a 1D2 and 5D to go through so I bit the bullet and tried RC 2.1 to see if it would fix the hangs. No joy.
-
Well..... 2.1 RC1 has been around for about a month now. I'm wondering if there's going to be an RC2 or perhaps a real 2.1 soon. RC1 works fine on my laptop with no hangs but not on my desktop machine.
Has anyone heard anything?