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

  • 29
  • Problem
  • Updated 8 months ago
  • Acknowledged
  • (Edited)
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
Photo of Carlos Oliveras

Carlos Oliveras

  • 138 Posts
  • 32 Reply Likes

Posted 1 year ago

  • 29
Photo of CS Chua

CS Chua

  • 19 Posts
  • 5 Reply Likes
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. 
(Edited)
Photo of Carlos Oliveras

Carlos Oliveras

  • 130 Posts
  • 32 Reply Likes
I'm sorry but I can't see how your "Geotagging 101" relates to the issue I described.
Or were you describing an issue of your own, maybe?
Photo of CS Chua

CS Chua

  • 19 Posts
  • 5 Reply Likes
Nope I don't have any problems with the methods you are having problems with. I geotag 100% of my photos as well hence suggest other methods. I just completed geotagging over a 1000 photos travel shoot. However I see your problem was replicated by Adobe. Would be interested to know under what conditions does geotagging rendered ineffective and Adobe's recommendation.


Photo of Carlos Oliveras

Carlos Oliveras

  • 130 Posts
  • 32 Reply Likes
But you do have that offset problem, don't you? I'm not experiencing it (or at least I am not able to detect it visually).
On the other hand, did you geotag 1000 photos with 7.5 already? Man that's fast, I think it was released yesterday. Good work.

PS. FWIW, I'm using Windows 10. Might be an OS thing?
(Edited)
Photo of G0apher

G0apher, Employee

  • 81 Posts
  • 27 Reply Likes
Wow, CS Chua - great to hear your experience! Were you trying that with the new 7.5 update?
Photo of Philippe Coudé du Foresto

Philippe Coudé du Foresto

  • 57 Posts
  • 22 Reply Likes
A friend had the offset problem with LR 7.5 and Windows 10. A reinitialization of the LR preference fixed it (and as a bonus, improved the LR performance !).
Photo of G0apher

G0apher, Employee

  • 92 Posts
  • 28 Reply Likes
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.
Photo of Carlos Oliveras

Carlos Oliveras

  • 138 Posts
  • 32 Reply Likes
Hey GOapher, thanks for taking the time to reproduce this issue.

It is truly an inconvenience since, like I said, I geotag photos on a daily basis. Luckily, I don't need 7.5, so I can live with 7.4. 

I hope this gets fixed sooner than later, though.

Thanks again.
Photo of Carlos Oliveras

Carlos Oliveras

  • 138 Posts
  • 32 Reply Likes
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.
(Edited)
Photo of G0apher

G0apher, Employee

  • 92 Posts
  • 28 Reply Likes
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.

Photo of Carlos Oliveras

Carlos Oliveras

  • 138 Posts
  • 32 Reply Likes
Yes, I did get that scary message about the map Module (or at least the ability to display photos on the map) going away on november 30th 2018 , until Rikk Flohr gave a definite answer about the subject on this thread.

Still, I am not sure whether the Address Lookup service experienced any pause during this time. I did not pause it,  at least that I am aware of.

I will give a try to cleaning the preferences  when I can, but first I would need to update to 7.5 again (which for some reason, takes a while, same as updating any CC app), then if it doesn't work, roll back again to 7.4 and set my preferences again. So, I will have to set some time aside to try that. Also, since 7.5 is pretty new and (so far) no one else seems to complain about this issue, I would also like to wait and see if other people are experiencing this problem.

When I do so, I will let you know the results. Thanks for your attention to this matter.
(Edited)
Photo of Carlos Oliveras

Carlos Oliveras

  • 138 Posts
  • 32 Reply Likes
Well, an update before I thought...

The Address Lookup feature stopped working on my computer with LR 7.4 a while ago (?). Out of desperation, I updated again to 7.5, to see what happened this time around.

The first time I opened LR 7.5 right after this second update, I was (again) unable to geo-tag any photo (no dragging, no ctrl+clicking, no right click and "Add GPS coord."... Nothing). But this time, instead of trying with more photos, I quickly closed LR, and then I started it again. And now it is working! (Both geotagging and the Adress Lookup).

Of course, I already tried restarting the first time I updated. The only difference is that, on my first update to 7.5, I spent a while trying to put photos on the map (to no avail) before I finally tried restarting LR. It's as if insisting on this on the first run made the issue stick. Or maybe it's just coincidence.

Whatever the real reason, I just hope it stays like this. Thanks again for your help, GOapher!
(Edited)
Photo of Fred van Os

Fred van Os

  • 3 Posts
  • 3 Reply Likes
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.





Photo of Carlos Oliveras

Carlos Oliveras

  • 130 Posts
  • 32 Reply Likes
Hey Fred, just so you know, although I said it was solved, the next day this issue was happening again. But now I've realised that, by closing and restarting LR, eventually the map Module works again. Normally it takes 1 restart, 2 tops, and that's if the issue happens at all to begin with (now it only happens every now and then).

I guess it's another one of those quirks that appear with one update, and then go away with the next update. Or so I hope...

PS. I don't know if this has anything to do, but I also use 2 screens.
Photo of Fred van Os

Fred van Os

  • 3 Posts
  • 3 Reply Likes
Thanks for the answer. I will give it try.
Photo of john beardsworth

john beardsworth

  • 1236 Posts
  • 321 Reply Likes
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.
Photo of john beardsworth

john beardsworth

  • 1236 Posts
  • 321 Reply Likes
Is reverse geocoding enabled? Catalog Settings, Metadata tab, Look up City....

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


(Edited)
Photo of chrisstr

chrisstr

  • 1 Post
  • 0 Reply Likes
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]

Photo of Joop van den Eijnde

Joop van den Eijnde

  • 9 Posts
  • 3 Reply Likes
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.

Photo of Philippe Coudé du Foresto

Philippe Coudé du Foresto

  • 69 Posts
  • 25 Reply Likes
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

Photo of Carlos Oliveras

Carlos Oliveras

  • 138 Posts
  • 32 Reply Likes
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!
(Edited)
Photo of Philippe Coudé du Foresto

Philippe Coudé du Foresto

  • 69 Posts
  • 25 Reply Likes
I agree with Carlos, at least for  me, this problem appeared with the 7.5 upgrade, I didn't have it with 7.4.
Photo of Joop van den Eijnde

Joop van den Eijnde

  • 9 Posts
  • 3 Reply Likes
It seems silly to say, but it feels as if alternating the method of geotagging (change regularly between ctrl-click, right-click and drag) helps to make the geotagging work. I just placed about 30 geotags, with at most 1 to 3 retries. Also I noticed that one time I tried 3 times, I stopped, being disappointed. Then, after 5 seconds, the pin appeared after all. However, I'm sure it has not been "just" a delay issue in the past days.

In my LR forum thread johnrellis kindly referred me to a powerful plugin for LR (freeware) that can do geotagging. Didn't try it myself yet, but will do so if Adobe will not fix the present issue.
Photo of Magnus Svensson

Magnus Svensson

  • 4 Posts
  • 0 Reply Likes
Same problem for me too.

Windows 10
Core i7 7700K
32 Gb RAM
GTX 1080

Dual screen


Photo of Luc Perrin-Pelletier

Luc Perrin-Pelletier

  • 5 Posts
  • 0 Reply Likes
I have a similar problem :

Whenever I switch to the module or move the map, the label "Map is off line" appears for a while, then the map displays but not Always completely.

When I want to change the location of one or several photo(s) by moving the orange tab(s) on the map,

- often it does not take the move into account, just nothing happens.

- or it takes it into account the move, but assigns it to a neighboring photo :(,

- and sometime, for no apparent Reason, it works (switching to a different module, select different photos (do anything) and returning to the map module helps).

Version Lightroom Classic: 7.5 [ 1186149 ]

Licence: Creative Cloud
Paramètre de langue: fr
Système d'exploitation : Windows 10 - Home Premium Edition
Version : 10.0.17134
Architecture de l'application : x64
Architecture du système : x64
Nombre de processeurs logiques: 8
Vitesse du processeur : 2,8 Ghz
Mémoire intégrée : 32589,3 Mo
Mémoire réelle disponible pour Lightroom : 32589,3 Mo
Mémoire réelle utilisée par Lightroom : 7937,1 Mo (24,3%)
Mémoire virtuelle utilisée par Lightroom : 11781,1 Mo
Nombre d'objets GDI : 1701
Nombre d'objets utilisateur : 5099
Nombre de processus gérés : 7581
Taille de la mémoire cache : 2279,6Mo
Révision interne Camera Raw: 1001
Nombre maximal de liens utilisé par Camera Raw  : 5
Optimisation SIMD de Camera Raw : SSE2,AVX,AVX2
Mémoire virtuelle de Camera Raw: 1441Mo / 16294Mo (8%)
Mémoire réelle de Camera Raw: 1442Mo / 32589Mo (4%)
Paramètre PPP du système : 240 PPP (mode haute résolution)
Composition sur le Bureau activée: Oui
Photo of Joop van den Eijnde

Joop van den Eijnde

  • 9 Posts
  • 3 Reply Likes
Same thing as I reported, almost simultaneously!
Photo of Joop van den Eijnde

Joop van den Eijnde

  • 9 Posts
  • 3 Reply Likes
One more thing: I noticed the same erratic behaviour when moving pins on the map which are already there. Moving (dragging) the pins always works, but the GPS coordinates don't follow most of the times, they remain unchanged. This yields the strange situation that the pin is in the correct position, but the coordinates of the photo are not in sync. That can be seen by dragging the map elsewhere and then clicking the photo: it will center on the coordinates, not the pin.
Photo of Jaime Sanz

Jaime Sanz

  • 7 Posts
  • 3 Reply Likes
I have the same problem with 7.5. When I drag an image or a set of images into the map nothing happens. I have downgrade to 7.4 and it is working again

(Edited)
Photo of G0apher

G0apher, Employee

  • 92 Posts
  • 28 Reply Likes
Official Response
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!

Photo of Darren Aylward

Darren Aylward

  • 4 Posts
  • 0 Reply Likes
I too have been intermittently getting this issue since the latest update. Here is my system info in case of any correlation with other users...
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: 3.5 GHz
Built-in memory: 32720.1 MB
Real memory available to Lightroom: 32720.1 MB
Real memory used by Lightroom: 3421.5 MB (10.4%)
Virtual memory used by Lightroom: 3841.2 MB
GDI objects count: 667
USER objects count: 3096
Process handles count: 2356
Memory cache size: 4388.6MB
Internal Camera Raw revision: 1001
Maximum thread count used by Camera Raw: 5
Camera Raw SIMD optimization: SSE2,AVX,AVX2
Camera Raw virtual memory: 1547MB / 16360MB (9%)
Camera Raw real memory: 1548MB / 32720MB (4%)
System DPI setting: 96 DPI
Desktop composition enabled: Yes
Displays: 1) 1920x1080
Input types: Multitouch: No, Integrated touch: No, Integrated pen: No, External touch: No, External pen: No, Keyboard: No

Graphics Processor Info: 
DirectX: NVIDIA GeForce GTX 1060 6GB (24.21.13.9907)
No error messages have been experienced at any point.
Photo of Ian Gordon

Ian Gordon

  • 1 Post
  • 0 Reply Likes
I too am experiencing problems with the Map Module after the latest update. When I select an image or group of images and try to add GPS data to it the program intermittently fails to this . Everything works fine until I take the final option to add the GPS data then nothing happens. Ive tried single and multiple images and nearly every attempt has resulted in failure.
Photo of G0apher

G0apher, Employee

  • 92 Posts
  • 28 Reply Likes
Please try the same now and let us know if you are still facing any failures in geocoding. 

An API we were using was being rate-limited, causing intermittent failures in Lightroom Classic. It has now been addressed, and the failure should no longer occur.

Happy Geocoding!

Photo of Jaime Sanz

Jaime Sanz

  • 7 Posts
  • 3 Reply Likes
Hi G0apher,

I have upgraded back to 7.5 to try geocoding and still it is not working correctly. Some times it works, sometimes not, and when it works it is really slow and it seems that even that it has writen geodata into the metadata it does not refresh the map to show it has worked, but if you select a diferent image then it refresh the information.
Photo of Carlos Oliveras

Carlos Oliveras

  • 138 Posts
  • 32 Reply Likes
This morning I tried, and it was working 100% of the time. But of course, I didn't want to be overconfident, so, I decided to wait a little more.

And it looks like I did the right thing, because now, it's doing weird things again. It does work sometimes, then it stops working, then it works, then it doesn't, etc. As far as I can see, there's no rhyme or reason as to why it works or doesn't work.

Thanks for looking into this, please keep trying....
Photo of Joop van den Eijnde

Joop van den Eijnde

  • 9 Posts
  • 3 Reply Likes
Hi G0apher,
For me, too, it's still not working correctly. It could be that it has improved somewhat, sometimes it does the geotagging instantly, but on other occasions I have to try 3-6 times before the tag catches. Sometimes I try ctrl-click to no avail 6 times, then do right-click and "attach geotags" and it works at once. Or the other way around. Still erratic behaviour it seems.
What do you need the API for anyway? This looks like a local action: click on a local map, place the pin, and add the coordinates you clicked on to the photo(s). Only if you need address lookup, I can imagine you make a web call. But I switched that off.
Sorry, but it doesn't seem be solved yet.
Regards, Joop
Photo of Philippe Coudé du Foresto

Philippe Coudé du Foresto

  • 69 Posts
  • 25 Reply Likes
Just did a quick test with about 150 photos taken in several groups and all were pinned and geotagged correctly (although a bit slow with a group of 70 photos).
I tested my protocol (suppressing the coordinates) and I couldn't reproduce the problem.
So far it seems to work fine.
Photo of Carlos Oliveras

Carlos Oliveras

  • 138 Posts
  • 32 Reply Likes
For the last 24 hours, it's been working flawlessly for me (like it did before 7.5 was launched). I feel unsure about this though, since so many times it seemed to work, then it stopped working again.  But still, I think this is the longest "good streak" since 7.5 was released.

On a related note, I also feel like some kind of explanation is missing, and maybe we will never get it, but... if the LR Team is fixing this by upgrading the API limits, doesn't it mean they lowered or restricted them at some point, probably around the same time 7.5 was launched? If so, I wonder why they took such a poor decision.

Well, nevermind as long as this keeps on working. I hope more people will share their experience, to confirm this is fixed. But then again, if this Mangalick guy or his minions (because I am pretty sure he is the one behind all this mess) can alter the API rate at their whim 5 minutes after I post this message, then I guess we will never have a permanent solution.

Whatever the case, thank you again, GOapher, for your attention to this matter, and for keeping us posted in a timely manner. It's much appreciated.
(Edited)
Photo of G0apher

G0apher, Employee

  • 92 Posts
  • 28 Reply Likes
Official Response
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.
Photo of Darren Aylward

Darren Aylward

  • 4 Posts
  • 0 Reply Likes
I've been doing quite a few photographs this afternoon (singles and groups of photos) and although not an exhaustive test, everything seems to be working fine for me now.
Thank you for looking into this in such a timely manner.
Photo of Jaime Sanz

Jaime Sanz

  • 7 Posts
  • 3 Reply Likes
Hi,

I have tried some images and I can not see any diference, it works for some geocoding (15 or 20) very slow and after that it does not work anymore unless you restart the aplication.
Photo of Alan Robertson

Alan Robertson

  • 10 Posts
  • 2 Reply Likes
This is marked as being fixed but I'm afraid it very much is NOT fixed when I tried it just now.  No issues with tracklogs (presumably as data is being provided), but dragging and dropping individual items onto the map is painfully slow and >75% of the time doesn't work at all. I've tried restarting Lightroom but to no avail.

This is a key part of my workflow for photos and I trust this is being given priority as a fix.
Photo of G0apher

G0apher, Employee

  • 92 Posts
  • 28 Reply Likes
Sorry to hear that Alan.

Does it not work at all or only works slowly - while filling in the Location (City, State, Sublocation, Country) fields? Does it happen with single photos as well as multiple photos?
Photo of Alan Robertson

Alan Robertson

  • 10 Posts
  • 2 Reply Likes
I got there in the end, it was just extremely slow - I tried both multiple photos at once and one at a time.  I would repeatedly drag it onto the map then nothing would happen. Eventually after many minutes per photo it would seem to stick.  I'm not quite sure what you mean about filling in Location fields - I was just dragging and dropping onto the map.

As mentioned above the tracklog worked fine and allocated all the photos OK.

I've pasted system info above too.
Photo of Joop van den Eijnde

Joop van den Eijnde

  • 9 Posts
  • 3 Reply Likes
Hi G0apher,
I managed do some geotagging with 7.5 as well after your fix, on 2 different days. Single photos, multiple photos, with ctrl-click, right-click and drag, all in all a few dozen of photos have been geotagged. It worked flawlessly this time. Not a single one failed. Even the dragging of a  pin to a different location went first time right. I am pretty confident that the bug is fixed. In a few days I will do many more photos and report back again.

I understand that the API call over the internet is new in 7.5? Then it may very well explain why it went wrong. And still, after the fix, we should be aware that we will always be dependent on network traffic and a stable internet connection. Anyway, it appears to work now. Thanks very much for solving this, it's a big relief for me.
Best regards, Joop
Photo of Michael Eicher

Michael Eicher

  • 16 Posts
  • 12 Reply Likes
Unfortunately i have to report the following behavior:
Map Module seems to work fine, until i switch to another Module - i.e the Library to select another Folder - Going then back to the Map module does what is described here: no entries possible by dragging a photo to the map.
Restarting Lightroom brings me back to the map module and everything seems to be OK, so long i do not switch again to an other Module. After that die Map module stops functioning again.

Sometimes i watched Problems when updating a position: ie. dragging the photo to a new position. This fails until i delete the Geo data by hitting the delete button with the map icon selected. After that i can drag the image to a new position. I think to remember, that this was also possible in the past.

Beside that i have noticed, that sometimes an updated position flips back to the position it was before. (on the map) To stop that a restart of Lightroom is necessary.  Looks like the new position is not written to the database.

So many failures at an update that should be mostly a bug-fix.
I am running win 10 prof. latest

regards 
mikel


Photo of Alan Robertson

Alan Robertson

  • 10 Posts
  • 2 Reply Likes
Exactly my experience - clearly not sorted!
Photo of G0apher

G0apher, Employee

  • 81 Posts
  • 27 Reply Likes
I tried the same workflow, and could not see any issue with the Map module. Could you share a screen-recording of Lightroom when this behaviour presents?

Also, kindly share your System Info (Help -> System Info) details.

Thanks for the details, as we try and investigate this issue further.
Photo of Alan Robertson

Alan Robertson

  • 10 Posts
  • 2 Reply Likes
System info below.  I don't have any screen recording software installed at present, anything you'd recommend?  It did eventually tag things but took minutes per photo.

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: 4
Processor speed: 3.7 GHz
Built-in memory: 16257.5 MB
Real memory available to Lightroom: 16257.5 MB
Real memory used by Lightroom: 788.0 MB (4.8%)
Virtual memory used by Lightroom: 865.1 MB
GDI objects count: 649
USER objects count: 2403
Process handles count: 2853
Memory cache size: 239.6MB
Internal Camera Raw revision: 1001
Maximum thread count used by Camera Raw: 3
Camera Raw SIMD optimization: SSE2,AVX,AVX2
Camera Raw virtual memory: 87MB / 8128MB (1%)
Camera Raw real memory: 87MB / 16257MB (0%)
System DPI setting: 96 DPI
Desktop composition enabled: Yes
Displays: 1) 1280x1024, 2) 1920x1080
Input types: Multitouch: No, Integrated touch: No, Integrated pen: No, External touch: No, External pen: No, Keyboard: No

Graphics Processor Info: 
DirectX: Intel(R) HD Graphics 630 (24.20.100.6025)



Application folder: C:\Program Files\Adobe\Adobe Lightroom Classic CC
Library Path: C:\Users\User\Dropbox\Lightroom\Lightroom Catalog\Lightroom Catalog.lrcat
Settings Folder: C:\Users\User\AppData\Roaming\Adobe\Lightroom

Installed Plugins: 
1) AdobeStock
2) Canon Tether Plugin
3) Facebook
4) Flickr
5) jf Extended Search
6) Nikon Tether Plugin

Config.lua flags: None

Adapter #1: Vendor : 8086
Device : 5912
Subsystem : 86941043
Revision : 4
Video Memory : 128
Adapter #2: Vendor : 1414
Device : 8c
Subsystem : 0
Revision : 0
Video Memory : 0
AudioDeviceIOBlockSize: 1024
AudioDeviceName: Speakers (Realtek High Definition Audio)
AudioDeviceNumberOfChannels: 2
AudioDeviceSampleRate: 48000
Build: Uninitialized
Direct2DEnabled: false
GL_ACCUM_ALPHA_BITS: 16
GL_ACCUM_BLUE_BITS: 16
GL_ACCUM_GREEN_BITS: 16
GL_ACCUM_RED_BITS: 16
GL_ALPHA_BITS: 8
GL_BLUE_BITS: 8
GL_DEPTH_BITS: 24
GL_GREEN_BITS: 8
GL_MAX_3D_TEXTURE_SIZE: 2048
GL_MAX_TEXTURE_SIZE: 16384
GL_MAX_TEXTURE_UNITS: 8
GL_MAX_VIEWPORT_DIMS: 16384,16384
GL_RED_BITS: 8
GL_RENDERER: Intel(R) HD Graphics 630
GL_SHADING_LANGUAGE_VERSION: 4.50 - Build 24.20.100.6025
GL_STENCIL_BITS: 8
GL_VENDOR: Intel
GL_VERSION: 4.5.0 - Build 24.20.100.6025
GPUDeviceEnabled: false
OGLEnabled: true
GL_EXTENSIONS: GL_3DFX_texture_compression_FXT1 GL_AMD_depth_clamp_separate GL_AMD_vertex_shader_layer GL_AMD_vertex_shader_viewport_index GL_ARB_ES2_compatibility GL_ARB_ES3_1_compatibility GL_ARB_ES3_compatibility GL_ARB_arrays_of_arrays GL_ARB_base_instance GL_ARB_bindless_texture GL_ARB_blend_func_extended GL_ARB_buffer_storage GL_ARB_cl_event GL_ARB_clear_buffer_object GL_ARB_clear_texture GL_ARB_clip_control GL_ARB_color_buffer_float GL_ARB_compatibility GL_ARB_compressed_texture_pixel_storage GL_ARB_compute_shader GL_ARB_conditional_render_inverted GL_ARB_conservative_depth GL_ARB_copy_buffer GL_ARB_copy_image GL_ARB_cull_distance GL_ARB_debug_output GL_ARB_depth_buffer_float GL_ARB_depth_clamp GL_ARB_depth_texture GL_ARB_derivative_control GL_ARB_direct_state_access GL_ARB_draw_buffers GL_ARB_draw_buffers_blend GL_ARB_draw_elements_base_vertex GL_ARB_draw_indirect GL_ARB_draw_instanced GL_ARB_enhanced_layouts GL_ARB_explicit_attrib_location GL_ARB_explicit_uniform_location GL_ARB_fragment_coord_conventions GL_ARB_fragment_layer_viewport GL_ARB_fragment_program GL_ARB_fragment_program_shadow GL_ARB_fragment_shader GL_ARB_fragment_shader_interlock GL_ARB_framebuffer_no_attachments GL_ARB_framebuffer_object GL_ARB_framebuffer_sRGB GL_ARB_geometry_shader4 GL_ARB_get_program_binary GL_ARB_get_texture_sub_image GL_ARB_gpu_shader5 GL_ARB_gpu_shader_fp64 GL_ARB_half_float_pixel GL_ARB_half_float_vertex GL_ARB_indirect_parameters GL_ARB_instanced_arrays GL_ARB_internalformat_query GL_ARB_internalformat_query2 GL_ARB_invalidate_subdata GL_ARB_map_buffer_alignment GL_ARB_map_buffer_range GL_ARB_multi_bind GL_ARB_multi_draw_indirect GL_ARB_multisample GL_ARB_multitexture GL_ARB_occlusion_query GL_ARB_occlusion_query2 GL_ARB_pixel_buffer_object GL_ARB_point_parameters GL_ARB_point_sprite GL_ARB_polygon_offset_clamp GL_ARB_post_depth_coverage GL_ARB_program_interface_query GL_ARB_provoking_vertex GL_ARB_query_buffer_object GL_ARB_robust_buffer_access_behavior GL_ARB_robustness GL_ARB_robustness_isolation GL_ARB_sample_shading GL_ARB_sampler_objects GL_ARB_seamless_cube_map GL_ARB_seamless_cubemap_per_texture GL_ARB_separate_shader_objects GL_ARB_shader_atomic_counter_ops GL_ARB_shader_atomic_counters GL_ARB_shader_bit_encoding GL_ARB_shader_draw_parameters GL_ARB_shader_group_vote GL_ARB_shader_image_load_store GL_ARB_shader_image_size GL_ARB_shader_objects GL_ARB_shader_precision GL_ARB_shader_stencil_export GL_ARB_shader_storage_buffer_object GL_ARB_shader_subroutine GL_ARB_shader_texture_image_samples GL_ARB_shading_language_100 GL_ARB_shading_language_420pack GL_ARB_shading_language_packing GL_ARB_shadow GL_ARB_stencil_texturing GL_ARB_sync GL_ARB_tessellation_shader GL_ARB_texture_barrier GL_ARB_texture_border_clamp GL_ARB_texture_buffer_object GL_ARB_texture_buffer_object_rgb32 GL_ARB_texture_buffer_range GL_ARB_texture_compression GL_ARB_texture_compression_bptc GL_ARB_texture_compression_rgtc GL_ARB_texture_cube_map GL_ARB_texture_cube_map_array GL_ARB_texture_env_add GL_ARB_texture_env_combine GL_ARB_texture_env_crossbar GL_ARB_texture_env_dot3 GL_ARB_texture_float GL_ARB_texture_gather GL_ARB_texture_mirror_clamp_to_edge GL_ARB_texture_mirrored_repeat GL_ARB_texture_multisample GL_ARB_texture_non_power_of_two GL_ARB_texture_query_levels GL_ARB_texture_query_lod GL_ARB_texture_rectangle GL_ARB_texture_rg GL_ARB_texture_rgb10_a2ui GL_ARB_texture_stencil8 GL_ARB_texture_storage GL_ARB_texture_storage_multisample GL_ARB_texture_swizzle GL_ARB_texture_view GL_ARB_timer_query GL_ARB_transform_feedback2 GL_ARB_transform_feedback3 GL_ARB_transform_feedback_instanced GL_ARB_transpose_matrix GL_ARB_uniform_buffer_object GL_ARB_vertex_array_bgra GL_ARB_vertex_array_object GL_ARB_vertex_attrib_64bit GL_ARB_vertex_attrib_binding GL_ARB_vertex_buffer_object GL_ARB_vertex_program GL_ARB_vertex_shader GL_ARB_vertex_type_10f_11f_11f_rev GL_ARB_vertex_type_2_10_10_10_rev GL_ARB_viewport_array GL_ARB_window_pos GL_ATI_separate_stencil GL_EXT_abgr GL_EXT_bgra GL_EXT_blend_color GL_EXT_blend_equation_separate GL_EXT_blend_func_separate GL_EXT_blend_minmax GL_EXT_blend_subtract GL_EXT_clip_volume_hint GL_EXT_compiled_vertex_array GL_EXT_direct_state_access GL_EXT_draw_buffers2 GL_EXT_draw_range_elements GL_EXT_fog_coord GL_EXT_framebuffer_blit GL_EXT_framebuffer_multisample GL_EXT_framebuffer_object GL_EXT_geometry_shader4 GL_EXT_gpu_program_parameters GL_EXT_gpu_shader4 GL_EXT_multi_draw_arrays GL_EXT_packed_depth_stencil GL_EXT_packed_float GL_EXT_packed_pixels GL_EXT_polygon_offset_clamp GL_EXT_rescale_normal GL_EXT_secondary_color GL_EXT_separate_specular_color GL_EXT_shader_framebuffer_fetch GL_EXT_shader_integer_mix GL_EXT_shadow_funcs GL_EXT_stencil_two_side GL_EXT_stencil_wrap GL_EXT_texture3D GL_EXT_texture_array GL_EXT_texture_compression_s3tc GL_EXT_texture_edge_clamp GL_EXT_texture_env_add GL_EXT_texture_env_combine GL_EXT_texture_filter_anisotropic GL_EXT_texture_integer GL_EXT_texture_lod_bias GL_EXT_texture_rectangle GL_EXT_texture_sRGB GL_EXT_texture_sRGB_decode GL_EXT_texture_shared_exponent GL_EXT_texture_snorm GL_EXT_texture_storage GL_EXT_texture_swizzle GL_EXT_timer_query GL_EXT_transform_feedback GL_IBM_texture_mirrored_repeat GL_INTEL_conservative_rasterization GL_INTEL_fragment_shader_ordering GL_INTEL_framebuffer_CMAA GL_INTEL_map_texture GL_INTEL_multi_rate_fragment_shader GL_INTEL_performance_query GL_KHR_blend_equation_advanced GL_KHR_blend_equation_advanced_coherent GL_KHR_context_flush_control GL_KHR_debug GL_KHR_texture_compression_astc_hdr GL_KHR_texture_compression_astc_ldr GL_NV_blend_square GL_NV_conditional_render GL_NV_primitive_restart GL_NV_texgen_reflection GL_SGIS_generate_mipmap GL_SGIS_texture_edge_clamp GL_SGIS_texture_lod GL_SUN_multi_draw_arrays GL_WIN_swap_hint WGL_EXT_swap_control
Photo of G0apher

G0apher, Employee

  • 81 Posts
  • 27 Reply Likes
Thanks for the details Alan - you could try the Windows Game Bar (hit Windows Key + G) that is available on Windows 10 to record screen contents as a video. Please share a recording that details your actions for tagging photos onto the Map, as well as switching to Library Mode and back. You could upload the same on any public share, and share the link here.
Photo of Alan Robertson

Alan Robertson

  • 10 Posts
  • 2 Reply Likes
I will do next time it happens - seems to be behaving itself this evening!
Photo of Alan Robertson

Alan Robertson

  • 10 Posts
  • 2 Reply Likes
OK now having the issue again, this time on my laptop.  Win + G doesn't so anything on my machine but behaviour is exactly as described by many others in this thread - drag photos onto map and nothing happens.  Randomly after switching to/from map mode it will sometimes tag them, but not reliably.
Photo of Joop van den Eijnde

Joop van den Eijnde

  • 9 Posts
  • 3 Reply Likes
Since the fix (upgrading the API limits) I have finished geotagging my holiday photos. I can report that I didn't have a single failure with any of over 150 photos any more. Single photos, multiple selections, 3 types of adding geotags, dragging a pin elsewhere, everything works fine for me. I hope the behaviour will remain like this, even after the next update and also when many more users will try to use the API for geotagging with version 7.5 and up.
I don't experience the behaviour that Michael Eicher reports about switching to other modules. I switch between Map and Library regularly and it makes no difference for me.
Regards, Joop