Skip to main content
corama.mx
Known Participant
May 28, 2024

P: Location/GPS data lost after updating to 13.3

  • May 28, 2024
  • 21 replies
  • 5515 views

Since updating to 13.3, I am having several issues.

First, almost half of the location data of my 40K catalog (country, city, state, etc.) has been either erased or changed to a variant like México/Mexico. GPS data was lost for 3K images. LR on the cloud has the same missing/wrong data. If I correct them in LR Classic, it reverts to the wrong one.

Then it became very sluggish, especially when metadata reading/writing is involved like rating, library filtering, adding keywords, etc. When selecting Lights out mode, it does not work until I rate or edit a photo. Before this version it was instantaneous. Switching to develop mode takes about 3 seconds (it was less than 1 before) and advancing to next image takes 2-3 seconds as well, it does not matter if images are RAW or JPG.

I already stopped syncing, optimize the catalog, increased cache to 99GB, deleted sync files, deleted previews, and generated them again, reset preferences, uninstalled, and installed again, removed presets, even tried a new catalog. Nothing seems to work.

I noted as well that I have 1.5K stubborn images that I can’t save the metadata manually to disk. As soon as it “saves” it, it shows “The metadata for this photo has been changed in lightroom, save the changes to disk?”.

I have paused Address Lookup, Face Detection and write to xmp. Generate Previews in Parallel is checked. Use of graphic processor is on Auto. I tried all other modes with no change in performance.

All images are on a samsung T7 SSD attached on USB-C. The catalog and cache are on a mac studio’s internal SSD, M1 Max, 64 GB of ram, runing on sonoma 14.5. All updates for the OS and any app installed are up to date. Images are displayed on a Apple Studio Display. all drives have plenty of free space and there is enough RAM available, no swap. I note that for any action I do in LR Classic, like edit a photo or switching modules, etc… all cores go up to 90-100% (specially when generating previews) making my machine OS sluggish and all apps become unresponsive.

Any suggestion to fix this behavior will be greatly appreciated.

This topic has been closed for replies.

21 replies

Mohit Goyal
Community Manager
Community Manager
June 4, 2024

Hi all,

 

We are happy to announce the release of Lightroom Classic 13.3.1, which incorporates the fix for this particular problem. To see the list of all fixed issues, click here

 

To update Lightroom Classic to 13.3.1, click "Update" in the Creative Cloud desktop app next to Lightroom Classic. More detailed instructions for updating

 

Let us know if the update resolves the problem for those affected, and share your feedback.

 

Thanks,

Mohit

Victoria Bampton LR Queen
Community Expert
Community Expert
June 1, 2024

@el*bandido Adobe takes it very seriously too. The current recommendation is to keep hold of your 13.2 catalog while they figure out the best way forward to ensure you don't lose that data. One option I've used in the past was a plug-in that could transfer data between catalogs via csv file, so there definitely are options that don't involve losing the work you've done in 13.3. We just need to give them a short while to ensure they've considered the options properly before moving forward. 

Victoria - The Lightroom Queen
el*bandido
Participant
June 1, 2024

I experience the same problem:

  • Only photos synced to the Cloud are affected
  • Country/City/State fields (which I entered manually) are either empty or changed/translated; Sublocation field seems to be unaffected
  • All synced photos have an extra "From Lr mobile" entry in the Develop history (although I rarely do modification from Lr mobile) so they all show up in my library with the "Photo has Develop adjustments" icon
  • For some photo's this "From Lr mobile" entry reverted settings in Develop

 

This kind of data loss is pretty serious. I hope it gets fixed soon.

 

I still have a v13.2 catalog backup, but will I loose the work I did in Lightroom since the upgrade to 13.3? 

Jeff A. Goulden
Inspiring
May 30, 2024

I'm able to reconstruct my missing location data without needing my pre-conversion catalog.  I did not see that I lost any GPS data like other users have reported.  My main concern right now is that just about everything I do in Lightroom seems slower after upgrading.  I think someone else reported the same problem.

Rikk Flohr_Photography
Community Manager
Community Manager
May 30, 2024

The team has discovered the issue and is working on a fix for the next release. 
Please hold onto your 13.2 pre-update catalogs until we can advise on remediation.

If you need the data immediately, you can use Reverse Geocoding to populate the fields from the GPS data. 

 

Thank you for your patience.


Please stand by. 

 

Rikk Flohr: Adobe Photography Org
Victoria Bampton LR Queen
Community Expert
Community Expert
May 30, 2024

@Rikk Flohr: Inactive Last time I checked, the text location fields other than GPS co-ordinates weren't supposed to sync Cloud <> Classic. They now are (with or without XMP). City/State/Country that were reverse-geocoded by the cloud are becoming confirmed locations in Classic. I haven't run down all the permutations, but this is definitely buggy.

Victoria - The Lightroom Queen
Jeff A. Goulden
Inspiring
May 29, 2024

Here's something to consider before upgrading to Lightroom Classic V13.3.  This upgrade requires conversion of the Lightroom catalog.  After converting my catalog, I found that 384 of my 16,753 photos no longer contained either sublocation, city, state or country (or some combination thereof) in the metadata.  While this is not catastrophic, it is extremely annoying that I have to go in and fix the 384 random images.

johnrellis
Legend
May 30, 2024

I recommend you zip up the .lrcat file of the old version of the catalog, upload it to Dropbox, Google Drive, or similar, and hold on to the sharing link. Hopefully, Adobe will offer to grab a copy of it and verify they can reproduce the problem.

Victoria Bampton LR Queen
Community Expert
Community Expert
May 29, 2024

For clarity, is it the Location text fields (shown in red) or the GPS data (shown in blue) that are going missing?

And how has that data got there initially? From the camera? By dropping on the map in Classic? or...?

Victoria - The Lightroom Queen
Inspiring
May 29, 2024

In my case the text fields in red are affected. 'Sublocation' is not affected, only City, State and Country/Region. I don't use ISO Country Code. The data either came from the camera (mobile phone) or was added manually.

Victoria Bampton LR Queen
Community Expert
Community Expert
May 29, 2024

Do you have GPS coordinates for those images or just the text fields?

Victoria - The Lightroom Queen
Rikk Flohr_Photography
Community Manager
Community Manager
May 29, 2024

@corama.mx  @CS Fotografie 

Are the affected images synced to the Cloud, local only, a mixture?

Rikk Flohr: Adobe Photography Org
Inspiring
May 29, 2024

In my case they are synced to the cloud. Currently the status of images without Location data has risen to more than 54'000. It seems that LR is constantly overwriting existing XMP-Data for no obvious reason.

 

Inspiring
May 29, 2024

I have a similar problem: When updating to 13.3. sync starts, deleting all location information. I have a catalog with some 90'000 pictures. After 24 hours some 78'000 pictures have lost GPS information. I restored to the previous catalog V13. All metadata seems to be correct again, 100% of my pictures have location information. 

When migrating to 13.3. again, I have now some 24'000 pictures with missing location information. 

I'm on a Mac Sonoma 14.5. Intel Core i9, 32GB RAM

Legend
May 29, 2024

As there are now two people in this thread reporting lost GPS info when syncing, I think this may be an actual bug. Or an insect. Or an arachnid. But anyway, the best thing you can do is to write up instructions that allow someone to repeat what you are doing step-by-step (in other words, lots of detail, and leaving nothing out), and then report this as a bug here on the Adobe Community. Don't simply copy and paste what you have written here, that will be rejected. Put some effort into the description so people can repeat the steps.