Photoshop CC 2018: Imacon 3F plugin not working

Do you know who they reported it to? I'm not seeing a record from them.

Hi Jeffrey, thank you for reacting.

I got an email reply on my support case with Hasselblad from Beatrice Dobirta. But I don't know to whom Hasselblad reported the issue to at Adobe.

I can try to request details about where in Adobe the issue was reported, if you require it.

Thanks. I think I've tracked something down from someone on the Camera Raw side. I'll follow up if they have any questions.

Sounds good.

A user on the "Imacon Scanners" Yahoo group (mristuccia) have found this workaround which makes it possible to open the 3f file:

1. Open Photoshop CC 2018
2. File -> Open... (as usual)
3. Click the button "Options" in the open dialog (bottom left)
4. Select the .fff file you want to work with
5, Now you should have:
    Enable: All Readable Documents
    Format: Imacon 3f
6. Click on "All Readable Documents" and JUST RE-SELECT it from the option list, or select another option and then re-select "All Readable Documents".
7. Click the button "Open" (as usual)

The thread can be found here: https://groups.yahoo.com/neo/groups/IMACONUSERS/conversations/topics/12453

I hope this may help in the work on this issue.

Thanks. This is helpful!

Hi Jeffrey, thank you for your reply.

Firstly, please bear in mind, that there is two types of 3F files; either files from a digital Hasselblad back, or files from the scanner software FlexColor (when using an Hasselblad/Imacon/Flextight scanner). The issue is with the latter. Just to make sure we are on the same page.

My workflow is:
1. scan to 3F file as a linear scan, no color inversions or color adjustments are made at this step.
2. open 3F file in Photoshop to remove dust/scratches, save 3F file.
3. open 3F file in FlexColor to convert the image (negative to positive with specific color settings), save as a new TIFF file
4. further processing of the TIFF in either Lightroom or Photoshop.

The reason that I use FlexColor to convert the images is because of the color profiles. I'm not interested in using 10-100x more time manually colorconverting my scans, which I hope you find a reasonable argument. 

I do know that the 3F file is a TIFF file, but renaming it does not solve the problem. Also, Adobe broke som existing functionality in the file handling, where re-selecting a dropdown in the open dialog circumvents the issue. So it should not be a terrible difficult error to correct.

I hope that this issue is to be resolved.

Hi Michael, is there a reason why you just don't skip step 2 and remove the dust and scratches in Photoshop after converting the file to a TIFF?

When removing dust/scratches before converting the file, I can make different conversions without having to remove dust/scratches more than once. This is explained in more depth here: https://www.knowhowtransfer.com/how-to/resources/3f-system-revolutionary-pro-scanning-system-by-hass... (under the section Retouching 3F originals)

Mr. Jeffrey Tranberry, will there be any solution to this bug? There has been a couple of updates, but none of them have solved this issue.

FYI same problem persists in CC2019. There is an "options" button at the lower left of the "open" dialog box - it brings up the "enable" and "format" options to open a file. The "format" drop down is able to find the 3F plugin but upon trying to open the file a dialog box says to update ACR and includes a weblink. The link shows supported cameras and under the Hasselblad cameras there is an * (** Hasselblad FFF files created by the Hasselblad Phocus software for currently supported models are also supported. FFF files created using the FlexColor software are not supported.) Regardless, I too want to open my scanner 3F files in Photoshop (not ACR) the way I used to. Is this possibly a plugin problem now?

Michael - I was having the same problem and I think I have diagnosed it and thought I would post here in case it helps anyone else. I noticed that I too could not rename .fff scanner files, nor delete them, nor sometimes open them in Flexcolor. A post above indicated that it was likely a permissions issue/being open somewhere in some other file, so I eventually traced it to likely relating to the Windows 10 'Photos' app and perhaps related to having a preview of the file (i.e. after I had opened a .fff file in Photos and could see the negative, if I closed it in Windows explorer it would show me a preview thumbnail of that photo, but not other 3f photos in the same directory that I hadn't specifically opened in Photos). I then uninstalled Photos app (instructions online) and also made sure to remove thumbnails when using the Disk Cleanup option - and this seems to have resolved the issue - I can now rename, move, delete at my hearts content.