• Welcome to the Lightroom Queen Forums! We're a friendly bunch, so please feel free to register and join in the conversation. If you're not familiar with forums, you'll find step by step instructions on how to post your first thread under Help at the bottom of the page. You're also welcome to download our free Lightroom Quick Start eBooks and explore our other FAQ resources.
  • Stop struggling with Lightroom! There's no need to spend hours hunting for the answers to your Lightroom Classic questions. All the information you need is in Adobe Lightroom Classic - The Missing FAQ!

    To help you get started, there's a series of easy tutorials to guide you through a simple workflow. As you grow in confidence, the book switches to a conversational FAQ format, so you can quickly find answers to advanced questions. And better still, the eBooks are updated for every release, so it's always up to date.
  • Dark mode now has a single preference for the whole site! It's a simple toggle switch in the bottom right-hand corner of any page. As it uses a cookie to store your preference, you may need to dismiss the cookie banner before you can see it. Any problems, please let us know!

GPS Pin in wrong position

Status
Not open for further replies.

Dave M

New Member
Premium Classic Member
Joined
Apr 3, 2019
Messages
12
Lightroom Version Number
Classic 12.0.1 Desktop
Operating System
  1. Windows 11
When I drag any photo onto the Map module with my mouse and release it at the position I want, the yellow pin always appears incorrectly about 30 yards north west.
If I then select the pin and drag it back to the original position, it now appears correctly. Any suggestions as to what is wrong are welcome.
 
Last edited:
I believe this is a known bug.
 
Thanks John. I've reverted to using the font selection 'Auto' in Lightroom's preferences & Windows 11 scaling 100%.
The GPS pins now work again correctly with these settings. I am left wondering why Adobe techies are content to leave a known issue unsolved for so long. If they can't be bothered to fix it, why continue to leave in menu items that cause the problems? Most odd !
 
I am left wondering why Adobe techies are content to leave a known issue unsolved for so long. If they can't be bothered to fix it, why continue to leave in menu items that cause the problems?
I have no inside information. My educated speculation as a former engineering and product manager and longtime plugin developer: Almost certainly the managers have concluded that the cost of fixing the bug is too high for them. Likely influencing factors: The bug only strikes in some circumstances; it has a straightforward workaround; they may not have the engineering skills in-house. I've long suspected the last factor is in play -- the Map module uses a Javascript library for displaying Google Maps, and the engineer who first implemented it years ago is likely long gone from the LR team. LR doesn't use Javascript otherwise, so to fix this could involve hiring an outside contractor. It might also involve significant modifications or rewrites to the Javascript library, given its age.

There are many such bugs in LR that have gone unfixed. Because there aren't any serious competitors to LR (a desktop digital asset manager with an integrated raw workflow), Adobe doesn't have to worry much about customer defection or blowback to its brand reputation. I think Adobe underestimates the long-term impact of such an approach on customer perception and its own engineering team -- top engineers don't stay around long in companies that don't take pride in their work.
 
Thanks again John- I agree with all you say. I think Adobe seems to be - like Apple - spending all its energy on new flashy toys and is neglecting all those who brought success in days gone by.
 
I have no inside information. My educated speculation as a former engineering and product manager and longtime plugin developer: Almost certainly the managers have concluded that the cost of fixing the bug is too high for them. Likely influencing factors: The bug only strikes in some circumstances; it has a straightforward workaround; they may not have the engineering skills in-house. I've long suspected the last factor is in play -- the Map module uses a Javascript library for displaying Google Maps, and the engineer who first implemented it years ago is likely long gone from the LR team. LR doesn't use Javascript otherwise, so to fix this could involve hiring an outside contractor. It might also involve significant modifications or rewrites to the Javascript library, given its age.

There are many such bugs in LR that have gone unfixed. Because there aren't any serious competitors to LR (a desktop digital asset manager with an integrated raw workflow), Adobe doesn't have to worry much about customer defection or blowback to its brand reputation. I think Adobe underestimates the long-term impact of such an approach on customer perception and its own engineering team -- top engineers don't stay around long in companies that don't take pride in their work.
A very, very belated comment on John's excellent post.

By the time the company, Adobe in this case, realizes the long-term reputational damage, it may be too late to fix this issue. If issues like these fester long enough, a competitor has the opportunity to swoop in, hire some good Adobe engineers, and gain significant market share. Not a prediction, but something that should worry Adobe top management when they aren't focusing on quarterly earnings growth.
 
Status
Not open for further replies.
Back
Top