Lightroom Classic: Counterintuitive behaviour of import-in-place and export-and-include

  • 1
  • Question
  • Updated 4 weeks ago
  • (Edited)
If I import-in-place -or- if I export with the 'Include in catalogue' option checked. LR Classic CC release 8.0 on a Mac running Mojave 10.14; creates a folder on the Folders panel that is visually 'disconnected' from the actual folder hierarchy (as understood by Finder) even if the folder is known to LR. The logic of this eludes me. The logic is made more elusive when I try to bring the existing real folder and the 'phantom' folder together. LR doesn't allow this and this has led me to doing things like moving or exporting to desktop, removing and re importing and then moving to where they're supposed to be. I now always export to a standard sub-folder of desktop (known to LR) and then move the exports to the folder where they were intended to go. This seems very screwball behaviour to me but that may be only because I don't understand the logic behind it. Could someone give me some guidance on this one, please?
Photo of Koro

Koro

  • 12 Posts
  • 5 Reply Likes

Posted 1 month ago

  • 1
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 4447 Posts
  • 874 Reply Likes
I am guessing this may be related to case-sensitivity in the folder path.  Some screenshots of your Finder window and your Lightroom Classic CC folder panel would go a long way toward diagnosing your issue. Is it possible for you post these?
Photo of Koro

Koro

  • 12 Posts
  • 5 Reply Likes
Good morning Rikk,

Thank you for your reply.

I set about to set up the screenshots that you asked for (starting by taking a screenshot of this screen). As part of that process, I discovered the 'Destination' panel that is available as part of the Import process. This panel did not exist in LR5 (my previous version) and hence I'm unfamiliar with it. Furthermore most of my importing is done from a device (SD card, phone, flash drive, etc) not from the HD. In that process the Destination panel options were directing the imported files by date into '.../root/Pictures/...'. Now that I understand what's going on, I will have a closer look at that panel. I'll post again on this thread if I have issues with this but for now I'll set this part of the question aside.

In the meantime, the export function is creating a 'phantom' folder like this (below). The image was exported using:



This is the result:  The folder is understood by Finder as the same but LR sees it as two 'different' folders (one 'real' and one 'phantom') but if I try to move the image from the 'phantom' folder to the 'real' one LR tells me the image is already there. True -- so why the 'phantom' folder? What's going on? I note that LR 5 did this identical process exactly as expected -- in other words the image appeared in the folder as understood by LR (i.e., the 'real' folder) and no 'phantom' was created.



Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 4447 Posts
  • 874 Reply Likes
Normally a 'phantom' folder like this is the result of a case-sensitivity issue somewhere in the path to each folder. If you right-click on the top folder and select Show Parent Folder until you reach the root and compare the paths, you may find a capital letter where small letter should be or vice-versa. 
Photo of Koro

Koro

  • 12 Posts
  • 5 Reply Likes
Looks like you are right (below). "/Users/buster/..." does not match ".../Users/Buster/..."

"Buster" is the root folder on the previous Mac (the one that runs/ran LR5). Setting up the new Mac required a name for the root folder. I gave it "Buster" which the OS converted to "buster" and then assigned. What I'm seeing now is the knock-on effect. Poo. It would seem that "Buster" is preserved in the metadata somewhere.

Thank for your assistance. Looks like I have a problem but it isn't the one I thought I had. Thanks again.

Best regards


Photo of Koro

Koro

  • 12 Posts
  • 5 Reply Likes
Rikk,

I have changed the home folder name to 'Buster' (instead of 'buster') and the export now behaves as expected. However, the Account Name for this Mac is still 'buster' (for reasons which I explained earlier) and it seems that there's no sane way to change it. Hence, importing from the HD creates a fully-qualified path like this: ".../Users/buster/..." NOT ".../Users/Buster/..." even though Finder understands ".../Buster/..." as the correct name.  Somewhat perversely, LR displays them as different folders but recognises them as being the same (hence disallowing moving files from one to the other).

Almost all of the time this will not be a problem even if imported images appear through '/buster/Pictures' because, invariably, images must be moved to a designated folder anyway.

Thanks for your time,
K

Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 4447 Posts
  • 874 Reply Likes
Please note that Lightroom Classic CC and Case-sensitive don't get along: Reference - https://helpx.adobe.com/lightroom/system-requirements.html
Photo of Koro

Koro

  • 12 Posts
  • 5 Reply Likes
Good morning Rikk

Oh, my giddy aunt! Case sensitivity is obviously a big-league serious issue for some users. I had no idea, but I can understand why it’s a problem. As you know I’m currently running two Macs:

The older Mac is OS X El Capitan
The newer Mac is macOs Mohave

OS X Mac diskutil info / returns:
File System Personality: Journaled HFS+
Type (Bundle): hfs
Name (User Visible): MAC OS Extended (Journaled)

MacOS Mojave diskutil info / returns:
File System Personality: APFS
Type (Bundle): apfs
Name (User Visible): APFS

Fundamentally different.

Hence the Mojave treatment of the Account name. My problem has now morphed into something of an entirely different character than what prompted my original question. We don’t need to pursue it further here, but I will have to take some steps to understand how it might affect me and how I can avoid causing problems for myself.

Thanks again for you time
K