Photo Forum / Digital Photography / DSLR Cameras / January 2005
D70 resolution: 3008x2000 - what's the 8 all about
|
|
Thread rating:  |
paul - 01 Jan 2005 22:37 GMT The D70 resolution is 3008x2000 pixels.
What is the extra 8 pixels all about?
Not that it matters I suppose, just curious.
John Bean - 01 Jan 2005 23:06 GMT > The D70 resolution is 3008x2000 pixels. > > What is the extra 8 pixels all about? > > Not that it matters I suppose, just curious. 3000 isn't divisible by 16, 3008 is.
The answer to your next question is to allow lossless rotation of JPEGs :-)
 Signature John Bean
The most likely way for the world to be destroyed, most experts agree, is by accident. That's where we come in; we're computer professionals. We cause accidents (Nathaniel Borenstein)
Merritt Mullen - 02 Jan 2005 03:37 GMT > > The D70 resolution is 3008x2000 pixels. > > [quoted text clipped - 5 lines] > > The answer to your next question is to allow lossless rotation of JPEGs :-) And MY next question is "How does 3008x2000 equate to the advertised 6.1 megapixels?" Seems to me it should be 6.016 megapixels.
Merritt
David J Taylor - 02 Jan 2005 09:54 GMT >>> The D70 resolution is 3008x2000 pixels. >>> [quoted text clipped - 11 lines] > > Merritt One presumes that marketing are allowed to round anything up!
Actually 3008 x 2000 is:-
6.016 million pixels
5875 KP (if K = 1024)
5.74MP (if M = 1024 x 1024)
So if the computing definition of mega were used, the camera is only 5.74MP!
(Some people complained a while back that not all "128MB" CF cards had the same capacity, and indeed it seems that some manufacturers use the MB = 1000000 bytes and other use MB = 1024 * 1024 bytes).
Cheers, David
Darrell - 02 Jan 2005 17:37 GMT > >>> The D70 resolution is 3008x2000 pixels. > >>> [quoted text clipped - 24 lines] > So if the computing definition of mega were used, the camera is only > 5.74MP! <rant> It seems mega has two different meanings, in storage it's 1,024x1,024. But in pixels it's the actual number. Same math my ISP uses for throughput speed ;) I also would prefer CF cards speeds be in mbps not 40X, 80X etc.. </rant
David J Taylor - 02 Jan 2005 18:11 GMT []
> <rant> > It seems mega has two different meanings, in storage it's > 1,024x1,024. But in pixels it's the actual number. Same math my ISP > uses for throughput speed ;) I also would prefer CF cards speeds be > in mbps not 40X, 80X etc.. </rant> You will be delighted to hear that both my SanDisk Ultra II CF and my wife's Kingmax Platinum SD cards do indeed carry a read and write MB/s rating....
David
John Bean - 02 Jan 2005 11:50 GMT >>> The D70 resolution is 3008x2000 pixels. >>> [quoted text clipped - 8 lines] > And MY next question is "How does 3008x2000 equate to the advertised 6.1 > megapixels?" Seems to me it should be 6.016 megapixels. You'll have to ask the whoever writes the advertising copy ;-)
FWIW my Pentax DS (with the same sensor) delivers 3008x2008 raw files, but crops JPEGs to 3008x2000.
 Signature John Bean
In all large corporations, there is a pervasive fear that someone, somewhere is having fun with a computer on company time. Networks help alleviate that fear (John C. Dvorak)
JPS@no.komm - 02 Jan 2005 16:45 GMT >And MY next question is "How does 3008x2000 equate to the advertised 6.1 >megapixels?" Seems to me it should be 6.016 megapixels. There is a border of RAW image data around the edges that most cameras making JPEGs or RAW converters will toss away in the process. There are also areas of pixels that are not exposed to light at all.
 Signature
<>>< ><<> ><<> <>>< ><<> <>>< <>>< ><<> John P Sheehy <JPS@no.komm>
><<> <>>< <>>< ><<> <>>< ><<> ><<> <>>< John Francis - 02 Jan 2005 19:31 GMT >> > The D70 resolution is 3008x2000 pixels. >> > [quoted text clipped - 8 lines] >And MY next question is "How does 3008x2000 equate to the advertised 6.1 >megapixels?" Seems to me it should be 6.016 megapixels. The full sensor imaging area is 3040x2024 (6,152,960 pixels).
Merritt Mullen - 03 Jan 2005 06:07 GMT > >And MY next question is "How does 3008x2000 equate to the advertised 6.1 > >megapixels?" Seems to me it should be 6.016 megapixels. > > The full sensor imaging area is 3040x2024 (6,152,960 pixels). Then, to summarize what has been posted so far:
Total number of pixels = 6.24 million
Full sensor imaging area = 6.15 million
Advertised full image size = 6.1 million
Actual stored image = 6.016 million
Do I have that correct? And does any of the above really matter except for the last number (3008 x 2000 full image size)?
Merritt
C J Campbell - 02 Jan 2005 22:21 GMT > > > The D70 resolution is 3008x2000 pixels. > > > [quoted text clipped - 9 lines] > And MY next question is "How does 3008x2000 equate to the advertised 6.1 > megapixels?" Seems to me it should be 6.016 megapixels. There are actually 6.24 million pixels on the sensor, of which 3008x2000 are used in the max size JPG or in raw NEF files, which Nikon rounds to 6.1 million pixels.
Merritt Mullen - 03 Jan 2005 05:59 GMT > "Merritt Mullen" <mmullen8014@mchsi.com> wrote in message
> > And MY next question is "How does 3008x2000 equate to the advertised 6.1 > > megapixels?" Seems to me it should be 6.016 megapixels.
> There are actually 6.24 million pixels on the sensor, of which 3008x2000 are > used in the max size JPG or in raw NEF files, which Nikon rounds to 6.1 > million pixels. Yes, I read that somewhere myself, but I still don't see how 3008 x 2000 = 6.016 million pixels "rounds" to 6.1 million pixels. Seems to me it rounds to 6.0 million pixels.
Can you clarify further?
Thanks,
Merritt
C J Campbell - 03 Jan 2005 12:38 GMT > > "Merritt Mullen" <mmullen8014@mchsi.com> wrote in message > [quoted text clipped - 10 lines] > > Can you clarify further? Nope. No doubt some lawyer will sue the camera companies for false advertising, claiming to represent all us consumers as a class. As part of the settlement, he will be paid millions of dollars, and we will get a coupon for $10 off on our next purchase of a camera. It will be hailed as "a great victory for consumers." At least, that is what happened to the manufacturers of disk drives and computer screens.
Alan Browne - 02 Jan 2005 16:41 GMT >>The D70 resolution is 3008x2000 pixels. >> [quoted text clipped - 5 lines] > > The answer to your next question is to allow lossless rotation of JPEGs :-) Lossless rotation can be maintained by merely keeping the number of pixels the same, eg: 3000 x 1500 -> 1500 x 3000 (or whatever dimesnions you please).
The 3008/16 is, as you imply, simply adopting the digital 'rounding' boundary that takes place with most digital devices.
Cheers, Alan
 Signature -- r.p.e.35mm user resource: http://www.aliasimages.com/rpe35mmur.htm -- r.p.d.slr-systems: http://www.aliasimages.com/rpdslrsysur.htm -- [SI] gallery & rulz: http://www.pbase.com/shootin -- e-meil: there's no such thing as a FreeLunch.
David J Taylor - 02 Jan 2005 16:52 GMT []
> Lossless rotation can be maintained by merely keeping the number of > pixels the same, eg: 3000 x 1500 -> 1500 x 3000 (or whatever > dimesnions you please). > The 3008/16 is, as you imply, simply adopting the digital 'rounding' > boundary that takes place with most digital devices. Alan, I think you will find that lossless rotation requires that the image dimensions be a multiple of 16 (and not 8 as I incorrectly stated earlier).
Cheers, David
Alan Browne - 02 Jan 2005 17:00 GMT > [] > [quoted text clipped - 7 lines] > dimensions be a multiple of 16 (and not 8 as I incorrectly stated > earlier). I fail to understand why. A matrix of 7 x 11 has the same quantity of information as a matrix of 11 x 7. Assuming the rotation is correctly done (and after conversion of individual R,G,B sensor to RGB pixels) then it makes no matter at all.
Cheers, Alan
 Signature -- r.p.e.35mm user resource: http://www.aliasimages.com/rpe35mmur.htm -- r.p.d.slr-systems: http://www.aliasimages.com/rpdslrsysur.htm -- [SI] gallery & rulz: http://www.pbase.com/shootin -- e-meil: there's no such thing as a FreeLunch.
David J Taylor - 02 Jan 2005 17:06 GMT >> [] >> [quoted text clipped - 12 lines] > correctly done (and after conversion of individual R,G,B sensor to > RGB pixels) then it makes no matter at all. If the image is JPEG, then the indivdual blocks are 16 x 16. The size quantisation restriction only applies to JPEG images, but of course almost all cameras do allow JPEG images as output.
If the image is not JPEG then it can, of course, be losslessly rotated at any size - as you say.
Cheers, David
John Bean - 02 Jan 2005 18:36 GMT >>> [] >>> [quoted text clipped - 19 lines] > If the image is not JPEG then it can, of course, be losslessly rotated at > any size - as you say. Thank you David, exactly correct :-)
 Signature John Bean
Why is it drug addicts and computer afficionados are both called users? (Clifford Stoll)
Alan Browne - 02 Jan 2005 19:23 GMT >>>Alan, I think you will find that lossless rotation requires that the >>>image dimensions be a multiple of 16 (and not 8 as I incorrectly [quoted text clipped - 11 lines] > If the image is not JPEG then it can, of course, be losslessly rotated at > any size - as you say. Now I'm really confused. Nothing prevents me from editing a JPG image to 1 pixel in either dimension. I can easilly come out with a 111 x 213 pixel image in JPG. From there, I can rotate it to 213 x 111 and it contains the same info. I can then save it at full quality. I've lost nothing.
Getting back on track, the reason we end up with 3008x2000, IMO, (D70, Maxxum 7d, et al) is that the hardware and software can be designed in even boundaries of 16 (or 8) and that is convenient to the engineers in terms of performace/$.
 Signature -- r.p.e.35mm user resource: http://www.aliasimages.com/rpe35mmur.htm -- r.p.d.slr-systems: http://www.aliasimages.com/rpdslrsysur.htm -- [SI] gallery & rulz: http://www.pbase.com/shootin -- e-meil: there's no such thing as a FreeLunch.
David J Taylor - 02 Jan 2005 19:42 GMT []
> Now I'm really confused. Nothing prevents me from editing a JPG > image to 1 pixel in either dimension. I can easilly come out with a > 111 x 213 pixel image in JPG. From there, I can rotate it to 213 x > 111 and it contains the same info. I can then save it at full > quality. I've lost nothing. If you save it as JPEG that will normally produce an extra loss compared to the original image. However, if you have a JPEG which is exactly a multiple of 16 in its X and Y dimension it can be losslessly rotated by 90 degrees.
Cheers, David
Alan Browne - 02 Jan 2005 20:27 GMT > [] > [quoted text clipped - 8 lines] > multiple of 16 in its X and Y dimension it can be losslessly rotated by 90 > degrees. I think I see what you're saying, though I don't know why truncation should affect the lossiness as the image is edited as an image not as a JPG. (JPG compression is a function of storage, not editing).
I also assume that at its least lossy setting JPG is lossless (which is not quite true, but close enough).
In terms of a RAW image it's a non-issue.
So, I believe the reason the engineers chose 3008:2000 is simply for the usual computer design reasons, not image related reasons. This also follows with the other saveable image sizes Maxxum 7d/Nikon d70: (2256x1496, 2240x1488, 1504x1000) ... 1496 and 1000 do not divide by 16, but all the dimensions mentioned divide by 8.
Cheers, Alan
 Signature -- r.p.e.35mm user resource: http://www.aliasimages.com/rpe35mmur.htm -- r.p.d.slr-systems: http://www.aliasimages.com/rpdslrsysur.htm -- [SI] gallery & rulz: http://www.pbase.com/shootin -- e-meil: there's no such thing as a FreeLunch.
John Bean - 02 Jan 2005 20:40 GMT >> [] >> [quoted text clipped - 12 lines] > affect the lossiness as the image is edited as an image not as a JPG. (JPG > compression is a function of storage, not editing). Lossless rotation is done on the JPEG data itself, not on a decoded image. The JPEG data is not decoded/rotated/re-encoded as it must be for any JPEG whose dimensions are not multiples of 16. That's why it's lossless.
> So, I believe the reason the engineers chose 3008:2000 is simply for the usual > computer design reasons, not image related reasons. Not so. As I said earlier the Pentax *istDS uses 3008x2008 for raw images but 3008x2000 for JPEG, for the reasons I've stated. This was a change from the older *istD, which used 3008x2008 for both - much to the annoyance of some users.
 Signature John Bean
Work is the curse of the drinking classes (Oscar Wilde)
John Francis - 02 Jan 2005 19:43 GMT >Now I'm really confused. Nothing prevents me from editing a JPG image to 1 >pixel in either dimension. I can easilly come out with a 111 x 213 pixel image >in JPG. From there, I can rotate it to 213 x 111 and it contains the same info. > I can then save it at full quality. I've lost nothing. Yes you have. If you don't save it as a JPG, you've lost the space savings. If you do re-save it as a JPG, you're going to re-run the compression algorithm. That's not being run on the same (original, uncompressed) image data that was the input to the first JPG compression, so it's extremely unlikely to come up with the same final result. That means you've lost some more image quality. The same holds true even if you don't rotate the image; you can still end up with a loss of quality just by re-saving a JPG image with no editing changes. That's why some image editing software checks for this case, and will simply copy the input file to the output in that situation.
Jeremy Nixon - 02 Jan 2005 20:31 GMT > Now I'm really confused. Nothing prevents me from editing a JPG image to 1 > pixel in either dimension. I can easilly come out with a 111 x 213 pixel > image in JPG. From there, I can rotate it to 213 x 111 and it contains the > same info. > I can then save it at full quality. I've lost nothing. Yes, you have, if you saved it as a JPEG. You have re-compressed the image. If you load a JPEG image, do something to it, and then save it again as a JPEG, that is a lossy operation due to the compression.
However, a JPEG image with dimensions divisible by 16 can be rotated without decompressing and recompressing the image at all -- that is, without ever loading it into an image editor in the first place, requiring no further step of re-saving as a JPEG and thus recompressing the data.
 Signature Jeremy | jeremy@exit109.com
Darrell - 02 Jan 2005 17:44 GMT > > [] > > [quoted text clipped - 12 lines] > after conversion of individual R,G,B sensor to RGB pixels) then it makes no > matter at all. Are the photosites in the sensor grid perfect squares? a 7x11 grid of rectangles is not the same 7x11 as it would be at 11x7
Alan Browne - 02 Jan 2005 19:27 GMT >>>[] >>> [quoted text clipped - 24 lines] > Are the photosites in the sensor grid perfect squares? a 7x11 grid of > rectangles is not the same 7x11 as it would be at 11x7 On the sensor in the D70 and Maxxum 7d I'm not sure they are really perfect squares. The data on dpreview suggests perhaps not. (pixel dimensions v. sensor dimensions. It's not clear what is 'cropped' by the camera when reading the device).
In the Canon 20D they do appear to be square..
 Signature -- r.p.e.35mm user resource: http://www.aliasimages.com/rpe35mmur.htm -- r.p.d.slr-systems: http://www.aliasimages.com/rpdslrsysur.htm -- [SI] gallery & rulz: http://www.pbase.com/shootin -- e-meil: there's no such thing as a FreeLunch.
Jeremy Nixon - 02 Jan 2005 20:29 GMT >> Alan, I think you will find that lossless rotation requires that the image >> dimensions be a multiple of 16 (and not 8 as I incorrectly stated [quoted text clipped - 4 lines] > done (and after conversion of individual R,G,B sensor to RGB pixels) > then it makes no matter at all. It matters for JPEGs, not for images in general. JPEGs can only be rotated losslessly (without decompressing and then recompressing the data) if the dimensions are divisible by 16.
 Signature Jeremy | jeremy@exit109.com
Alan Browne - 02 Jan 2005 20:37 GMT >>>Alan, I think you will find that lossless rotation requires that the image >>>dimensions be a multiple of 16 (and not 8 as I incorrectly stated [quoted text clipped - 8 lines] > rotated losslessly (without decompressing and then recompressing the > data) if the dimensions are divisible by 16. I'm beginning to understand that through the force of people saying so and not because I've looked at the mechanics.
You bring up 'uncompressing and recompressing' and that really is it... a JPG image is only such when stored. When it is 'in the camera' prior to storage or in photoshop it is not JPG... it is 'image'. So it can be rotated without loss regardless of dimensions. It's all semantics, I suppose.
Cheers, Alan.
 Signature -- r.p.e.35mm user resource: http://www.aliasimages.com/rpe35mmur.htm -- r.p.d.slr-systems: http://www.aliasimages.com/rpdslrsysur.htm -- [SI] gallery & rulz: http://www.pbase.com/shootin -- e-meil: there's no such thing as a FreeLunch.
Jeremy Nixon - 02 Jan 2005 21:18 GMT > You bring up 'uncompressing and recompressing' and that really is it... a JPG > image is only such when stored. When it is 'in the camera' prior to storage > or in photoshop it is not JPG... it is 'image'. So it can be rotated without > loss regardless of dimensions. It's all semantics, I suppose. The normal case is that someone takes a bunch of pictures, loads them onto his computer, looks at a screen full of thumbnails, and clicks a "rotate" button to make the vertical compositions vertical. If the saved images are JPEGs, this can be done with no recompression loss if the image dimensions are divisible by 16.
If you don't use JPEG, this doesn't matter to you.
 Signature Jeremy | jeremy@exit109.com
Ken Tough - 10 Jan 2005 17:36 GMT >I'm beginning to understand that through the force of people saying >so and not because I've looked at the mechanics.
>You bring up 'uncompressing and recompressing' and that really is it... a JPG >image is only such when stored. When it is 'in the camera' prior to storage or >in photoshop it is not JPG... it is 'image'. So it can be rotated without loss >regardless of dimensions. It's all semantics, I suppose. You're right, it's because of compressing, but no you don't understand it; it has nothing to do with semantics.
I'll have a stab at explaining it:
The original image comes out of the camera in JPG. That is lossy compression with effects; it has artifacts. For illustration, let's say that horizontal high-contrast areas cause a shadow in the lighter region.
You open that image (uncompressing it) in your viewer, and edit the pixels. What you're looking at has loss and artifacts. You do a pixel-for-pixel rotation (also duly rotating the artifacts). The result in your editing window, as you point out, is exactly the same as the original rotated.
Now, you save that edited image as JPG. The saving process compresses, and introduces new artifacts due to the new horizontal high-contrast areas (as well as the previous, rotated artifacts of course). This compression loses more info. When you open the newly formed JPG, it no longer looks exactly like the original, rotated. It's a lossless rotation only so long as you don't save it in JPG.
On the other hand, lossless rotation is a mathematical operation on the original JPG, effectively transforming it so that it uncompresses into a rotated version. There is no additional loss, no additional artifacts.
Hope that helps?
 Signature Ken Tough
leo - 02 Jan 2005 02:47 GMT > The D70 resolution is 3008x2000 pixels. > > What is the extra 8 pixels all about? > > Not that it matters I suppose, just curious. Why would you care? The Sony sensor used in the D70 doesn't have the 3:2 ratio anyway. A 35mm film is 36mmx24mm. Sony's chip is 23.7mmx15.6mm and that makes the crop factor comes out to somewhere between 1.519x and 1.538x. Just for comparison, Canon's sensor is 22.5mmx15mm which is exactly 1.6x.
Lourens Smak - 02 Jan 2005 14:59 GMT > > The D70 resolution is 3008x2000 pixels. > > [quoted text clipped - 7 lines] > 1.538x. Just for comparison, Canon's sensor is 22.5mmx15mm which is > exactly 1.6x. why post an answer if you are totally clueless?
Lourens
leo - 02 Jan 2005 18:05 GMT >>>The D70 resolution is 3008x2000 pixels. >>> [quoted text clipped - 11 lines] > > Lourens Why not. As the ratio indicates, there is more width info than height in the sensor (0.3mm wider). It might even translate into 8 pixels...
Roland Karlsson - 02 Jan 2005 18:44 GMT > Why not. As the ratio indicates, there is more width info than height in > the sensor (0.3mm wider). It might even translate into 8 pixels... The correct answer is already given. 3008 is possible to divide by 16. Thats it - nothing more to see here - please move along.
/Roland
Will D. - 03 Jan 2005 00:26 GMT >> Why not. As the ratio indicates, there is more width info than height in >> the sensor (0.3mm wider). It might even translate into 8 pixels... [quoted text clipped - 3 lines] > > /Roland Anyone ask to see Roland's badge number?
;)
Will D.
Roland Karlsson - 03 Jan 2005 18:28 GMT > Anyone ask to see Roland's badge number? Hehe ...
/Roland
|
|
|