Known Participant

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

Forum|Forum|7 years ago
August 22, 2018
116 replies
2481 views

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

This topic has been closed for replies.

Show previous replies

alanjr_uk

Inspiring

Exactly my experience - clearly not sorted!

alanjr_uk

Inspiring

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.

J

joopvde

Known Participant

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

F

FeedbackCommunityMember

Inspiring

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

J

joopvde

Known Participant

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

J

jsanzgar

Participating Frequently

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.

DarrenA

Participant

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.

Carlos_OliverasAuthor

Known Participant

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.

Lauca

Participating Frequently

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.

G

Goapher

Adobe Employee

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.

Show more replies

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded