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

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!

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.

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.

Select multiple photos from the flimstrip.  Left Click the selection. You must wait for the appearance of a cluster icon to appear before you drag the cursor to the map. When you drop the photo to the map the position is offset south-east.  Move the cursor to the position you want to tag and right click to populate the GPS coords to the selected photos.

How long you need to wait for the appearance of the cluster icon to appear depends on your system performance and how many photos you selected. 

Hi Carlos, sorry for the inconvenience and thanks for bringing this to our notice.

I am able to see the issue and investigating further to identify a pattern.

I have updated LR Classic on a different computer (this one was updated from 7.3.1 straight to 7.5), and strangely enough, the same issue happens, albeit not so often. Matter of fact, sometimes it works flawlessly for several photos in a row, then it won't work with one or two photos, then it will work again (while on my main computer it failed most of the time). Still can't find a reason or a pattern for this erratic behavior.

The first lines in system info for this other computer where it works better (but still not 100% as it did before the update):

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

Thanks.

Thanks, Carlos for more details.

While on the previous version, and using the Map module, were you prompted with any information regarding the Map feature and its availability? Could you also please confirm that the Address Lookup service was never paused/restarted while Lightroom was running?

While I was able to reproduce the problem and investigating it, I cleaned the preferences and restarted Lightroom. Now geo-tagging images, including drag-drop of photos, and Ctrl+Click, works as expected without any issues. I was wondering if you could also try that to see if it starts working on your main machine. Let us know when you try that.

I will keep digging for this issue again on my workdesk. Thanks for your patience.

On a mac, I have the same problems. in version 7.5 I cannot place my photo's on the map to geotag them.

Lightroom Classic version: 7.5 [ 1186149 ]License: Creative Cloud
Language setting: en
Operating system: Mac OS 10
Version: 10.11.6 [15G18013]
Application architecture: x64
Logical processor count: 16
Processor speed: 2,2 GHz
Built-in memory: 16.384,0 MB
Real memory available to Lightroom: 16.384,0 MB
Real memory used by Lightroom: 863,3 MB (5,2%)

I have reset the pref. But that didn't make a difference. Als. I use 2 screens. On one the map, on the other a grid-view, from where I drag the photos to the map. I makes no difference when I use the filmstrip at the bottom.  Adreslookup is running.

I also see this and have been unable to identify a pattern. There was an API change in 7.4, and I suspect this is the underlying issue.

Is reverse geocoding enabled? Catalog Settings, Metadata tab, Look up City....

I have it disabled, and suspect it may be relevant to the problem.

Same for me on a Mac.

But I discovered that when the tagging stops to work after like 5 photos, then you wait for a few minutes, it works again for a few photos before stopping to work again and so on.

Restart Lightroom, restart computer, etc. - no matter what I do, it's always the same behavior after a while.

Lightroom Classic-Version: 7.5 [ 1186149 ]
Lizenz: Creative Cloud
Spracheinstellung: de-DE
Betriebssystem: Mac OS 10
Version: 10.13.6 [17G65]

I have the same problem, also reported it in the LR Classic forum.
Whatever method I try to place geotags in map mode, ctrl-click, right click or drag, it takes many trials before the tag is actually placed, maybe 3, 5, or even 10 or 15 times. Single photo or a selection doesn't matter. It sometimes helps to restart LR, then it works a little better for the first photos to be tagged.

I attached my (wired optical) mouse directly to the pc instead of a hub, didn't make any difference. I don't have mouse issues in any other app btw. I tried different metadata presets on the info panel on the right. Doesn't make any difference. Switched of the automatic address lookup in the preferences (reverse geotagging), didn't help either. Could this be a memory issue (8 GB)? Or does geotagging require interaction with the Adobe servers (which may be slow)?

I don't consider this issue to be solved, as it says in the header of this thread. If it is not solved in the next few days I will be forced to downgrade to version 7.4. I never had any problems with that version.

My system info is:

Lightroom Classic-versie: 7.5 [ 1186149 ]
Licentie: Creative Cloud
Taalinstelling: nl
Besturingssysteem: Windows 10 - Business Edition
Versie: 10.0.17134
Toepassingsarchitectuur: x64
Systeemarchitectuur: x64
Aantal logische processors: 8
Processorsnelheid: 2,6 GHz
Ingebouwd geheugen: 8183,1 MB
Beschikbaar fysiek geheugen voor Lightroom: 8183,1 MB
Fysiek geheugen gebruikt door Lightroom: 1570,0 MB (19,1%)
Virtueel geheugen gebruikt door Lightroom: 1537,3 MB
Aantal GDI-objecten: 752
Aantal gebruikersobjecten: 2780
Aantal proceshandelingen: 2206
Cachegeheugengrootte: 7,0MB
Interne Camera Raw-revisie: 1001
Maximumaantal door Camera Raw gebruikte threads: 5
Camera Raw SIMD-optimalisatie: SSE2
Virtueel geheugen Camera Raw: 738MB / 4091MB (18%)
Fysiek geheugen Camera Raw: 739MB / 8183MB (9%)
Dpi-instelling systeem: 96 dpi
Bureaubladcompositie ingeschakeld: Ja
Schermen: 1) 1920x1080, 2) 1280x1024
Invoertypen: Multi-aanraking: Nee, Geïntegreerde aanraking: Nee, Geïntegreerde pen: Nee, Externe aanraking: Nee, Externe pen: Nee, Toetsenbord: Nee

Please let this be fixed soon, it is very frustrating and costs me too much time to manage my photo collection.

I also get this problem. I'm abble to make it happen usthe following sequence :

1. Go the map module
2. Select a group of photo that are already geotagged
3. Suppress the GPS coordinates of these photos

Now, if I drag a group of photos (or even a single photo) over the map, LR won't set the position.

Notes :
I had the map message before ugrading to 7.5 (from 7.4)
I've reinitialized the LR préférences, it didn't fix the problem (however it improved the LR performances !)

>>>
Version Lightroom Classic: 7.5 [ 1186149 ]
Licence: Creative Cloud
Paramètre de langue: fr
Système d'exploitation : Windows 7  - Ultimate Edition
Version : 6.1.7601
Architecture de l'application : x64
Architecture du système : x64
Nombre de processeurs logiques: 8
Vitesse du processeur : 3,4 Ghz
Mémoire intégrée : 16351,1 Mo
Mémoire réelle disponible pour Lightroom : 16351,1 Mo
Mémoire réelle utilisée par Lightroom : 1469,2 Mo (8,9%)
Mémoire virtuelle utilisée par Lightroom : 1536,9 Mo
Nombre d'objets GDI : 830
Nombre d'objets utilisateur : 2222
Nombre de processus gérés : 1747
Taille de la mémoire cache : 337,9Mo
Révision interne Camera Raw: 1001
Nombre maximal de liens utilisé par Camera Raw  : 5
Optimisation SIMD de Camera Raw : SSE2,AVX
Mémoire virtuelle de Camera Raw: 615Mo / 8175Mo (7%)
Mémoire réelle de Camera Raw: 616Mo / 16351Mo (3%)
Paramètre PPP du système : 96 PPP
Composition sur le Bureau activée: Oui
Affichages : 1) 2560x1440
Types d'entrée: Tactile multipoint : Non, Tactile intégré : Non, Plume intégrée : Non, Tactile externe : Non, Plume externe : Non, Clavier : Non

Informations relatives au processeur graphique :
OpenGL: GeForce GTX 1060 6GB/PCIe/SSE2

Check OpenGL support: Passed
Vendor: NVIDIA Corporation
Version: 3.3.0 NVIDIA 397.64
Renderer: GeForce GTX 1060 6GB/PCIe/SSE2
LanguageVersion: 3.30 NVIDIA via Cg compiler
Total Video Memory: 6144 MB


Dossier de l'application : C:\Program Files\Adobe\Adobe Lightroom Classic CC
Chemin d'accès à la bibliothèque : C:\Workfiles\Catalogue\GlobalCat\GlobalCat-LR.lrcat
Dossier des paramètres : C:\Users\philippe\AppData\Roaming\Adobe\Lightroom

Modules installés :
1) Adobe Stock
2) Facebook
3) Flickr
4) HDR Efex Pro 2
5) Module externe de prise de vue en mode connecté Canon
6) Module externe de prise de vue en mode connecté Nikon

Marqueurs Config.lua: None

Adaptateur n° 1: Fournisseur : 10de
    Appareil : 1c03
    So

John Beardsworth: I do have both of those options (reverse address lookup) checked. And while the API change could indeed be the root cause, I'm pretty sure that the trigger was the 7.5 update. Geotagging was working flawlesssly with 7.4 .

Joop van den Eijnde: I have 16 GB and still I'm experiencing this problem. It's not a performance issue.

The issue was marked as "solved" when it was just me complaining and it looked like it was working fine, so I said "hey it's fixed" (but I was wrong - the issue came back later). 

But now that more people have me-too'ed and posted since, I agree that this thread should be set back to "acknowledged" or something neutral. Otherwise I guess Adobe's engineers won't have a look at it.

Please G0apher , could you do that for us? Thanks!

I agree with Carlos, at least for  me, this problem appeared with the 7.5 upgrade, I didn't have it with 7.4.