Photoshop CC 2018: Imacon 3F plugin not working

If anyone is interested, Hasselblad Support have reproduced the issue, and have reported it to Adobe.

The latest update (19.1.2) didn't fix this issue.

Adobe, are you working on this problem?

Sorry for the late reply. I was out of town the past two weeks. Eric from the ACR team looked at this back in 2014: https://feedback.photoshop.com/photoshop_family/topics/support_of_hasselblad_3f_files

fff files are essentially 16-bit RGB TIFF files with some custom/proprietary tags in them for the Hasselblad software to access.

Do you use the Hasselblad software to edit your the original fff images?

If not, the simplest thing to do is rename the files from <myfilename>.fff to <myfilename>.tiff and Photoshop will open them without any extra hoops. If you want them to open directly in Camera Raw, then set the ACR pref to automatically open TIFFs after you rename the files.

This reply was created from a merged topic originally titled Can't open Hasselblad Flextight x5 scanner .fff files.

1.  I am working with .fff files created with Flextight x5 (Hasselblad) scanner and Flexcolor software on an Apple computer.  Working in Windows 10 LR 8.4 will does not recognize files.  In Import, the files are listed, but no image (Preview Unavailable), "File cannot be opened by Lightroom." (My understand is that .fff files from the scanner are not the same as .fff from a Hasselblad camera.)

2.  In Photoshop 20.0.6, I've installed latest plugin from Hasselbald, but Raw converter does not recognize .fff images.

3.  And the most interesting issue.  On Windows 10 computer, I cannot rename or delete any of the .fff files.  They can be copied.  There were no permissions issues.  No luck in Command Mode until I tried Safe Mode where still could not rename a file, but could delete a directory. 

Note: This conversation was created from a reply on: LR Classic Hates on Hasselblad Files .FFF and .3FR.

My original post has been merged into this thread and I was referred to J Tanberry's post about a workaround involving renaming the 3f files to .tif.  However, i'm unable to rename the 3f files.  Is there any possibility that because the scans were produced on a Apple computer that this causes problems in Windows 10?