<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Care for a Byte &#8211; Explaining Bits, Bytes and More</title>
	<atom:link href="http://digital-photography-school.com/care-for-a-byte-explaining-bits-bytes-and-more/feed" rel="self" type="application/rss+xml" />
	<link>http://digital-photography-school.com/care-for-a-byte-explaining-bits-bytes-and-more</link>
	<description>Discover how to use your digital camera with our Digital Photography Tips. We are a community of photographers of all experience levels who come together to learn, share and grow in our understanding of photography.</description>
	<lastBuildDate>Sat, 21 Nov 2009 12:17:12 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: John Gambino</title>
		<link>http://digital-photography-school.com/care-for-a-byte-explaining-bits-bytes-and-more/comment-page-1#comment-47027</link>
		<dc:creator>John Gambino</dc:creator>
		<pubDate>Wed, 08 Apr 2009 02:43:35 +0000</pubDate>
		<guid isPermaLink="false">http://digital-photography-school.com/?p=5069#comment-47027</guid>
		<description>My previous post was refered to Jeffrey Kontur&#039;s comment. 

and I just wanted to add, that I actualy find jeffrey&#039;s post (1 before that) most educating and interesting. Although it was a bit harsh of him to start with words &quot;I’d say that this article fails&quot; :) 
Nevertheless, If someone knows better, they should talk so we can learn from it. That what I think.</description>
		<content:encoded><![CDATA[<p>My previous post was refered to Jeffrey Kontur&#8217;s comment. </p>
<p>and I just wanted to add, that I actualy find jeffrey&#8217;s post (1 before that) most educating and interesting. Although it was a bit harsh of him to start with words &#8220;I’d say that this article fails&#8221; :)<br />
Nevertheless, If someone knows better, they should talk so we can learn from it. That what I think.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Gambino</title>
		<link>http://digital-photography-school.com/care-for-a-byte-explaining-bits-bytes-and-more/comment-page-1#comment-47026</link>
		<dc:creator>John Gambino</dc:creator>
		<pubDate>Wed, 08 Apr 2009 02:39:03 +0000</pubDate>
		<guid isPermaLink="false">http://digital-photography-school.com/?p=5069#comment-47026</guid>
		<description>Well, Jeffery, It is not nitpicking.  80gig drive holds 75gigs of data, thats the fact that we all knew already. But the author was trying to explain WHY it is so. Information given to us was incorrect, so why not correct it? 

I don&#039;t see anything wrong with getting facts straight. I see a different issue: This info was not given to us as a authors guess, or opinion. It was given like a pure truth, which is wasn&#039;t. That worries me a little as for quality of other info, advice, explanation I am getting here. So it si a good reality check. While this site is extremely good and helpfull, I think its very important that we all get smarter and educated by getting the proper info.  You dont have to get deep into math, computer science, or nuclear disbalance chemistry, but no reason to expain things wrong way. It wont benefit newbies, and will turn off the pros. IMHO, anyway. No disrespect or offence meant to anyone.</description>
		<content:encoded><![CDATA[<p>Well, Jeffery, It is not nitpicking.  80gig drive holds 75gigs of data, thats the fact that we all knew already. But the author was trying to explain WHY it is so. Information given to us was incorrect, so why not correct it? </p>
<p>I don&#8217;t see anything wrong with getting facts straight. I see a different issue: This info was not given to us as a authors guess, or opinion. It was given like a pure truth, which is wasn&#8217;t. That worries me a little as for quality of other info, advice, explanation I am getting here. So it si a good reality check. While this site is extremely good and helpfull, I think its very important that we all get smarter and educated by getting the proper info.  You dont have to get deep into math, computer science, or nuclear disbalance chemistry, but no reason to expain things wrong way. It wont benefit newbies, and will turn off the pros. IMHO, anyway. No disrespect or offence meant to anyone.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 0rovert</title>
		<link>http://digital-photography-school.com/care-for-a-byte-explaining-bits-bytes-and-more/comment-page-1#comment-46904</link>
		<dc:creator>0rovert</dc:creator>
		<pubDate>Mon, 06 Apr 2009 16:15:12 +0000</pubDate>
		<guid isPermaLink="false">http://digital-photography-school.com/?p=5069#comment-46904</guid>
		<description>I got this from another site, but it made me laugh.  Thanks to Ilan for the inspiration.

010000100110010100100000011100110111010101110010011001
010010000001110100011011110010000001100100011100100110
100101101110011010110010000001111001011011110111010101
110010001000000100111101110110011000010110110001110100
01101001011011100110010100101110</description>
		<content:encoded><![CDATA[<p>I got this from another site, but it made me laugh.  Thanks to Ilan for the inspiration.</p>
<p>010000100110010100100000011100110111010101110010011001<br />
010010000001110100011011110010000001100100011100100110<br />
100101101110011010110010000001111001011011110111010101<br />
110010001000000100111101110110011000010110110001110100<br />
01101001011011100110010100101110</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeffrey Kontur</title>
		<link>http://digital-photography-school.com/care-for-a-byte-explaining-bits-bytes-and-more/comment-page-1#comment-46893</link>
		<dc:creator>Jeffrey Kontur</dc:creator>
		<pubDate>Mon, 06 Apr 2009 13:13:37 +0000</pubDate>
		<guid isPermaLink="false">http://digital-photography-school.com/?p=5069#comment-46893</guid>
		<description>I find it disheartening that most everyone who has commented seems to be nitpicking details of measurement and overlooking one of the primary intentions of the post. Regardless whether your drive is truly 80GB or only &quot;nominally&quot; 80GB, understanding bit-depth as it applies to photography is the most relevant issue here. I think it was pretty well explained, though full understanding does require some prior technical knowledge.

Given that this is such a technical and complex topic, I think it was very well summarized in such a short post.</description>
		<content:encoded><![CDATA[<p>I find it disheartening that most everyone who has commented seems to be nitpicking details of measurement and overlooking one of the primary intentions of the post. Regardless whether your drive is truly 80GB or only &#8220;nominally&#8221; 80GB, understanding bit-depth as it applies to photography is the most relevant issue here. I think it was pretty well explained, though full understanding does require some prior technical knowledge.</p>
<p>Given that this is such a technical and complex topic, I think it was very well summarized in such a short post.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeffrey</title>
		<link>http://digital-photography-school.com/care-for-a-byte-explaining-bits-bytes-and-more/comment-page-1#comment-46870</link>
		<dc:creator>Jeffrey</dc:creator>
		<pubDate>Mon, 06 Apr 2009 05:23:52 +0000</pubDate>
		<guid isPermaLink="false">http://digital-photography-school.com/?p=5069#comment-46870</guid>
		<description>@Bruce&#039;s answer is the most correct - dan and Chris&#039;s previous comments were both technically correct, but have different impacts

I&#039;d say that this article fails to go over the importance of 12-bit and 14-bit images. The JPEG implementation that most computers use usually only does 8-bit images (AFAIK). You get 12 and 14 bit images from shooting in RAW. The nice thing about 12-14 bit images is that you get a better _dynamic range_. Although you might not get a wider range (someone verify this?) you&#039;ll definitely get a finer gradiation/steps between each color that can make all the difference in post processing. For example - say something is majorly underexposed. When you up the exposure in post, 12-14 bit images offer you 16-64 times more colors, so you&#039;ll probably be able to extract more detail. =]</description>
		<content:encoded><![CDATA[<p>@Bruce&#8217;s answer is the most correct &#8211; dan and Chris&#8217;s previous comments were both technically correct, but have different impacts</p>
<p>I&#8217;d say that this article fails to go over the importance of 12-bit and 14-bit images. The JPEG implementation that most computers use usually only does 8-bit images (AFAIK). You get 12 and 14 bit images from shooting in RAW. The nice thing about 12-14 bit images is that you get a better _dynamic range_. Although you might not get a wider range (someone verify this?) you&#8217;ll definitely get a finer gradiation/steps between each color that can make all the difference in post processing. For example &#8211; say something is majorly underexposed. When you up the exposure in post, 12-14 bit images offer you 16-64 times more colors, so you&#8217;ll probably be able to extract more detail. =]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bruce</title>
		<link>http://digital-photography-school.com/care-for-a-byte-explaining-bits-bytes-and-more/comment-page-1#comment-46866</link>
		<dc:creator>Bruce</dc:creator>
		<pubDate>Mon, 06 Apr 2009 04:35:01 +0000</pubDate>
		<guid isPermaLink="false">http://digital-photography-school.com/?p=5069#comment-46866</guid>
		<description>Actually, both dan and Chris/chrisc are correct, but the impact is different.

A hard drive that is marketed as being &quot;500GB&quot; is in fact roughly 500,000,000,000 bytes in size, thus using the &quot;metric&quot; giga meaning 1,000,000,000.  This is roughly 465 of the &quot;computer&quot; gigabytes, as described in the article.

However, that space is allocated in sectors (typically 512 bytes), and organized by the operating system into blocks, which are usually 4kB (so eight sectors).  As dan indicates, every file is allocated in terms of these blocks, so there is an average of 2kB of wasted space per file.  However, this wasted space is not a consideration when discussing the total drive capacity.

There are a number of tables on the disk that are used by the operating system to actually locate the correct blocks, which does reduce the available space or capacity.  In the grand scheme of things, however, the difference between metric or hard drive marketing GB (1,000,000,000 bytes) and computer or binary GB (1,073,741,824 bytes) is much larger than the amount of disk space consumed by these tables.

The question is a good one to answer, as there is frequently confusion when people ask why their drive is smaller than advertised, but a better answer than what is in the article would be beneficial.</description>
		<content:encoded><![CDATA[<p>Actually, both dan and Chris/chrisc are correct, but the impact is different.</p>
<p>A hard drive that is marketed as being &#8220;500GB&#8221; is in fact roughly 500,000,000,000 bytes in size, thus using the &#8220;metric&#8221; giga meaning 1,000,000,000.  This is roughly 465 of the &#8220;computer&#8221; gigabytes, as described in the article.</p>
<p>However, that space is allocated in sectors (typically 512 bytes), and organized by the operating system into blocks, which are usually 4kB (so eight sectors).  As dan indicates, every file is allocated in terms of these blocks, so there is an average of 2kB of wasted space per file.  However, this wasted space is not a consideration when discussing the total drive capacity.</p>
<p>There are a number of tables on the disk that are used by the operating system to actually locate the correct blocks, which does reduce the available space or capacity.  In the grand scheme of things, however, the difference between metric or hard drive marketing GB (1,000,000,000 bytes) and computer or binary GB (1,073,741,824 bytes) is much larger than the amount of disk space consumed by these tables.</p>
<p>The question is a good one to answer, as there is frequently confusion when people ask why their drive is smaller than advertised, but a better answer than what is in the article would be beneficial.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan</title>
		<link>http://digital-photography-school.com/care-for-a-byte-explaining-bits-bytes-and-more/comment-page-1#comment-46829</link>
		<dc:creator>Dan</dc:creator>
		<pubDate>Sun, 05 Apr 2009 19:21:01 +0000</pubDate>
		<guid isPermaLink="false">http://digital-photography-school.com/?p=5069#comment-46829</guid>
		<description>No, sectors are relevant. Think of a formatted hard drive as being like a spiral-bound notepad. Each page is represents a sector on the drive. Every time you save a file, it starts on a new page. If the file is bigger than the page, it spills over to the next one. However, any empty space between the end of the file and the end of the page can&#039;t be used for a new file, it&#039;s effectively &quot;dead space&quot;, until you delete the file and free up the whole sector again. A sector on a hard drive might be 4K in size, so if you write out that shopping list in notepad and save it, it may only take up 2% of the sector. The other 98% can&#039;t be used at all until you delete the shopping list. It may say in explorer that the shopping list is 1K in size, but it&#039;s actually using up 4K of disc space.</description>
		<content:encoded><![CDATA[<p>No, sectors are relevant. Think of a formatted hard drive as being like a spiral-bound notepad. Each page is represents a sector on the drive. Every time you save a file, it starts on a new page. If the file is bigger than the page, it spills over to the next one. However, any empty space between the end of the file and the end of the page can&#8217;t be used for a new file, it&#8217;s effectively &#8220;dead space&#8221;, until you delete the file and free up the whole sector again. A sector on a hard drive might be 4K in size, so if you write out that shopping list in notepad and save it, it may only take up 2% of the sector. The other 98% can&#8217;t be used at all until you delete the shopping list. It may say in explorer that the shopping list is 1K in size, but it&#8217;s actually using up 4K of disc space.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dante</title>
		<link>http://digital-photography-school.com/care-for-a-byte-explaining-bits-bytes-and-more/comment-page-1#comment-46788</link>
		<dc:creator>Dante</dc:creator>
		<pubDate>Sun, 05 Apr 2009 07:43:00 +0000</pubDate>
		<guid isPermaLink="false">http://digital-photography-school.com/?p=5069#comment-46788</guid>
		<description>What chrisc said. You should delete that sectors nonsense in the article. Formatting only accounts for a small percentage of the apparent loss.</description>
		<content:encoded><![CDATA[<p>What chrisc said. You should delete that sectors nonsense in the article. Formatting only accounts for a small percentage of the apparent loss.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dcclark</title>
		<link>http://digital-photography-school.com/care-for-a-byte-explaining-bits-bytes-and-more/comment-page-1#comment-46779</link>
		<dc:creator>dcclark</dc:creator>
		<pubDate>Sun, 05 Apr 2009 00:30:09 +0000</pubDate>
		<guid isPermaLink="false">http://digital-photography-school.com/?p=5069#comment-46779</guid>
		<description>And here&#039;s a useful connection: 1 megapixel = 1 million pixels (as opposed to 2^20, which is slightly more -- &quot;mega&quot; usually means &quot;million&quot; in everyday computer usage), and each pixel typically is recorded with 8 bits of information. That makes for 24 bits (= 3 bytes) of information per pixel, so the &lt;i&gt;uncompressed&lt;/i&gt; size of your 10 MP image is 10,000,000 * 3 = 30,000,000 bytes = 28 megabytes (approximately -- there is usually a little more information included, such as exposure data). This is why your images shot in raw format are so huge! On the other hand, images converted to jpegs are considerably smaller, because &lt;i&gt;not&lt;/i&gt; every single pixel is recorder -- rather, big swaths of (approximately) the same color are recorded all together. This is why jpegs are smaller, but also why they can look worse if you compress them too much -- too many &quot;similar&quot; colors get compressed into just a single color.

Anyhow, that&#039;s a connection between bits, bytes, and megapixels. Enjoy!</description>
		<content:encoded><![CDATA[<p>And here&#8217;s a useful connection: 1 megapixel = 1 million pixels (as opposed to 2^20, which is slightly more &#8212; &#8220;mega&#8221; usually means &#8220;million&#8221; in everyday computer usage), and each pixel typically is recorded with 8 bits of information. That makes for 24 bits (= 3 bytes) of information per pixel, so the <i>uncompressed</i> size of your 10 MP image is 10,000,000 * 3 = 30,000,000 bytes = 28 megabytes (approximately &#8212; there is usually a little more information included, such as exposure data). This is why your images shot in raw format are so huge! On the other hand, images converted to jpegs are considerably smaller, because <i>not</i> every single pixel is recorder &#8212; rather, big swaths of (approximately) the same color are recorded all together. This is why jpegs are smaller, but also why they can look worse if you compress them too much &#8212; too many &#8220;similar&#8221; colors get compressed into just a single color.</p>
<p>Anyhow, that&#8217;s a connection between bits, bytes, and megapixels. Enjoy!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ChrisC</title>
		<link>http://digital-photography-school.com/care-for-a-byte-explaining-bits-bytes-and-more/comment-page-1#comment-46776</link>
		<dc:creator>ChrisC</dc:creator>
		<pubDate>Sat, 04 Apr 2009 23:42:52 +0000</pubDate>
		<guid isPermaLink="false">http://digital-photography-school.com/?p=5069#comment-46776</guid>
		<description>The reduction in size isn&#039;t because of sectors, it&#039;s purely due to marketing being deceptive.

A 2GB drive that you buy will typically be very close to 2,000,000,000 bytes, which is actually only 1.86GB, properly counted (1.86* 1024 * 1024 * 1024).  The manufacturers use 1000 rather than 1024 to artificially inflate advertised drive prices.</description>
		<content:encoded><![CDATA[<p>The reduction in size isn&#8217;t because of sectors, it&#8217;s purely due to marketing being deceptive.</p>
<p>A 2GB drive that you buy will typically be very close to 2,000,000,000 bytes, which is actually only 1.86GB, properly counted (1.86* 1024 * 1024 * 1024).  The manufacturers use 1000 rather than 1024 to artificially inflate advertised drive prices.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
