• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
29

P: Placing photos on Map module erratic and slow since update LR Classic CC 7.5 (Windows)

Engaged ,
Aug 22, 2018 Aug 22, 2018

Copy link to clipboard

Copied

I geotag photos on a daily basis, and today, after updating LR Classic CC to version 7.5, I was going to resume my geotagging tasks as usual, but then I started to experience weird issues when placing photos on the map.

Most of the time, the problem is that I drag the photo from the filmstrip to the map (in the Map module, of course), and nothing happens (no photo on the map, no gps coordinates in the metadata). If I drag and hold the photo over the map for a few seconds before releasing the mouse button, sometimes it does place the photo.

I would say it's even more difficult when I select several photos and try to place them on the same spot at once, but I can't say absolutely for sure.

Also, selecting the photo (or photos) and then Ctrl+clicking (Windows) on the map to place them stopped working altogether as soon as I updated to 7.5, no matter how long I kept the keys or mouse button pressed down, or how many times I tried (previously, I was using this shortcut dozens of times a day).

Since I do need to keep geotagging photos, and with v7.5 it was much more difficult, I've downgraded to 7.4 and now things are working ok again. Of course I can't absolutely say for sure that this is an universal issue but... this is what's happening on my system. Any idea what could be going on? Thanks.

My first 10 lines in Help>Sytem info:

Lightroom Classic version: 7.5 [ 1186149 ]
License: Creative Cloud
Language setting: en
Operating system: Windows 10 - Business Edition
Version: 10.0.17134
Application architecture: x64
System architecture: x64
Logical processor count: 8
Processor speed: 4,0 GHz
Built-in memory: 16314,6 MB

Bug Fixed
TOPICS
macOS , Windows

Views

446

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 3 Correct answers

Adobe Employee , Oct 15, 2018 Oct 15, 2018
Greetings, 

The Lightroom Classic CC was updated today and contains a fix for this issue. Please download the new version and give it a try and let us know how it works.

Votes

Translate

Translate
Adobe Employee , Sep 12, 2018 Sep 12, 2018
Thanks for your patience!

We have upgraded the limits for the API again - request you to please give it a try and report any issues.

Joop, I understand your concern - but recent changes in our Map APIs mean that we have to make an API call over the internet to deduce the coordinates, as well as the geocode information. So, even if you have address lookup switched off, Lightroom does make an API call to deduce only the coordinates. Hope it clears your concerns!

Thanks again.

Votes

Translate

Translate
Adobe Employee , Sep 02, 2018 Sep 02, 2018
We are actively looking into this issue - it seems to intermittently occur in our test scenarios as well, albeit without a pattern. We are collecting a few logs and investigating the possible root cause. Hang on.

Apologies for the inconvenience, and thanks for being persistent!

Votes

Translate

Translate
replies 116 Replies 116
116 Comments
Engaged ,
Dec 18, 2018 Dec 18, 2018

Copy link to clipboard

Copied

J'ignorais qu'il y avait un forum francophone. Quelle est son adresse ?

Votes

Translate

Translate

Report

Report
LEGEND ,
Dec 19, 2018 Dec 19, 2018

Copy link to clipboard

Copied

@Philippe Coudé du Foresto

Il s'agit d'un forum généraliste ( donc pas spécialisé LR). Si je me rappelle bien c'est Philippe Duval qui avait posté la question sur ce forum. C'est lui qui pourra  indiquer la réponse comme correcte après avoir ajouté sa solution sur la discussion initiale.
J'avoue qu'à aucun moment je n'ai pensé à demander si le logiciel faisait partie d'une "liste blanche" de son par-feu.

Voici l'adresse du forum.
https://forums.adobe.com/community/international_forums/francais

Votes

Translate

Translate

Report

Report
Explorer ,
Jan 21, 2019 Jan 21, 2019

Copy link to clipboard

Copied

So is there any update on when this core feature will actually be fixed?  I'm on Lightroom CC 8.1 now (latest version) and still having exactly the same issue - find desired location on map, highlight images then drag them on to map and nothing happens.  Really frustrating for this to still not be working so many months on.  For now I'm having to find location on Google Maps separately, manually copy and paste the GPS co-ordinates.  Total pain!

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Jan 21, 2019 Jan 21, 2019

Copy link to clipboard

Copied

Hi Alan, sorry to hear about your inconvenience.

We have seen instances where a firewall conflict or invalid GPS data available in the catalog have been a cause for these issues. Could you please share the log file as described here?
https://feedback.photoshop.com/photoshop_family/topics/lightroom-8-latest-update-win10-drag-and-drop...

Thanks for your patience and help.

Votes

Translate

Translate

Report

Report
LEGEND ,
Jan 22, 2019 Jan 22, 2019

Copy link to clipboard

Copied

I have exactly the same problem!!!!!!






Votes

Translate

Translate

Report

Report
Community Beginner ,
Mar 19, 2019 Mar 19, 2019

Copy link to clipboard

Copied

I reported earlier in this thread, but since the improvements in September 2018 geotagging in LR 7.6, 8 and now 8.2 worked fine for me: always, fast, flawlessly. However, today March 19th, 2019 around 15:00 CET geotagging stopped working. First a few slow reactions, then nothing. No geotags are being placed anymore. After waiting and restarting it worked again once or twice, but again stopped. A 3rd restart, and then even the maps wouldn't be retrieved correctly or not at all: see image

RackMultipart20190319101016nwr-f5987dd4-f838-48bd-a4dc-ef844bfdd16e-841381104.jpg

I need geotagging badly, I still have thousands of photos to be tagged from years passed. I was happy it worked again last year, but now... desolated. I hope they are just passing Adobe server problems. All in all, it took me 2 hours to geotag 52 photos in the folder at hand.

Btw, I still don't understand why since version 7.5 geotags would have to be placed by a web call to the server. In LR maps mode you have a map open, so you have a geographic grid reference in your window (never mind the image of the map that is showing). If you place a pin in a certain location, the coordinates could easily be calculated locally, I gather. I could understand the map images are being retrieved in a web call, but not the coordinates. In that way you are too vulnerable to web traffic issues.

Please provide us with a better working solution.

One more thing: what does this warning mean: "Too many map requests"? I got it in the past 2 months, each time after geotagging a few dozen photos (and moving the map several times). Once started it keeps coming, but geotagging kept working nevertheless. It is a bit annoying.

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Mar 22, 2019 Mar 22, 2019

Copy link to clipboard

Copied

Thanks, Joop for your feedback, and sorry for the inconvenience.

Because of a change in the service provider APIs, Lightroom has to make additional web calls to deduce the coordinates from the map view while geocoding. "Too many requests" may sometimes show up if there are too many such requests to the map service provider being made within a short time. These also include the panning requests from the map view, along with the Geocoding requests. 

Have you tried disabling and enabling the Address Lookup option before restarting? Are there any images getting stuck while Address lookup is running?

Votes

Translate

Translate

Report

Report
Community Beginner ,
Mar 23, 2019 Mar 23, 2019

Copy link to clipboard

Copied

Thank you for the explanation. I imagine that maybe the web calls have something to do with the transformation of coordinates from a curved surface to a flat map. Alright, that could make the interpolation more accurate.
Today the geotagging was working fine again: more than 100 photos tagged. Hopefully the issue earlier this week was caused by temporary traffic or server problems.
I tried to prevent "too many map requests" from occurring, by using Google Maps for searching the right locations, and that worked OK. Thanks again G0apher!

Votes

Translate

Translate

Report

Report
Explorer ,
Dec 25, 2019 Dec 25, 2019

Copy link to clipboard

Copied

Still broken on v.9.1 of LR Classic - any idea when it might be fixed?

Votes

Translate

Translate

Report

Report
Explorer ,
Jan 13, 2020 Jan 13, 2020

Copy link to clipboard

Copied

Unbelievably a year on Adobe still haven't fixed this issue. Sure you can do a workaround by disabling Graphics Acceleration but then the rest of the app slows down. Lots of other customers report the same issue and I'm astounded they keep on ignoring it.

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Jan 13, 2020 Jan 13, 2020

Copy link to clipboard

Copied

Alan, I am going to port you to a new thread. The original issue was fixed in Lightroom 8.0 some time ago. 
Rikk Flohr - Customer Advocacy: Adobe Photography Products

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Jan 13, 2020 Jan 13, 2020

Copy link to clipboard

Copied

This appears to be a different issue than were originally posted.

Please reference the new conversation here: Lightroom Classic: Issue Placing Images in Map Module
Rikk Flohr - Customer Advocacy: Adobe Photography Products

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Jan 13, 2020 Jan 13, 2020

Copy link to clipboard

Copied

Please see new issue post here: https://feedback.photoshop.com/photoshop_family/topics/lightroom-classic-issue-placing-images-in-map...
Rikk Flohr - Customer Advocacy: Adobe Photography Products

Votes

Translate

Translate

Report

Report
Explorer ,
Jan 14, 2020 Jan 14, 2020

Copy link to clipboard

Copied

I've re read the original post here and it sounds like a pretty similar issue to me! Regardless both have been going on for many months and it's appalling Adobe still haven't fixed the issue.

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Jan 14, 2020 Jan 14, 2020

Copy link to clipboard

Copied

"Pretty Similar" and "The Same" are really two different things.  Regardless this thread is closed and the originally reported issue was fixed.

Since you are the only poster in the past 10 months I've moved you to a new thread where we need to collect complete system information and a detailed description of the problem you are experiencing. This needs to be treated as a new issue.

Please reply on the other thread. 

Thank you!
Rikk Flohr - Customer Advocacy: Adobe Photography Products

Votes

Translate

Translate

Report

Report
Explorer ,
Jan 14, 2020 Jan 14, 2020

Copy link to clipboard

Copied

LATEST
I find it incredibly depressing that Adobe seem to be going back to square one on an issue that so many customers have had for so long. It seems to be a stalling exercise and the technical support have been completely hopeless so far (I've spent too many hours on chat and the phone to them).  Hopefully someone from Adobe technical support will finally take it seriously.

Votes

Translate

Translate

Report

Report