I have my photos on a separate volume at
Everything works fine except when I choose "Edit in Photoshop CS6", work on the image in Photoshop then save it. It gets saved back to the same folder as the original file, but when I tab back to Lightroom it just shows a square tile with a question mark instead of the new file. Tapping on the exclamation mark reveals that Lightroom thinks the new file is supposed to be in
For example the dialog box might say:
“_DSC3047-Edit.tif” could not be used because the original file could not be found. Would you like to locate it?
Previous location: /Users/Lightroom Photos/2012/2012-12-08/_DSC3047-Edit.tif
When in reality the original and the edit are both in /Volumes/Users/Lightroom Photos/2012/2012-12-08/ and there is not, and never was a /Users/Lightroom Photos/…
That is, something about saving back from Photoshop stripped off the "/Volumes/" from the beginning of the path. I can choose Locate and find it right where it should be and it will show up. Once it shows up the image tile shows the image but has an exclamation mark; tapping on that brings up a dialog box that says:
The metadata for this photo has been changed by both Lightroom and another application. Should Lightroom import settings from disk or overwrite disk settings with those from the catalog?
Doing this for every roundtrip is extremely tedious.
This is on a Mac and so /Users does exist but that maps to /Volumes/Macintosh HD/Users. I wonder if either LR or PS is confused by there being a /Users and a /Volumes/Users.
Editing in a Nik Plugin (e.g. Silver Efx) works properly, FWIW.
I am using LR4.2 and PS CS6 13.0.1 on OS X 10.8.2.
Can we see a screenshot of your Folders panel, so we can see the 2 different volumes showing please? I think it's one that'll be fairly easily fixed, but it helps to see what we're dealing with.
Thanks Victoria, here you go.
SSD is my root volume (most people would have "Macintosh HD" instead), so that is where /Users/… resides: so for example my home folder is at /Users/dave which is the same as /Volumes/SSD/Users/dave. You can see that saving from PS has made LR think I have image folders at /Users/… when I do not, and never have. You can see below "SSD" is the volume "Users" where the real image folders live (an external Firewire drive in this case).
I have expanded "Show Parent" to the root of each volume in that screenshot.
So under SSD, "/Users/Lightroom Photos 2/…" is bogus and under Users "Lightroom Photos 2" is legitimate.
Ok, great, before we do anything else, back up your catalog!
Let's start with the Volumes one. Right-click on / folder and choose Hide Parent Folder. Repeat for the Volumes folder, and probably the Users folder. You'll probably need to do the same with the Users folder in the bottom one. If everything disappears and the Folders panel goes blank at any stage, don't panic, just restart LR and they'll reappear. That's the point you're aiming for, without removing a folder directly containing photos. Then let's see an updated screenshot and we should be most of the way there.
Hang on, I've just spotted something. The SSD in your screenshot is listed as 110gb, but the Users folder is listed as 931gb. How is that? Is there a symbolic link moving the Users folder, or something like that? That would certainly explain your issue.
It puts the bogus entry back: as I said it is the LR->PS->LR round trip that put the bogus entry in the in the first place. I think it's getting confused by the fact that /Volumes/Users has "Users" in its name and there's also /Users. I don't disagree that it's a bad name but I can't change it now, and only LR/PS seems not to be able to cope with it.
I could however plug in another external drive that isn't called /Volumes/Users, put photos on it and in LR and see if LR->PS->LR works for that case. If it does that would seem to point to LR/PS being confused by the two Users somewhere.
Ah, so your whole user account is relocated onto the other drive? Wow, ok, I'm not quite sure where to go with this one then.
Yes, your test sounds pretty logical, so it's probably a good next port of call.