*BUSTED* 1D Mark V Spec List [CR1]

[Canon Rumors]

Share

*Busted* Another spec list torn apart by the community. The crop factors are off to a lot of people. APS-C isn’t 1/1.6.

Received 8 spec lists today! I expect 1.6x more tomorrow.

1D Mark V A new claimed spec list of the upcoming 1D Mark 5.

We’re still getting conflicting 1Ds Mark IV & 1D Mark V model names. I’m still not sure what the new flagship will be called.

• Sensor: 36 x 24mm CMOS sensor
• Processor: Dual DIGIC 5
• A/D conversion: 14 bit
• Image sizes: 32.4 mp, 16.2 mp, 8.1 mp @ 5, 3 fps
• APS-H mode (1.3x) – 24.9 mp, 12.5 mp, 6.2 mp @ 8, 3 fps
• APS-C mode (1.6x) – 20.3 mp, 10.1 mp, 5.1 mp @ 10, 3 fps
• Movie Mode: 1920 x 1080 @ 29.97, 25, 23.976 fps
• 1280 x 720 @ 59.94, 50 fps
• 640 x 480 @ 59.94, 50 fps
• APS-H mode (1.3x) – 1920 x 1080 @ 59.94, 50 fps
• APS-C mode (1.6x) – 1280 x 720 @ 119,88, 100 fps
• Viewfinder: Magnification: 0.76x, 100% frame coverage
• APS-H viewfinder magnification zoom: 0.87x – 89% viewfinder crop
• APS-C viewfinder magnification zoom: 1.0x – 82% viewfinder crop

Go on and discuss what you think. This is fairly inline with what we’ve heard previously.

cr

[bchernicoff]

I'm not sure these numbers are internally consistent. 20.3mp * 10.3 fps indicates the camera can process 209mp/s of data. 24.9mp * 8.3fps = 207mp/s which is are fairly close, but 32.4mp * 5.3fps = 171mp/s. If it shot full-frame at 6.4 fps it would be consistent...unless Canon had some other reason to constrain full-frame shooting to 5.3fps. Also why would a viewfinder that can show 100% of full-frame show less than that for APS-C or APS-H?

I call BS.

[neuroanatomist]

This is fairly inline with what we’ve heard previously.

This may be in line with what we've heard previously, but we're obviously hearing these things from people who are making this crap up.

• Image sizes: 32.4 mp, 16.2 mp, 8.1 mp @ 5, 3 fps
• APS-H mode (1.3x) – 24.9 mp, 12.5 mp, 6.2 mp @ 8, 3 fps
• APS-C mode (1.6x) – 20.3 mp, 10.1 mp, 5.1 mp @ 10, 3 fps

Folks, if you're going to fabricate a rumor and send it to CRguy, please go out and learn how sensor sizes scale and also some basic math.

If you take a FF 32.4 MP sensor and run it in a hypothetical 'APS-C mode' you don't get a 32.4 ÷ 1.6 = 20.3 MP image.  The 'crop factor' is a diagonal measure that impacts field of view, but real pixels on a sensor have both x and y dimensions, so when you scale a FF 32.4 MP sensor to that 'APS-C mode' you get a 32.4 ÷ 1.6² = 12.6 MP image.

Please, go waste someone else's time, or come back when you're smarter.

I declare shennigans!!

[mkln]

I'm not sure these numbers are internally consistent. 20.3mp * 10.3 fps indicates the camera can process 209mp/s of data. 24.9mp * 8.3fps = 207mp/s which is are fairly close, but 32.4mp * 5.3fps = 171mp/s. If it shot full-frame at 6.4 fps it would be consistent...unless Canon had some other reason to constrain full-frame shooting to 5.3fps. Also why would a viewfinder that can show 100% of full-frame show less than that for APS-C or APS-H?

I call BS.

agreed,
would the sensor have a different density in different areas? I don't believe this.

if there are 20mpix on APSC format then, with the same density on a 2.56x larger area, there should be 51.2mpix on the FF area.
also note how 20.3 * 1.6 = 32.48 and this is the wrong way to calculate mpixels.

this tells us that the person who sent you that doesn't even know how to build credible specs.

[Shnookums]

This will not happen if for one reason it is exactly what I would like. Merge both 1D and 1Ds and price it just a bit higher than the current 1D.

But, I continue wishing hard this is what will be announced in the next month.

[JasonM]

I declare shennigans!!

Yep, shenanigans are afoot.  Is it meant in good fun or just a mischievous annoyance from a Nikon shooter rattling our chains?

[Rocky]

""Viewfinder: Magnification: 0.76x, 100% frame coverage
APS-H viewfinder magnification zoom: 0.87x – 89% viewfinder crop
APS-C viewfinder magnification zoom: 1.0x – 82% viewfinder crop ""
That will make the view finder system become a monster with a built-in zoom (Automatic??). I do not think that is real spec.

[dilbert]

This is fairly inline with what we’ve heard previously.

This may be in line with what we've heard previously, but we're obviously hearing these things from people who are making this crap up.

• Image sizes: 32.4 mp, 16.2 mp, 8.1 mp @ 5, 3 fps
• APS-H mode (1.3x) – 24.9 mp, 12.5 mp, 6.2 mp @ 8, 3 fps
• APS-C mode (1.6x) – 20.3 mp, 10.1 mp, 5.1 mp @ 10, 3 fps

Folks, if you're going to fabricate a rumor and send it to CRguy, please go out and learn how sensor sizes scale and also some basic math.

If you take a FF 32.4 MP sensor and run it in a hypothetical 'APS-C mode' you don't get a 32.4 ÷ 1.6 = 20.3 MP image.  The 'crop factor' is a diagonal measure that impacts field of view, but real pixels on a sensor have both x and y dimensions, so when you scale a FF 32.4 MP sensor to that 'APS-C mode' you get a 32.4 ÷ 1.6² = 12.6 MP image.

Please, go waste someone else's time, or come back when you're smarter.

I declare shennigans!!

FWIW, the APS-H megapixel number is also wrong.

But, the question is, is the mode there and the submitter has just made up the megapixel number or is the whole thing a fiction?

[Bokehmon]

This is fairly inline with what we’ve heard previously.

This may be in line with what we've heard previously, but we're obviously hearing these things from people who are making this crap up.

• Image sizes: 32.4 mp, 16.2 mp, 8.1 mp @ 5, 3 fps
• APS-H mode (1.3x) – 24.9 mp, 12.5 mp, 6.2 mp @ 8, 3 fps
• APS-C mode (1.6x) – 20.3 mp, 10.1 mp, 5.1 mp @ 10, 3 fps

Folks, if you're going to fabricate a rumor and send it to CRguy, please go out and learn how sensor sizes scale and also some basic math.

If you take a FF 32.4 MP sensor and run it in a hypothetical 'APS-C mode' you don't get a 32.4 ÷ 1.6 = 20.3 MP image.  The 'crop factor' is a diagonal measure that impacts field of view, but real pixels on a sensor have both x and y dimensions, so when you scale a FF 32.4 MP sensor to that 'APS-C mode' you get a 32.4 ÷ 1.6² = 12.6 MP image.

Please, go waste someone else's time, or come back when you're smarter.

I declare shennigans!!

hit the nail on the head. i really hope it's a 12fps monster, so I can do 2x speed video at like 6k

[Holy Trinity]

BS. In terms of density, The equivalent of a 32Mpx full frame sensor is around:

- 19Mpx for an APS-H
- 13Mpx for an APSC-C

...

[neuroanatomist]

FWIW, the APS-H megapixel number is also wrong.

But, the question is, is the mode there and the submitter has just made up the megapixel number or is the whole thing a fiction?

Of course.

Maybe the specs are correct, and the amazing procesing power of dual Digic V enables the new camera to perfectly interpolate and upscale the images.  Or maybe it just adds a big border of black pixels...   

[RS_RS]

What all you naysayers haven't realised is that this new model has different-sized pixels in different parts of the sensor. 

[Shnookums]

BS. In terms of density, The equivalent of a 32Mpx full frame sensor is around:

- 19Mpx for an APS-H
- 13Mpx for an APSC-C

I would love that much better than being stuck with max 5fps or 10fps.

[kubelik]

I declare shennigans!!

good call.  also, given the fairly legit canon warranty page rumor showing a "1Ds Mark IV" it sounds like that's what's actually in the pipeline, so anything calling out for a 1D unification better try double hard to convince us all...

[bchernicoff]

What all you naysayers haven't realized is that this new model has different-sized pixels in different parts of the sensor. 

I know you are joking, but I wonder if maybe the densities could be accurate for a different kind of pixel...say full RGB per pixel in line with the patent mentioned here: http://www.canonrumors.com/2011/07/canon-3-layer-sensor-foveon-type-patent/