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!
Let's hope so! The more great choices the better.I think Hasselblad is aware of it … it will be more a question about whether it can be fixed technically at all …
As we can see the PDAF lines even when using a HR 32 mm unshifted , I just wonder if the lines can also be seen when using the 907x 100c in "native mode" just using a XCD 21 or 30mm lens . Has anyone of the owners of the 100C tried this ? ? ?I can confirm I can see the PDAF lines when using the Rodenstock 32mm HR unshifted on the CFV-100c. Attaching a sample of the sky, converted to B&W in LR with some sliders increased to make it clearly visible here. Will it ruin what I want to do until hopefully Hasselblad provides a fix? Not sure, especially if I can use the tricks already mentioned to make it much less visible or not visible at all. In the meantime, does anyone have the best email contacts for Hasselblad and Alpa just to add my data points?
Thanks
Could someone please try this with a gfx100…
this is the point: I used the Fuji gfx100S as also Sony A7RIV - both have the same Sony BSI sensor, afcouse sony in other size-and both shows no stripes issues at all!!!
tested also with Schneider Apo Digitars 35, 43, 47 and some Digarons with extra large movements.
I never seen this issue, even these are camera bodies, not backs, with all restriction of this bodies. But they work on technical cameras with all lenses that allows it mechanicly. So it was logical for me that with the new hasselblad back we get the ultimativ BSI sensor, where all the Schneider wides can be used at full movements...
But What have Hasselbald done!!!!
it is - as Imacon- one of the pioneer of digital backs!!!!
and they produce a first back ever that dont work with no one wide technical lens?
I cant imagine that technician at hasseblad did not see this. never, never!!!! these cant be all idiots!!!
I am sure that they see this problem, but other people decide what a company do.
some people there have decided that this is not so important,
nice advertising campaign, the moon story and the job is done.
Then some trolls and some youtube campaign and who cares so stupid things like technical cameras....
Dont forget that Fuji GFX is not a back and was not produce for use with technical cameras!No manufacturer is immune to having shipped a product with an issue that seemed obvious that they somehow missed. If you knew the amount of sausage that we see in our kitchen with the manufacturers we work with, it would maybe boggle your mind. It is not restricted to Hasselblad. We do quite a bit of behind the scenes reporting. And remember, Fuji also had an issue with PDAF banding with the original GFX 100, as I noted above.
The positive is there's no possibility they are not aware of it now. We've reported this to Hasselblad, and I'm sure others have as well, and yes, they do follow forums and other public outlets for discourse concerning their products.
It's now an obvious issue with the ball in their court, and hopefully they resolve it and sooner than later. It will take some time, but this only came to light less than a month ago, and the product only began shipping about 2 months ago.
Steve Hendrix/CI
That's interesting that Fuji was able to fix it. Thanks for the insight.
Is it completely gone, even with tech cam lenses shifted on bellows type cameras?
Dont forget that Fuji GFX is not a back and was not produce for use with technical cameras!
And this problem was solved years ago. So this issues were known.
So how a company like hasselblad can reapead it some years later, with same sensor, when one of the main reason to buy this back it is the use on technical cameras.
No sign of it shifting a S-K APO-Digitar 35mm 8mm on a GFX 100S.That's interesting that Fuji was able to fix it. Thanks for the insight.
Is it completely gone, even with tech cam lenses shifted on bellows type cameras?
There's always at least a few villagers ready to grab their torches and pitchforks. Some eagerly volunteer if it's their favorite villain being chased!Ok! Time to get out the torches and pitchforks. ...
Where there's on-sensor PDAF, you can find varying degrees of either banding or striping with the right (or wrong — depending on your point of view) combination of: scene and lighting conditions, lens and settings, processing adjustments, and magnification. PDAF banding or striping have different causes, but both can be mitigated in post processing.... Here's an LCC I just shot with an X2D and an XCD 28P. 100% crop from UL corner. The processing in LR is EXTREME. I included the LR screenshot so you can see just HOW extreme, but ....
Clarity is 100%, FWIW.
For the record, this issue does not concern me at all for use with the X2D. But I have done extreme BW conversion and it *is* there.
Matt
There’s always at least one villager who defends the King, no matter what he has done.There's always at least a few villagers ready to grab their torches and pitchforks. Some eagerly volunteer if it's their favorite villain being chased!
To be clear, I just did that test and posted it because the question would come up eventually and I wanted to close off that avenue of endless speculation (and argument). We seem to be closing in on "Hasselblad failed to correct a well known problem, and we expect they'll get on it soon. Heck, we can even demand it." I consider that real progress. Yes, it should have been attended to before now but, as @Steve Hendrix said, a lot of things make it out the door that shouldn't have.There's always at least a few villagers ready to grab their torches and pitchforks. Some eagerly volunteer if it's their favorite villain being chased!
Where there's on-sensor PDAF, you can find varying degrees of either banding or striping with the right (or wrong — depending on your point of view) combination of: scene and lighting conditions, lens and settings, processing adjustments, and magnification. PDAF banding or striping have different causes, but both can be mitigated in post processing.
PDAF striping might result from reflections onto imaging pixels from the masks which partially cover neighboring PDAF pixels. PDAF banding appears to result from manufacturers' attempts to mitigate PDAF striping thru in-camera filtering. Discussions of these artifacts began long ago with the earliest PDAF sensors and include every brand incorporating on-sensor PDAF technology to improve mirrorless camera autofocus performance.
I appreciate you posting your results and comments along with Rob's regarding his GFX. I also appreciate the results and accompanying comments which others have shared as they are individually and collectively informative.To be clear, I just did that test and posted it because the question would come up eventually and I wanted to close off that avenue of endless speculation (and argument). We seem to be closing in on "Hasselblad failed to correct a well known problem, and we expect they'll get on it soon. Heck, we can even demand it." I consider that real progress. Yes, it should have been attended to before now but, as @Steve Hendrix said, a lot of things make it out the door that shouldn't have.