Lightroom 5.7: Cannot read Xtrans raw files with filenames starting with underscore.

  • 1
  • Problem
  • Updated 3 years ago
  • (Edited)
Attempting to import raw files from Fuji X-E1 or X-T1 (Xtrans .RAF files) fails in specific situation.

- Importing a folder containing any RAF files with leading underscores causes the entire import to fail.
- Renaming all files in the import to remove the leading underscore results in all of them being imported successfully (Doing this just for testing - I would prefer to keep the leading underscore as an indication that they have the Adobe RGB color space embedded)

This happens in both Lightroom 5.6 and 5.7.

My computer:
iMac 21 in (3.1 GHz Intel Core i7), running Mac OS X 10.9.5 .

Additional info:
- this is new behavior (previous imports of files named this way worked fine) and
- it doesn't appear to matter which LR version I use (5.6, or 5.7), and
- files from 2 cameras exhibit the same symptoms, and
- two different card readers - same results

Here's a picture of the LR error (see attached):

One more thing:
It would be great if your bug entry form did not lose all of the content I typed in before prompting me to log in. That problem has been here for years (not exaggerating).
Do you really want feedback from your customers ? If so, fix your web form so they don't go away even more annoyed than when they arrived.
Photo of j13ag0

j13ag0

  • 6 Posts
  • 0 Reply Likes

Posted 3 years ago

  • 1
Photo of Steve Sprengel

Steve Sprengel, Champion

  • 2586 Posts
  • 323 Reply Likes
"Cannot be read" usually means the destination is not writable.

I never lose my entered information if it makes me login on this feedback site.
Photo of j13ag0

j13ag0

  • 6 Posts
  • 0 Reply Likes
Has anyone got useful feedback on this problem ?

Has anyone seen it, or anything like it ?

I'm asking here for a couple of reasons:
- contributing to a forum like this might help others who encounter the same problems
- I now understand that Adobe does not support their products for 'Troubleshooting' issues.

-jg-
Photo of John R. Ellis

John R. Ellis, Champion

  • 3378 Posts
  • 848 Reply Likes
I downloaded some sample X-T1 .raf pics from these sites:

http://www.imaging-resource.com/PRODS...
http://www.photographyblog.com/previe...

added leading underscores to their names, and couldn't reproduce the problem.

Adobe does pay attention to this forum for bug reports, but they're more likely to respond to reproducible bugs. If you uploaded a couple of sample pics to a Dropbox (or similar) folder, and provided details about your import settings (move/copy/add, any file renamings, any presets, etc.) then others could see if they could reproduce the problem, and/or you might get a better understanding of which conditions trigger it.

Also, it's very possible I'm missing something, but why is it important to know that your camera was set to AdobeRGB when you captured the raw image? Any embedded AdobeRGB profile won't affect raw processing.
Photo of Steve Sprengel

Steve Sprengel, Champion

  • 2586 Posts
  • 323 Reply Likes
I am not seeing this problem using LR 5.7 with a test X-T1 RAF file I have downloaded previously but not imported.

The file was originally called DSCF0511.RAF and I renamed it to _SCF0511.RAF and it imported fine along with two other Canon raws I took last night.

Here is the image in the Import grid:


and here is the image in the Library grid after import:


If you feel the issue is the name of the file, itself, then please upload your image, somewhere like http://www.dropbox.com/ and post a public download link to it, here.

I would add that I don't have a Fuji camera so cannot do a test import by connecting to the camera, itself. I am using an SD card plugged into my computer's built-in card-reader. If you would try this scenario on your system, rather than plugging in the camera, that would at least eliminate the issue as being something to do with how your computer filters files coming directly from the camera. If there is some codec or driver installed for your camera then it could be doing something to the files that has nothing to do with LR.

The most direct way to import into LR is to copy the files with Explorer or Finder to their final destination and do an Add import. See if that works for you.

As John asks, why do you shoot in AdobeRGB for some of your raw files? The raw data is the same either way so the initial underscore is not telling you anything about the raw data, and only the camera JPGs or the camera-embedded previews which are irrelevant to LR are going to have data in the AdobeRGB colorspace.
Photo of j13ag0

j13ag0

  • 6 Posts
  • 0 Reply Likes
Hello John (R. Ellis):

Thanks for your response and your suggestions. I will follow up with more details.

My mention of having selected 'Adobe RGB' for (Setup Menu) -> COLOR SPACE, was by way of explaining why the files in question have the leading underscores.
Even though I'm only writing raw (.RAF) files, the underscore character is prepended to the file name.
Since the COLOR SPACE setting only affects JPEGs or the JPEG enbedded in the raw file, I can (and will) change this setting to sRGB to work around the problem with LR.

regard,
-jg-
Photo of j13ag0

j13ag0

  • 6 Posts
  • 0 Reply Likes
In order to prepare a response to todays post by Steve Sprengel, I did some more tests. My intent was to elaborate on the specific conditions under which this problem occurs.

I an surprised to report that the problem no longer occurs as of now: Sunday November 30, 2014, 3:00pm.
I'm testing with the same files on the same SD card that failed to import when I reported the problem.

I will update this thread if the problem occurs again.

In the mean time, thanks to Steve and John for responding with suggestions.

regards,
-jg-

John Gibson
Toronto

PS. If pressed to explain the appearance of the problem and its subsequent disappearance, my best guess would be that fixes and fixes to fixes delivered in automatic (as of Mavericks) Mac OS X updates could be at the root.
Photo of John R. Ellis

John R. Ellis, Champion

  • 3378 Posts
  • 848 Reply Likes
Another hypothesis: Your SD card is intermittently flaky or has bad blocks. A quick google shows a number of disk utilities targeting SD cards, but I don't see anything for Mac.
Photo of Steve Sprengel

Steve Sprengel, Champion

  • 2586 Posts
  • 323 Reply Likes
The "cannot be read message" means your destination is not writeable, so an errant destination setting was superstitiously tied to the leading underscore in the filenames, hence my request for files and different testing scenarios to verify it was the leading underscore.

How does a bad destination specification lead to a read error: when the destination is not writable, the initial Copy phase fails to copy the files to the destination (without any error message) so then there's nothing to import during the Import phase, hence the message about files not being read.