Lightroom Classic 9.2: LR will not sync file saved by PS

  • 1
  • Problem
  • Updated 1 month ago
  • (Edited)
1. From LR library, select an image and "Open in Photoshop"
2. In PS, make changes then "Save As" into a different folder to the original file (psd/tiff both affected)
3. Close the file in PS and return to LR.
4. The updated file does not display in LR in the selected folder, but a file manager will confirm that it does exist there. If you right click the folder in LR and select "Synchronise folder..." the sync dialog shows 1 new image ready for import and the Import window shows the new image but greyed out and the hover-over text says that it has already been imported. However, if you search the catalog it is not found.

The only way to get the new file into the catalog is to close LR, move the file externally to another folder then sync that folder. Once re-synchronised, the original destination folder does not show a duplicate image or report a problem.
Photo of Geoff Baylis

Geoff Baylis

  • 6 Posts
  • 1 Reply Like

Posted 1 month ago

  • 1
Photo of Ruurd van Dijk

Ruurd van Dijk

  • 50 Posts
  • 12 Reply Likes
You need to do a 'Save' and NOT a 'Save as' in Photoshop. Otherwise Lightroom can't find your file!
Photo of Jerry Syder

Jerry Syder

  • 413 Posts
  • 188 Reply Likes
I believe the OP is specifically referring to the Sync issue. I've seen this reported before and I think it's a bug. 
Photo of Robert Somrak

Robert Somrak, Champion

  • 549 Posts
  • 184 Reply Likes
Ruurd

Using Lr9.2 and macOS 10.14.6 I can do a "Save As" to a different folder and Lightroom will happily automatically import it after doing the "Edit In".   This behavior changed from requiring "Save" awhile back.
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 5513 Posts
  • 2200 Reply Likes
If you go to All Photographs, can you confirm it's not actually in the catalog somewhere? There's a scenario where Lightroom sees the file as imported at a different path, so it would be worth ruling that out.
Photo of Geoff Baylis

Geoff Baylis

  • 6 Posts
  • 1 Reply Like
Hi Victoria...this is getting weird! Having looked in All Photographs, the image is there although if I searched for the file name it wasn't found. However, what I have discovered is that LR seems to be creating phantom network paths for the data which is on a QNAP NAS drive.

Somehow it seems to be differentiating between \\Qnap453\qnap\ (which is the primary path to my image folders) and \\Qnap453\QNAP\ which it creates when I "save as" from PS...sometimes!

If I Sync the \\Qnap453\qnap\ version of the folder, the file can be seen, but is greyed out.
If I Sync the new \\Qnap453\QNAP\ version of the same folder, the file can be successfully imported but remains in the LR catalog in its parallel universe. In File Manager I can see that there is only ONE version of the folder with all files.

I haven't worked out yet exactly under which circumstances this happens, but with my eyeballs spinning, I'll carry on tomorrow and report back.

BTW I'm using the very latest LR, PS and Win 10 Home 64bit.


Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 5513 Posts
  • 2200 Reply Likes
Bingo, that’s what I suspected. It’s essentially a variation on this issue: https://www.lightroomqueen.com/capitalization-catalog-error/ 

If you import a photo through the normal import dialog, which one does it end up in?
Photo of Geoff Baylis

Geoff Baylis

  • 6 Posts
  • 1 Reply Like
I imported an image from the Desktop and used the standard Import folder selection dialog to select "2020 LR to PS test 2" as the destination...and I now have a third variant. The destination dialog doesn't see the path variants and interestingly the Source folder list doesn't seem to recognise them either.


Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 5513 Posts
  • 2200 Reply Likes
Follow the instructions in that blog post to set them all to a different drive and back again, and that should hopefully do the trick.
Photo of Geoff Baylis

Geoff Baylis

  • 6 Posts
  • 1 Reply Like
Yes, your blog explains how to fix it once it is in the incorrect state (which does work), but not how to stop it happening again.

I cleared the various test folder from the system then started testing again.

One thing that I immediately noticed is that the Import dialog's Source and Destination file picker windows don't necessarily show the same network path naming:



There was no import between these two screen shots, I just went from setting the source to the destination as is normal.

To try to identify the root of the error I followed three import scenarios:

1. Import to a new folder set up by the Import Destination dialog:

This works correctly!

2. Import to a new folder that was set up by Explorer, externally to LR:

This has imported the image OK, but to the incorrect network path name.

3. Import to a folder that was created in the Library view immediately prior to the import:

Here we have the original issue that I reported where the same physical folder is duplicated within the catalog.

So, three scenarios and three different outcomes, but wait...it gets worse. I experimented with the destination folder selection by taking different routes in the file picker to navigate the tree (e.g. navigating down the tree on the left of the window to the lowest level then selecting the file, as opposed to double-clicking in the right hand window until I reached the file). This gives further results combinations:


I've not involved PS at all here although the original reported issue concerned "save as" in PS, so it's definitely not an issue with PS per se, although I suspect that it may just be the same issue of the selection of the target folder within the file picker that was the cause.

I've been using my NAS as my primary storage for a few years and have only encountered this issue within the last couple of LR/PS updates.

Why are LR and PS not case-insensitive? I know that some operating systems are case-sensitive for files and commands, but having two or more folders which vary in only the case of their characters seems fundamentally high risk.