• Welcome to the Lightroom Queen Forums! We're a friendly bunch, so please feel free to register and join in the conversation. If you're not familiar with forums, you'll find step by step instructions on how to post your first thread under Help at the bottom of the page. You're also welcome to download our free Lightroom Quick Start eBooks and explore our other FAQ resources.
  • Are you using the cloud-based Lightroom apps for Windows, Mac, iOS, Android, Apple TV and Web? Then you'll love my new book, Adobe Lightroom - Edit Like a Pro!

    You'll learn how to use the Lightroom cloud ecosystem to organize, edit and share your photos. You'll also come to understand the thought processes used by professional photographers when they're editing their own photos, so you can transform your photos quickly and easily. And better still, the eBooks are updated for every release, so it's always up to date.
  • It's Lightroom update time again! New cameras (including the Canon R5/R6), lens profiles and bug fixes, and the ability to disable built-in lens corrections for specific new cameras. Here's the usual list

NC_FLLST.DAT — What to do with it in LR

Joined
Jun 20, 2009
Messages
16,488
Location
Houston, TX USA
Lightroom Experience
Power User
Lightroom Version
Cloud Service
Lightroom Version
8.3.1
Operating System
macOS 10.14 Mojave
The camera card folder that holds my Nikon Z7 RAW files also contain a file named NC_FLLST.DAT. This file appears to be some sort of index of the contents in the folder on the card. It does not seem to be of any end user value and being binary, isn't even human readable. Every time I import RAW files, LR pops up a warning/error message about the file. Is there a way to get LR to ignore the file or by some means not have too deal with the warning/error message every time I import from my camera?
 
Joined
Sep 29, 2007
Messages
22,660
Location
Isle of Wight, UK
Lightroom Experience
Power User
Lightroom Version
Cloud Service
Hmmmm. Not that I can think of. Nikon probably forgot to make it invisible. I wonder whether making the file invisible through Terminal would mess anything up.
 
Top