Why does a Canon 5D Mark II show a 0.976 crop factor instead of 1.0?
Asked 11/18/2014
2 views
2 answers
0
When importing Canon 5D Mark II images into Hugin, the software auto-fills a focal length multiplier/crop factor of about 0.976 instead of 1.0. EXIF data reports a similar value for “Scale Factor To 35 mm Equivalent,” even though the camera is generally considered full frame and Canon lists the sensor as 36×24 mm. Should this value be changed to 1.0 for panorama stitching, or is the metadata-derived value more correct? Why might the camera record a value slightly below 1 on a full-frame body?
Originally by Photography Stack Exchange contributor. Source · Licensed CC BY-SA 4.0
Photography Stack Exchange contributor
11y ago
2 Answers
9
I think you should, in fact, use the slightly-smaller value. That's not because I've measured, but because I can resolve the apparent contradiction from exiftool: it's showing you a rounded value. Try giving it the -n flag, to disable what exiftool calls "print conversion":
$ exiftool -n -ScaleFactor35efl sample.jpg
Scale Factor To 35 mm Equivalent: 0.975938688184433
Which, of course, is ridiculous over precision, but there's the raw value. I agree with Philip's comment that the difference probably has little practical effect, but it seems likely that if you're going for "most correct", the metadata is right.
I suspect that the small difference is due to the edge of the frame being masked out and used for setting black level and similar. (Some of it is for demosaicing edge pixels, but 2% seems excessive for that.)
And I can confirm that this lines up with Canon's specs, too: the spec sheet lists
Effective Pixels Approx 21.1M
Total Pixels Approx 22.0M
and, a-ha:
22 × 0.975938688184433² ≈ 20.95403911
which is pretty close to the effective number — close enough that I'm going to call the remaining difference rounding error. (This works out to a strip of about 100 pixels around each edge, by the way.)
Originally by user1943. Source · Licensed CC BY-SA 4.0
user1943
11y ago
0
Generated from our catalog & community — verify before relying on it.
Use 1.0 only if you want the conventional “full-frame” simplification; the EXIF value around 0.976 is likely the more technically correct value for that camera’s effective imaging area.
A 5D Mark II is marketed as full frame, but the actual active sensor area used for the image may be very slightly smaller than the nominal 36×24 mm. That can happen because edge pixels may be reserved or masked for calibration/black-level processing, or because the true sensor dimensions differ slightly from the nominal spec. That would explain why the metadata reports a value just under 1.
In practice, the difference is tiny and usually won’t matter much. But if your goal is “most correct,” keeping the metadata value is reasonable. Your Hugin tests also suggest that values very close to 1.0 behave similarly, with 1.0 giving slightly lower alignment error in your sample, so either choice is unlikely to make a major difference.
Bottom line: 0.976 is not necessarily wrong; it likely reflects the camera’s effective sensor area more precisely than the rounded full-frame assumption of 1.0.
Recommended products
UniqueBot
AI11y ago
Your Answer
Related Questions
What lens data should I enter in Hugin for a Sony DSC-T100?
Is a used Canon 5D Mark II a good budget full-frame upgrade from a Rebel?
Why would you use a 0.007mm circle of confusion on a Canon 5D Mark II?
Could a camera use a 36×36 mm square sensor, and would that count as medium format?
Does circle of confusion depend on megapixels or sensor size?