Lightroom: Time to refund the purchase of LR4

  • 2
  • Question
  • Updated 6 years ago
  • (Edited)
There are many loyal Adobe and Lightroom clients, including me, who are struggling with LR4. Considering that this version is full of bugs and problems, shouldn't Adobe consider refunding all of the money that people have paid to purchase LR4. Get us all back to LR3.6 and then when you get your act together and have a workable LR4, offer it again. This fix is taking too long and I for one, am tired of seeing reports saying that you are working to improve performance. Performance is not the issue. LR4 is not a workable product.
Photo of Lance Levine

Lance Levine

  • 44 Posts
  • 0 Reply Likes

Posted 6 years ago

  • 2
Photo of jdv

jdv, Champion

  • 728 Posts
  • 55 Reply Likes
You can just call Adobe up and ask for a refund. You can also just roll back to 3.6 right now while that is sorted out.
Photo of Lee Jay

Lee Jay

  • 990 Posts
  • 131 Reply Likes
"LR4 is not a workable product."

I know some people are having real problems, and I'm having some problems, but I have processed about 10,000 images with it so far.
Photo of Lance Levine

Lance Levine

  • 44 Posts
  • 0 Reply Likes
Tried another test to see if this might help Adobe. My computer is a late 2009 Imac 27, ios 10.7.3, 2.86 hz, intel core I7, 8gb ram. I have about 63000 pictures in my catalog. Everything ran great with LR 3.6.

1. opened LR4.1, moved 3 pix, then moved 4 pix, then moved 1 pix. All moved ok and relatively fast (less than 1 sec per pix.)
2. moved 14 pix. all ok.
3. moved 14 pix all ok.
4. in library mode, opened one pix. moved 14 pix ok. Took about 12 sec for the 14 pix.
5. in develop mode, opened 1 pix.
6. in library mode, moved 14 pix. very slow.
7. closed and restarted LR. moved 14 pix. very slow.
8. closed LR, restarted Mac, opened LR, moved 4 pix. slow.
9. Moved 9 pix took 3.5 sec per pix.
10. Moved 14 pix took 44 seconds.
11. went to develop mode, opened 1 pix, changed view to 1:1, back to library mode, moved same 14 pix. Took 101 seconds.

Not sure if this adds anything to the conversation, but I hope it helps put the puzzle together and get this previously great program working again.
Photo of jdv

jdv, Champion

  • 728 Posts
  • 55 Reply Likes
It is unclear exactly what you are demonstrating here. What does "move pix" mean? Do you mean moving image files around within the Folders panel?

If so, my first question is, why are you doing this so much? You are stacking up a fair number of async updates to the catalogue, so my second question is, have you optimized the catalogue recently?

Anyway, have you captured a "sample" of the Lr process from Activity Monitor when reproducing the problem?

Also, where are your image files located? Are they on a local volume. Likewise, where is your catalogue located.
Photo of Lance Levine

Lance Levine

  • 44 Posts
  • 0 Reply Likes
I think i lost a long answer that I was trying to send. I'll try to write again.
I was just testing to try and offer assistance to adobe.

I was moving picture files from one folder to another on the same drive. My catalog is also on the same drive.

I have optimized frequently. It hasn't shown any improvements.

Not sure what I should be focusing on in activity monitor. I have looked at it. I"m not a techy. Just a longtime LR user. Started with ver 1.

Look at all my posts to see my experiences with this miserable 4.0 release.

I have many of the other symptoms also. I've just been focusing on the moving files from one folder to another issue.

At Adobe's request, I sent a zipped catalog days ago. I have heard nothing.

Please read all my posts so I don't have to repeat all the history.

Thanks.
Photo of jdv

jdv, Champion

  • 728 Posts
  • 55 Reply Likes
So, just to be clear: Adobe is working on your problem, perhaps in concert with other issues some people have reported, and this is the thread you start?

How about if we start again?

It can take time to analyze problems, so not getting anything back from a company for a few days after you supply them with information is normal.

If you are seeing a performance issue, the best way to solve it is to work from the known to the unknown. Since we know that not everyone is seeing what you are seeing, the first step is reproducing the problem and collecting good information.

1. Get a "sample" of the Lightroom process when you experience the problem. To do this, run Activity Monitor. When the Lr UI seems to be exhibiting the symptoms you report earlier, select the Lightroom process, and select "Sample Process":



Save the results in case Adobe wants to see them, or post them back here somehow -- either as an attachment if that works, or with a service like yousendit.

If you want to get even more targeted info, try this:

1. Open Terminal
2. Run the following commands:
cd ~/Desktop
sudo fs_usage -f filesys "Adobe Photoshop Lightroom 4.app" > fs_usage.out

Let this run for a while while you reproduce the problem in Lightroom. When it you have let it run for a few minutes, go back into Terminal and press "control-c" (hold down the control key and press the "c" key at the same time). Again, keep the file it created on your desktop for Adobe.