Menu
What's new
The GetDPI Photography Forum

Great to see you here. Join our insightful photographic forum today and start tapping into a huge wealth of photographic knowledge. Completing our simple registration process will allow you to gain access to exclusive content, add your own topics and posts, share your work and connect with other members through your own private inbox! And don’t forget to say hi!

Hasselblad 100C and 35XL

A

Alkibiades

Well-known member
diggles said:
Thank you Marco for sticking with it! I've tried your solution on 2 different 35XL images now and it is working really well, better than what I came up with because using overlay isn't introducing noise like divide sometimes does.

On the second image I tried, the lines were still barely visible after applying the first overlay lcc image. I ended up duplicating the overlay lcc image and as far as I can tell it cleaned it up completely.

@Alkibiades , try this with your 28XL and let us know how it works :)

View attachment 213468
Click to expand...
Î will try it next days
 
A

anyone

Well-known member
Oh wow. Hasselblad replied to me finally on the issue:

"For the banding issue you are referring,Our R&D team confirmed that the "horizontal stripes"as you mentioned is caused by PDAF.And it is also known as PDAF banding.When using a wide-angle lens, especially when using a technical camera, it is easy to appear in the edge position, because the CRA of the edge light is large, and the dark Angle problem is more significant. The algorithm will expand the gain of the corners to compensate for the attenuation of brightness, and because the sensitivity of PD pixels is only half of that of ordinary pixels, the difference of PD pixels is further amplified.hence It forms a regular horizontal black line.

Here is the method we provide to mitigate this kind of issue(see attached)."

... and the method they attached, is a word document, I provide a screenshot, there are some elements that may seem familiar to some of you:

Bildschirmfoto 2024-06-05 um 15.26.07.png

Right. It's a copy of the steps AND the images Warren (@diggles) provided. Did they reach out to you, Warren, and ask for permission?

Needless to say that this is not the answer I hoped for. I replied and asked for a native fix, either in the firmware or in Phocus.
 
Last edited:
P

Paul Spinnler

Well-known member
OMG. I'd be furious if they'd take my makeshift solution from a forum post.

Firstly its not ok w/o permission and secondly its not a REAL solution.

Looks like there won't be a fix for this back.
 
diggles

diggles

Well-known member
anyone said:
Oh wow. Hasselblad replied to me finally on the issue:

"For the banding issue you are referring,Our R&D team confirmed that the "horizontal stripes"as you mentioned is caused by PDAF.And it is also known as PDAF banding.When using a wide-angle lens, especially when using a technical camera, it is easy to appear in the edge position, because the CRA of the edge light is large, and the dark Angle problem is more significant. The algorithm will expand the gain of the corners to compensate for the attenuation of brightness, and because the sensitivity of PD pixels is only half of that of ordinary pixels, the difference of PD pixels is further amplified.hence It forms a regular horizontal black line.

Here is the method we provide to mitigate this kind of issue(see attached)."

... and the method they attached, is a word document, I provide a screenshot, there are some elements that may seem familiar to some of you:

View attachment 213714

Right. It's a copy of the steps AND the images Warren (@diggles) provided. Did they reach out to you, Warren, and ask for permission?

Needless to say that this is not the answer I hoped for. I replied and asked for a native fix, either in the firmware or in Phocus.
Click to expand...
Shortly after this thread started, I reached out to Hasselblad support to bring the issue to their attention and shared this solution with them. They have permission, and I’m happy they find it useful enough to share with others.

Perhaps the fix by @mristuccia should be shared with them as well, but I'll leave that up to Marco. ;)

Ideally, they will develop a method within Phocus. If RawTherapee can do it, then they should be able to do it too. I wonder if they know about it…
 
B

Bill_Evans

Active member
I just bought into this ”mess” :). I confess that I’m quite a bit disappointed that I wasn’t able to bargain basement shop this “crapy” digital back in the buy / sell forum :). But luckily our fabulous forum sponsor had a couple in stock. I’m looking forward to easing it into my various workflows and am grateful for all the useful info this site provides.
 
A

anyone

Well-known member
Bill_Evans said:
I just bought into this ”mess” :). I confess that I’m quite a bit disappointed that I wasn’t able to bargain basement shop this “crapy” digital back in the buy / sell forum :). But luckily our fabulous forum sponsor had a couple in stock. I’m looking forward to easing it into my various workflows and am grateful for all the useful info this site provides.
Click to expand...
Congratulations! I think this is an awesome back in many situations. Just this thread is about the fix of a specific problem. If Hasselblad manages to get this fixed, it will be 100% awesome. Now it's "just" 85%.
 
mristuccia

mristuccia

Well-known member
diggles said:
Shortly after this thread started, I reached out to Hasselblad support to bring the issue to their attention and shared this solution with them. They have permission, and I’m happy they find it useful enough to share with others.

Perhaps the fix by @mristuccia should be shared with them as well, but I'll leave that up to Marco. ;)

Ideally, they will develop a method within Phocus. If RawTherapee can do it, then they should be able to do it too. I wonder if they know about it…
Click to expand...
Any of you feel free to share my fix with HB, if you find this helpful.

I for one am not going to waste my time with HB support again in my life, unless it is really, really necessary. Last time I reported an issue on Phocus for macOS Intel machines, I did not see any fix in any of the next three versions of the software, despite thanks and the promise of a fix (keystone correction was not applied to exported TIFFs/JPEGs). Then I gave up, moved to Apple Silicon and lost track. But I bet the issue is still there. 😉
 
Last edited:
A

anyone

Well-known member
Another answer of the support, to my reply:
"As the technical support,your request is understood by us.We will report your request to our R&D team and currently we kindly recommend you to stay tuned with our official website for the latest news on this."
 
You must log in or register to reply here.
Top