HELP Hasselblad Phocus making my files too "crunchy"

[delfalex]

Sometimes restarting computer help to solve some issues.

If only it were that simple to fix the problem

Sent from my Pixel 2 using Tapatalk

[delfalex]

One step is the conversion to the .FFF raw file. That has to be done.

ACR supports the FFF files directly so I am unsure why anything is being exported. Exporting as a DNG to ACR is just asking for trouble.


If you are on a Mac then just for fun open a FFF file using the Preview app and then export as a TIF. Does it look the same as the export of TIF from Phocus?

The conversion from RAW data stream to FFF is done by Phocus after it has received all 4 / 6 data packages (multishot files don't exist in the 3FR format).

The only software that currently supports Hasselblad's Multishot FFF files is Phocus, all other convertors require that the file be demosiced beforehand & fed as a linear DNG (hence the exporting in such a manner).

FWIW I've tested every version of Phocus with 6S files and in each case that harsh shadow/ highlight that the OP has alluded to manifests itself in the same way.

Sent from my Pixel 2 using Tapatalk

[BobShaw]

The only software that currently supports Hasselblad's Multishot FFF files is Phocus, all other convertors require that the file be demosiced beforehand & fed as a linear DNG (hence the exporting in such a manner).

Can you put a Multishot FFF file somewhere to download?
You can't see anything in a JPG.
I assume the camera, viewfinder and back are at the latest firmware?

[Master Technika]

The conversion from RAW data stream to FFF is done by Phocus after it has received all 4 / 6 data packages (multishot files don't exist in the 3FR format).

The only software that currently supports Hasselblad's Multishot FFF files is Phocus, all other convertors require that the file be demosiced beforehand & fed as a linear DNG (hence the exporting in such a manner).

FWIW I've tested every version of Phocus with 6S files and in each case that harsh shadow/ highlight that the OP has alluded to manifests itself in the same way.

Sent from my Pixel 2 using Tapatalk

Thank you Deleflex-
I’m just getting back to this now that the work is done.
I had no choice but to use Phocus with the 6shot files, but honestly those files are not what they could be if Hasselblad would just give the user a little more control. Their formula that is embedded in these files when processed through Phocus could be so much smoother, detail-wise, while still containing all that extra detail. I wish they would listen to their users more. We do have some reasonable experience and expectations.

[BobShaw]

I wish they would listen to their users more.

So you actually contacted Hasselblad support?
I ask that because although I haven't seen your images I downloaded a Multishot FFF file and the resulting TIF from the sample images site and the FFF is definitely fuzzy but the TIF is very sharp.
(I would say that some parts of the image are overexposed but not "crunchy".)

https://www.hasselblad.com/learn/sample-images/

[delfalex]

(I would say that some parts of the image are overexposed but not "crunchy".)
https://www.hasselblad.com/learn/sample-images/

Unfortunately, after forgetting about the camera shake (hence fringing), I'd say that the halos in these 100% crops are crunchy  - definitely some kind of OTT Unsharp Mask being applied:
(0115 images are from the Tif & 0116 are from from the FFF)

BTW with that lens (HC120II) on these 100MP backs, one starts seeing the beginings of diffraction kicking in from F9, so if you think this file is sharp F16, you'll be amazing when reviewing F8 images - incredible (ahem except for the nasty halos!)

[Master Technika]

Yes, Bob, of course I reached out to the company- they were of minimal help.

Delfalex, thank you for posting examples and your experience! Also, I agree with your assesments about where diffraction starts setting in. I also use that lens and previously with the regular 100c camera. When you get it just right- it does create a very sharp point of focus.