ectobuilder
Veteran
Holy cow I never knew this type of sensor-lens-dof behaviour even existed.
To give you some background, I own a Batis 25 F2. This lens of course has a digital DOF scale readout. And when I used this lens on the A7S (12MP), A7II (24MP), A7RII (42MP) the digital DOF scale reads differently.
For example when Aperture = F22 and the Lens = Infinite (all in FF mode), the DOF scale reads:
A7S (12MP) = 4.4ft to Infinite
A7II (24MP) = 6.1ft to Infinite
A7RII (42MP) = 7.1ft to Infinite
So I wrote to Zeiss to see what their answer would be. I received a response from one of their Customer Care associates, Bertram:
Thanks for your inquiry.
The resulting depth-of-field depends on the resolution of the camera sensor (when compared e.g. in 100% view afterwards). So with different camera bodies (pixel sizes), the display of the Batis lenses will show different depth-of-field data under the same conditions (aperture setting, distance setting).
By the way, the data shown on the display of the Batis lenses (focus distance, depth of field) come from the camera body an cannot be influenced by the lens itself.
For further details, please do not hesitate to contact us!
With best regards
Bertram Hönlinger
_________________
Carl Zeiss AG
Camera Lens Division
Kundencenter / Customer Care Center / PHO-VC
Kundensupport / Customer Support
Bertram Hönlinger
Carl-Zeiss-Straße 22 - 73447 Oberkochen
Telefon/Phone: +49 7364 20-6175
Fax: +49 7364 20-5216
Email: photoapplication@zeiss.de
http://www.zeiss.de/photo
So the higher the MP, the shallower the DOF. This pretty much has made up my mind to stick with all A7S or A7SII's as I want to keep all of my working DOF's the same.
For applications like steadicam, having a hyperfocal distance of 7.1ft to infinite is not cool! 4.4ft to infinite (A7S) is definitely better! That is a huge difference of almost 3ft of working distance!
Up until recently, this hasn't been an issue since most of the popular DSLR cameras ranged from 18-24MP. But now we have a range of 12MP all the way up to 50MP to choose from. So the issue is way more apparent now.
This is something to be aware of!
To give you some background, I own a Batis 25 F2. This lens of course has a digital DOF scale readout. And when I used this lens on the A7S (12MP), A7II (24MP), A7RII (42MP) the digital DOF scale reads differently.
For example when Aperture = F22 and the Lens = Infinite (all in FF mode), the DOF scale reads:
A7S (12MP) = 4.4ft to Infinite
A7II (24MP) = 6.1ft to Infinite
A7RII (42MP) = 7.1ft to Infinite
So I wrote to Zeiss to see what their answer would be. I received a response from one of their Customer Care associates, Bertram:
Thanks for your inquiry.
The resulting depth-of-field depends on the resolution of the camera sensor (when compared e.g. in 100% view afterwards). So with different camera bodies (pixel sizes), the display of the Batis lenses will show different depth-of-field data under the same conditions (aperture setting, distance setting).
By the way, the data shown on the display of the Batis lenses (focus distance, depth of field) come from the camera body an cannot be influenced by the lens itself.
For further details, please do not hesitate to contact us!
With best regards
Bertram Hönlinger
_________________
Carl Zeiss AG
Camera Lens Division
Kundencenter / Customer Care Center / PHO-VC
Kundensupport / Customer Support
Bertram Hönlinger
Carl-Zeiss-Straße 22 - 73447 Oberkochen
Telefon/Phone: +49 7364 20-6175
Fax: +49 7364 20-5216
Email: photoapplication@zeiss.de
http://www.zeiss.de/photo
So the higher the MP, the shallower the DOF. This pretty much has made up my mind to stick with all A7S or A7SII's as I want to keep all of my working DOF's the same.
For applications like steadicam, having a hyperfocal distance of 7.1ft to infinite is not cool! 4.4ft to infinite (A7S) is definitely better! That is a huge difference of almost 3ft of working distance!
Up until recently, this hasn't been an issue since most of the popular DSLR cameras ranged from 18-24MP. But now we have a range of 12MP all the way up to 50MP to choose from. So the issue is way more apparent now.
This is something to be aware of!
Last edited: