Skip to main content
Adobe Photoshop Family

248 Messages

 • 

4.1K Points

Tue, Dec 24, 2019 10:03 PM

Lightroom Classic: Will you PLEASE fix ongoing problems

I've been dealing with these two issues since at least LR 3.0.

1.  Select and move or delete files and one file is not moved or deleted.
2.  Previews are not properly rendered and appear slightly blurry.  An adobe engineer suggested this might be caused by a thread race condition.

Both behaviors are totally unacceptable for an adobe product - but to not fix for a decade.  C'mon - I thought the rent program was going to let you deal with this stuff.

PLEASE FIX!!

Responses

147 Messages

 • 

2.4K Points

10 months ago

Re:#1. What module are you in?

248 Messages

 • 

4.1K Points

Library.

170 Messages

 • 

4.4K Points

10 months ago

We're not paying to rent the software. We're paying to be their beta testers.

Champion

 • 

751 Messages

 • 

13.3K Points

That was helpfull

170 Messages

 • 

4.4K Points

It is helpful if it prompts Adobe to do a better job of QA testing. It's shameful of Adobe to keep putting out versions which break people's functions and workflows. Especially those who depend on the product in a business environment.

Champion

 • 

219 Messages

 • 

3.9K Points

10 months ago

If you want help it is helpful to provide details of your system and what you are doing in each of 1 and 2.There are no live issues like you are stating so let us see if we can isolate why you have this experience.

248 Messages

 • 

4.1K Points

Geoff - I'm using Win 10.  Item 1 is an issue in both grid and loupe views.  It does not occur all the time, but quite often.  I have seen this reported several times over the years.  Item 2 is in loupe view, and again, has be reported several times.

143 Messages

 • 

2.9K Points

Windows also, same issues. It's a PITA, especially when working with Panoramas - had to change my workflow to get around the inevitable move failures.

3 Messages

 • 

514 Points

10 months ago

I must be imagining I've had problems like these for years ... Sorry for disturbing you.

Champion

 • 

219 Messages

 • 

3.9K Points

Very useful

Champion

 • 

219 Messages

 • 

3.9K Points

Very useful

442 Messages

 • 

6.6K Points

Well, Gary, I've used LR since it was invented and I've never had either of your problems. I assume it is a problem in your setup or hardware. What are you using? Mac or windows? etc etc.

Happy Christmas,

Bob Frost

143 Messages

 • 

2.9K Points

Hi Geoff, I also have used LR since the start (from RawShooter). I use Windows.
That should be enough, as over this timespan the issues are always there, over all subsequent versions of Windows, AMD/Intel CPUs & motherboards, various flavours & amounts of RAM, etc etc. across all updates of LR.

1 Message

 • 

60 Points

10 months ago

These aren't the only problems. Lighroom should have a "feedback" button on the help menu like Google often uses in their apps. My current install of lightroom is buggy and hangs every few seconds during launch, export, and any other processor intensive operation. It's only the newest version that does this. Also automatic perspective correction doesn't work. These forums don't seem very helpful to get attention with problems. Adobe! Get it in gear or someone will come along and steal your spot...

Champion

 • 

3.1K Messages

 • 

56.1K Points

I'm amazed you know so well how these forums work after just posting for the first time...

Johan W. Elzenga,

http://www.johanfoto.com

170 Messages

 • 

4.4K Points

Not a helpful reply to a paying customer. Whatever happened to "The customer is always right?"

Champion

 • 

3.1K Messages

 • 

56.1K Points

I am not an Adobe employee, so this is not my (paying) customer. If somebody makes a statement like this about a forum, without having ever posted a message in that forum, then she is asking for a sarcastic remark.

Johan W. Elzenga,

http://www.johanfoto.com

143 Messages

 • 

2.9K Points

God, I'd love to be as smart and righteous as you... I mean, yes, how dare they - how could they know the forum and all of the posts in it if they haven't posted to it before!

71 Messages

 • 

3.4K Points

10 months ago

Must admit that the OP's first point does occur for me too.

I'm a Win 10 LR Classic User and have been with LR for many years. In all that time, I have seen an intermittent issue with moving files (I've never noticed it on deleting).

When in Library mode, if a group of photos is selected to move, then sometimes, a single image (I'm fairly sure its always the last in the view) is left behind un-moved. I have never been able to replicate this in any way, it just happens periodically.

I have one thought on it that suggests it is more likely if I select the last file in the view, then click select the top one, than if I do it the other way round. But I don't have consistency in this behaviour.

The only other possible link I have is that frequently when renaming a folder within LR, this will sometimes fail (error msg saying cannot rename) if the folder is open in Windows Explorer. Again, there is no clear behaviour on this point, but I wonder if the two might be linked.



Champion

 • 

3.1K Messages

 • 

56.1K Points

10 months ago

I can understand your frustration that this does not get resolved, but put yourself in Adobe technical staff shoes for a moment. A customer has a problem he cannot replicate. It sometimes happens and other times it does not happen. It’s not possible to make it happen on demand. How are you supposed to deal with such a bug (if it really is a bug, and not user error after all)?

Johan W. Elzenga,

http://www.johanfoto.com

143 Messages

 • 

2.9K Points

A random bug is hard to deal with, yes, but over so long a time? I'd say they either a) couldn't be bothered, or b) they know what it is but its inherent and a fix would be too expensive. (I'm basing this on 40 years of development experience)

165 Messages

 • 

2.9K Points

Maybe it's my shorter time spent as a developer, but I've never heard of any properly-managed development team changing code without reproducing a problem (especially in an app as complex as LR). You'd try to get as much info as possible to reproduce the environment & circumstances where the anomaly occurred, but if it can't be reproduced in either the development/test environment or on the reporting customer's own system - then no developer would go change a piece of code based on hope (no test manager would approve it either). Doesn't matter how long the issue has been intermittently reported - if a developer can't see it, they can't fix it.

The OP (Rory) said Issue #1 does not occur all the time, but quite often. If it only occurs when he's processing panoramas, then it might be worth his time to record all such sessions until it happens again, so he can pass on the recording to Adobe Support.

Issue #2 should be easier to reproduce...

71 Messages

 • 

3.4K Points

10 months ago

Not sure who you were aiming your reply at, but if it was me, I was certainly not expressing any frustration. All I did was try to give some evidence to back up the OP's point.

"How are you supposed to deal with such a bug"

I thought the whole point of a forum like this was that a user could report an issue, and others would add/detract from the discussion, to try and gain a consensus on what the issue actually is.

That is how you deal with it!

Champion

 • 

3.1K Messages

 • 

56.1K Points

My point was that as long as issues cannot be reproduced, not even by the people who report them, it’s virtually impossible for the technical staff reading this to solve this issue. But if you experience such an issue from time to time, it can be frustrating nevertheless. The OP certainly sounds frustrated, and a few other people too.

Johan W. Elzenga,

http://www.johanfoto.com

143 Messages

 • 

2.9K Points

Thanks for the more reasoned response. This issue has been a running gripe for me, usually waiting to rear its head when l'm least expecting it :(
I've changed methodology for dealing with Panoramas so that I don't have to perform a move anymore, and the deletes are usually less of a problem.
I'd also throw in (I think it's related) LR's random dislike of renaming a file - a really frustrating experience when the new name is long and technical.

165 Messages

 • 

2.9K Points

Gary, regarding the seemingly random dislike of renaming a file (when the new name is long and technical), have you ever checked if the fully qualified filename (i.e. absolute pathname plus filename) doesn't exceed Windows' MAXPATH limitation? See: https://docs.microsoft.com/en-us/windows/win32/fileio/naming-a-file#maximum-path-length-limitation

The above also gives a potential workaround for newer versions of Windows (which require a setting to be changed in order to opt-in)...

143 Messages

 • 

2.9K Points

Hi Edmund, no the names aren't that long; it's a matter of trying & retrying until LR accepts the new name, sometiumes taking up to 6 attempts :(

Champion

 • 

751 Messages

 • 

13.3K Points

What are the Rename dialog settings?