importing creating a new (phantom)folder

  • 1
  • Problem
  • Updated 8 months ago
Merged

This conversation has been merged. Please reference the main conversation: Lightroom: Doesn't ignore case of folder names

perating System:Mac 10.13.1
Exact Lightroom Version (Help menu > System Info):Classic

I am seeing some strange behavior on importing images, either from RAW on a camera card or JPEG on a thumb drive.
My work has always been to create a folder in the Folder panel of the Library Module of Lightroom. Then import and set thew destination to the newly created folder in the import panel.

As of 3 days ago this importing has some strange behavior. Now I should mention that my Catalog and Library are in the default Picture folder of the boot drive. (2TB SSD)
What I see:
1) The destination folder shows 0 after the import
2) A new phantom folder is created with the images inside.
3) The path for the folder is identical to what I had created prior to the import except the new folder is outside of the picture folder, in fact it shows even when the user folder is closed.
4) If I right click on a newly imported image and select show in finder, it shows it in the destination folder I had selected, not the phantom folder.???
5) If I try to drag the images into the destination folder I get a pop up window saying they can't be moved because they already exist. ???

I have made a screen movie of this behavior, it should be below. 
Photo of TJ Cadwalader

TJ Cadwalader

  • 3 Posts
  • 0 Reply Likes

Posted 8 months ago

  • 1
Photo of Jeff

Jeff

  • 38 Posts
  • 16 Reply Likes
This actually started on LR CC (2015 version) a few updates ago (maybe 2?). I can confirm that's exactly what happens on my Windows 10 system so we can't blame MacOS or Windows, can we? This behavior carries over to Lightroom "Classic". 

To "fix" it, I have to delete that phantom folder in lightroom, then Synchronize Folder with the existing folder selected. It's a PITA.
Photo of Johan Elzenga

Johan Elzenga, Champion

  • 1228 Posts
  • 495 Reply Likes
This is probably caused by a mysterious bug that creeps up from time to time, known as the 'case sensitive' problem or 'capitalization' problem. In short: MacOS X and Windows are case-insensitive, so they consider a folder called 'Folder' and another folder called 'FOLDER' as one and the same folder. Lightroom is case-sensitive however, so Lightroom does see two different folders. That problematic 'double' folder is usually a parent folder, that's why Lightroom shows the new subfolder in a different location. The easiest way to try to solve it in this case is not create the subfolder in Lightroom, but in the Finder (Mac) or Windows Explorer. Then in the import dialog you can just select it.
Photo of TJ Cadwalader

TJ Cadwalader

  • 3 Posts
  • 1 Reply Like
This makes sense, prior to 2 weeks ago my SSD WAS case sensitive. Updating my SSD machine to the new operating system, reformatted my drive to APFS which by default is NOT case sensitive.
You do not have an option, on a machine with an SSD, to select a formatting option. There may be more people having this issue as they update the OS.
Photo of Jeff

Jeff

  • 38 Posts
  • 16 Reply Likes
It's a Lightroom bug that should be fixed - I have been using LR since v2.0 and only recently started having this problem (on Windows). For some reason, LR thinks the root of my pictures drive is e:\pictures. But drive letters are always uppercase and this apparently leads to the confusion. I don't know why my catalog thinks it's lowercase but I've used the same catalog since day one (with conversions of course).

Regardless, they should fix some bugs rather than introduce or regress old ones.
Photo of Johan Elzenga

Johan Elzenga, Champion

  • 1228 Posts
  • 495 Reply Likes
The root of the problem is not that Lightroom “thinks” something. The root of the problem is that e:\pictures and E:\pictures really both exist. For Windows these are one and the same thing, because Windows is case-insensitive. But for Lightroom these are two distictly different paths, because Lightroom is case-sensitive. Why both exist is anyones guess however. It could be a bug in Lightroom, but it could also be a problem of the OS.

This conversation is no longer open for comments or replies.