<?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/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"	>
<channel>
	<title>Comments on: Is JPEG Good Enough for Archival Masters?</title>
	<atom:link href="http://dltj.org/article/jpeg-as-master/feed/" rel="self" type="application/rss+xml" />
	<link>http://dltj.org/article/jpeg-as-master/</link>
	<description>We&#039;re Disrupted, We&#039;re Librarians, and We&#039;re Not Going to Take It Anymore</description>
	<lastBuildDate>Thu, 02 Sep 2010 08:58:34 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Mining Metadata &#187; JPEG and Archives</title>
		<link>http://dltj.org/article/jpeg-as-master/comment-page-1/#comment-31731</link>
		<dc:creator>Mining Metadata &#187; JPEG and Archives</dc:creator>
		<pubDate>Fri, 29 Feb 2008 12:28:27 +0000</pubDate>
		<guid isPermaLink="false">http://dltj.org/article/jpeg-as-master/#comment-31731</guid>
		<description>[...] http://dltj.org/article/jpeg-as-master/ [...]</description>
		<content:encoded><![CDATA[<p>[...] <a href="http://dltj.org/article/jpeg-as-master/" rel="nofollow">http://dltj.org/article/jpeg-as-master/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Re: All generalizations are wrong...: Nikon D300/D200/D100 Forum: Digital Photography Review</title>
		<link>http://dltj.org/article/jpeg-as-master/comment-page-1/#comment-31292</link>
		<dc:creator>Re: All generalizations are wrong...: Nikon D300/D200/D100 Forum: Digital Photography Review</dc:creator>
		<pubDate>Thu, 21 Feb 2008 15:54:10 +0000</pubDate>
		<guid isPermaLink="false">http://dltj.org/article/jpeg-as-master/#comment-31292</guid>
		<description>&lt;!--%kramer-ref-pre%--&gt;[...] As to the issue of using JPEG for &quot;definitive&quot; storage of image data, here&#039;s a link to a discussion on that point which is currently going on among archivists: http://dltj.org/article/jpeg-as-master/ [...]&lt;!--%kramer-ref-post%--&gt;</description>
		<content:encoded><![CDATA[<p><a href="http://dev.wp-plugins.org/wiki/Kramer"><img src="http://dltj.org/wp-content/plugins/kramer/kramer.php?kramer=gif-icon" class="technorati-balloon" alt="Kramer auto Pingback" style="border:0;" /></a>[...] As to the issue of using JPEG for &#8220;definitive&#8221; storage of image data, here&#8217;s a link to a discussion on that point which is currently going on among archivists: <a href="http://dltj.org/article/jpeg-as-master/" rel="nofollow">http://dltj.org/article/jpeg-as-master/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: the Jester</title>
		<link>http://dltj.org/article/jpeg-as-master/comment-page-1/#comment-30919</link>
		<dc:creator>the Jester</dc:creator>
		<pubDate>Fri, 15 Feb 2008 00:19:58 +0000</pubDate>
		<guid isPermaLink="false">http://dltj.org/article/jpeg-as-master/#comment-30919</guid>
		<description>Howard,

The full version of Ken Fleisher&#039;s recommendation, recently added to the text of this posting above, does acknowledge the benefit of TIFF over JPEG for greater-than-8-bit-depth images: &lt;blockquote&gt;Higher bit-depth is really the only advantage of using TIFF over JPEG 10 or 12 (in terms of image quality). &lt;/blockquote&gt;

The recommendation also says that JPEG is appropriate for terminal copies (my phrase, the text says &quot;and if they do not require much pixel editing before use&quot;).  I think, in other words, no further transformations are expected.</description>
		<content:encoded><![CDATA[<p>Howard,</p>
<p>The full version of Ken Fleisher&#8217;s recommendation, recently added to the text of this posting above, does acknowledge the benefit of TIFF over JPEG for greater-than-8-bit-depth images:<br />
<blockquote>Higher bit-depth is really the only advantage of using TIFF over JPEG 10 or 12 (in terms of image quality). </p></blockquote>
<p>The recommendation also says that JPEG is appropriate for terminal copies (my phrase, the text says &#8220;and if they do not require much pixel editing before use&#8221;).  I think, in other words, no further transformations are expected.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Howard Brainen</title>
		<link>http://dltj.org/article/jpeg-as-master/comment-page-1/#comment-30906</link>
		<dc:creator>Howard Brainen</dc:creator>
		<pubDate>Thu, 14 Feb 2008 18:46:45 +0000</pubDate>
		<guid isPermaLink="false">http://dltj.org/article/jpeg-as-master/#comment-30906</guid>
		<description>I have no problem with JPEG as a proper format as a &quot;delivery spec.&quot;  But I can&#039;t recommend archiving any image file that started life with more than 8 bits per channel as a JPEG.  Those extra bits often contain significant amounts of useful information. One needs to save as much information as possible because some of it will be lost when files are later delivered for various outputs.</description>
		<content:encoded><![CDATA[<p>I have no problem with JPEG as a proper format as a &#8220;delivery spec.&#8221;  But I can&#8217;t recommend archiving any image file that started life with more than 8 bits per channel as a JPEG.  Those extra bits often contain significant amounts of useful information. One needs to save as much information as possible because some of it will be lost when files are later delivered for various outputs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Digitization 101: Blog post: Is JPEG Good Enough for Archival Masters?</title>
		<link>http://dltj.org/article/jpeg-as-master/comment-page-1/#comment-30844</link>
		<dc:creator>Digitization 101: Blog post: Is JPEG Good Enough for Archival Masters?</dc:creator>
		<pubDate>Wed, 13 Feb 2008 19:43:12 +0000</pubDate>
		<guid isPermaLink="false">http://dltj.org/article/jpeg-as-master/#comment-30844</guid>
		<description>&lt;!--%kramer-ref-pre%--&gt;[...] Blog post: Is JPEG Good Enough for Archival Masters? [...]&lt;!--%kramer-ref-post%--&gt;</description>
		<content:encoded><![CDATA[<p><a href="http://dev.wp-plugins.org/wiki/Kramer"><img src="http://dltj.org/wp-content/plugins/kramer/kramer.php?kramer=gif-icon" class="technorati-balloon" alt="Kramer auto Pingback" style="border:0;" /></a>[...] Blog post: Is JPEG Good Enough for Archival Masters? [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: the Jester</title>
		<link>http://dltj.org/article/jpeg-as-master/comment-page-1/#comment-30728</link>
		<dc:creator>the Jester</dc:creator>
		<pubDate>Mon, 11 Feb 2008 18:13:53 +0000</pubDate>
		<guid isPermaLink="false">http://dltj.org/article/jpeg-as-master/#comment-30728</guid>
		<description>Ken --

For me, the key part of your reply was: &lt;blockquote&gt;I feel that JPEG should not be disregarded as a delivery format because it�s perceived as &quot;lossy&quot;.&lt;/blockquote&gt;  I, for one, and just coming to terms with the concept of &quot;visually lossless&quot; and its associated consequences as a practice for terminal (e.g. archival) copies.  It is, of course, much easier to say &quot;JPEG is a lossy compression method, therefore it should not be used for archival copies.&quot;  It is much harder to give the nuanced argument, as you did with your example comparing a TIFF with its corresponding JPEG quality 12 instance.  (I almost used the word &quot;derivative&quot; instead of &quot;instance&quot; -- demonstrating that I&#039;m still struggling internally with the nuanced argument.)

I do not want to give a misleading impression to anyone who comes upon this post, so I&#039;ve updated the text of the main posting with the full paragraph from the UPDIG site.  Thanks for offering your perspective and setting the record straight.</description>
		<content:encoded><![CDATA[<p>Ken &#8211;</p>
<p>For me, the key part of your reply was:<br />
<blockquote>I feel that JPEG should not be disregarded as a delivery format because it�s perceived as &#8220;lossy&#8221;.</p></blockquote>
<p>  I, for one, and just coming to terms with the concept of &#8220;visually lossless&#8221; and its associated consequences as a practice for terminal (e.g. archival) copies.  It is, of course, much easier to say &#8220;JPEG is a lossy compression method, therefore it should not be used for archival copies.&#8221;  It is much harder to give the nuanced argument, as you did with your example comparing a TIFF with its corresponding JPEG quality 12 instance.  (I almost used the word &#8220;derivative&#8221; instead of &#8220;instance&#8221; &#8212; demonstrating that I&#8217;m still struggling internally with the nuanced argument.)</p>
<p>I do not want to give a misleading impression to anyone who comes upon this post, so I&#8217;ve updated the text of the main posting with the full paragraph from the UPDIG site.  Thanks for offering your perspective and setting the record straight.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ken Fleisher</title>
		<link>http://dltj.org/article/jpeg-as-master/comment-page-1/#comment-30567</link>
		<dc:creator>Ken Fleisher</dc:creator>
		<pubDate>Fri, 08 Feb 2008 16:40:42 +0000</pubDate>
		<guid isPermaLink="false">http://dltj.org/article/jpeg-as-master/#comment-30567</guid>
		<description>Upon reviewing my documents, I realize that my comments on JPEG as an archiving format were not taken out of context. I made the recommendation for both a delivery format and (conditionally) as an archiving format. However, the quoted text above was truncated before the qualifying statements, which essentially restate my comments from my last post. The full text on the UPDIG site reads:

&quot;Archiving JPEG files: Conventional wisdom holds that the TIFF format holds a quality advantage over the JPEG format. This holds true only if the JPEG file is saved at less than 10 quality using the Photoshop standard. When using JPEG quality 10 or 12, the artifacts are either non-existent or insignificant. Higher bit-depth is really the only advantage of using TIFF over JPEG 10 or 12 (in terms of image quality). Some have argued that that JPEG, because of the way it encodes data, compromises color. This is a misconception. When using the highest quality settings, there is no loss of color fidelity. Therefore, if JPEG files are saved at 10-12 quality, and if they do not require much pixel editing before use, archiving JPEG files is not a bad concept, and it can save a lot of space. For many picture archives, the economics of storing large numbers of files dominates all other considerations, and JPEG offers a feasible solution to the problem.&quot;

This relates the ideas that 1) the image is already edited or does not require significant editing, 2) that only the highest JPEG quality levels are used, and 3) that the solution is not for everybody but when appropriate, it can have certain advantages--namely significant space savings (translates to &quot;cost savings&quot; for most of us). Given these qualifying statements, I don&#039;t feel the text requires any changes.

Also after re-reading the original message, I believe that for most professional uses, JPEG (with stated constraints) should be a viable solution. For scientific uses where introduction of any compounding error can distort experimental results, JPEG is clearly not a solution. But since these errors are so small (most are less than plus or minus 2), they simply will not be visible in most cases (large gamut color spaces noted as an exception, but even then the errors are only &quot;slightly&quot; visible and only if you look for them). I&#039;m not saying that errors aren&#039;t introduced, but they truly are insignificant.</description>
		<content:encoded><![CDATA[<p>Upon reviewing my documents, I realize that my comments on JPEG as an archiving format were not taken out of context. I made the recommendation for both a delivery format and (conditionally) as an archiving format. However, the quoted text above was truncated before the qualifying statements, which essentially restate my comments from my last post. The full text on the UPDIG site reads:</p>
<p>&#8220;Archiving JPEG files: Conventional wisdom holds that the TIFF format holds a quality advantage over the JPEG format. This holds true only if the JPEG file is saved at less than 10 quality using the Photoshop standard. When using JPEG quality 10 or 12, the artifacts are either non-existent or insignificant. Higher bit-depth is really the only advantage of using TIFF over JPEG 10 or 12 (in terms of image quality). Some have argued that that JPEG, because of the way it encodes data, compromises color. This is a misconception. When using the highest quality settings, there is no loss of color fidelity. Therefore, if JPEG files are saved at 10-12 quality, and if they do not require much pixel editing before use, archiving JPEG files is not a bad concept, and it can save a lot of space. For many picture archives, the economics of storing large numbers of files dominates all other considerations, and JPEG offers a feasible solution to the problem.&#8221;</p>
<p>This relates the ideas that 1) the image is already edited or does not require significant editing, 2) that only the highest JPEG quality levels are used, and 3) that the solution is not for everybody but when appropriate, it can have certain advantages&#8211;namely significant space savings (translates to &#8220;cost savings&#8221; for most of us). Given these qualifying statements, I don&#8217;t feel the text requires any changes.</p>
<p>Also after re-reading the original message, I believe that for most professional uses, JPEG (with stated constraints) should be a viable solution. For scientific uses where introduction of any compounding error can distort experimental results, JPEG is clearly not a solution. But since these errors are so small (most are less than plus or minus 2), they simply will not be visible in most cases (large gamut color spaces noted as an exception, but even then the errors are only &#8220;slightly&#8221; visible and only if you look for them). I&#8217;m not saying that errors aren&#8217;t introduced, but they truly are insignificant.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ken Fleisher</title>
		<link>http://dltj.org/article/jpeg-as-master/comment-page-1/#comment-30513</link>
		<dc:creator>Ken Fleisher</dc:creator>
		<pubDate>Thu, 07 Feb 2008 19:27:07 +0000</pubDate>
		<guid isPermaLink="false">http://dltj.org/article/jpeg-as-master/#comment-30513</guid>
		<description>Thank you for pointing me to this discussion. It appears as if my comments about JPEG were attached to the wrong section and I had not caught this. (I will see about having this fixed on the UPDIG site, or at least clarified.) My original comments were in response to the JPEG vs. TIFF issue with respect to image quality in the context of a &quot;Delivery Spec&quot;, not as an archival master. I do feel that a JPEG saved at Photoshop&#039;s level 10 or 12 is a perfectly reasonable delivery format and not inferior to TIFF for a number of reasons. Particularly, I feel that JPEG should not be disregarded as a delivery format because it&#039;s perceived as &quot;lossy&quot;.

That said, I do also feel that in some situations, though certainly not all, JPEG &quot;could&quot; be appropriate as an archival format as well. Take this example:

I took an image capture of a painting (color corrected, sharpened, etc., and then downsampled to 8-bit/channel). I saved one version as TIFF and one as JPEG quality 12, baseline optimized. I get the following results when I compare the difference between the two files:

17,020,752 total pixels in the image

(RED channel histogram values listed, but similar numbers for GREEN and BLUE channels)
8-BIT DIFFERENCE LEVEL - # Pixels
0 - 7,438,696
1 - 8,128,655
2 - 1,375,457
3 - 75,734
4 - 2,173
5 - 37
6 - 0
7 - 0
etc.

Typical camera noise for digital cameras is on the order of 2.5% and follows a gaussian distribution. (This is a gross over-simplification of noise, but is sufficient for this discussion.) That means we can expect 8-bit pixel values to vary by a maximum of plus or minus 6 pixels, with a standard deviation of about 1.5 - 2 pixels. In other words, based on noise characteristics, we can expect our image captures to have errors of plus or minus &quot;2&quot; for 2/3 of the pixels, with errors no larger than 6. Although the example does not exactly fit this model, it should be clear that the errors introduced by saving as JPEG are very close to being on the order of typical image capture noise.  Errors such as this will be visually lossless in most cases. An exception might be if using a colorspace such as ProPhoto RGB, then there may be &quot;very&quot; slight visual differences. Therefore, I believe that in some cases where it is not necessary to save the raw camera capture, JPEG can be used instead of TIFF for archival purposes. Stated another way, a JPEG file saved as above does not add any more distortion than typical camera noise. As long as the effect (which is admittedly compounded with the camera noise) is not visible, then why is this any worse of an archive file? I&#039;ll stress again, this depends highly on the application and purpose of the archive you are creating, but I do see it as a plausible format for some cases.</description>
		<content:encoded><![CDATA[<p>Thank you for pointing me to this discussion. It appears as if my comments about JPEG were attached to the wrong section and I had not caught this. (I will see about having this fixed on the UPDIG site, or at least clarified.) My original comments were in response to the JPEG vs. TIFF issue with respect to image quality in the context of a &#8220;Delivery Spec&#8221;, not as an archival master. I do feel that a JPEG saved at Photoshop&#8217;s level 10 or 12 is a perfectly reasonable delivery format and not inferior to TIFF for a number of reasons. Particularly, I feel that JPEG should not be disregarded as a delivery format because it&#8217;s perceived as &#8220;lossy&#8221;.</p>
<p>That said, I do also feel that in some situations, though certainly not all, JPEG &#8220;could&#8221; be appropriate as an archival format as well. Take this example:</p>
<p>I took an image capture of a painting (color corrected, sharpened, etc., and then downsampled to 8-bit/channel). I saved one version as TIFF and one as JPEG quality 12, baseline optimized. I get the following results when I compare the difference between the two files:</p>
<p>17,020,752 total pixels in the image</p>
<p>(RED channel histogram values listed, but similar numbers for GREEN and BLUE channels)<br />
8-BIT DIFFERENCE LEVEL &#8211; # Pixels<br />
0 &#8211; 7,438,696<br />
1 &#8211; 8,128,655<br />
2 &#8211; 1,375,457<br />
3 &#8211; 75,734<br />
4 &#8211; 2,173<br />
5 &#8211; 37<br />
6 &#8211; 0<br />
7 &#8211; 0<br />
etc.</p>
<p>Typical camera noise for digital cameras is on the order of 2.5% and follows a gaussian distribution. (This is a gross over-simplification of noise, but is sufficient for this discussion.) That means we can expect 8-bit pixel values to vary by a maximum of plus or minus 6 pixels, with a standard deviation of about 1.5 &#8211; 2 pixels. In other words, based on noise characteristics, we can expect our image captures to have errors of plus or minus &#8220;2&#8243; for 2/3 of the pixels, with errors no larger than 6. Although the example does not exactly fit this model, it should be clear that the errors introduced by saving as JPEG are very close to being on the order of typical image capture noise.  Errors such as this will be visually lossless in most cases. An exception might be if using a colorspace such as ProPhoto RGB, then there may be &#8220;very&#8221; slight visual differences. Therefore, I believe that in some cases where it is not necessary to save the raw camera capture, JPEG can be used instead of TIFF for archival purposes. Stated another way, a JPEG file saved as above does not add any more distortion than typical camera noise. As long as the effect (which is admittedly compounded with the camera noise) is not visible, then why is this any worse of an archive file? I&#8217;ll stress again, this depends highly on the application and purpose of the archive you are creating, but I do see it as a plausible format for some cases.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob Lancefield</title>
		<link>http://dltj.org/article/jpeg-as-master/comment-page-1/#comment-30457</link>
		<dc:creator>Rob Lancefield</dc:creator>
		<pubDate>Wed, 06 Feb 2008 18:24:02 +0000</pubDate>
		<guid isPermaLink="false">http://dltj.org/article/jpeg-as-master/#comment-30457</guid>
		<description>And three quick followups:

- another key framing factor is the likelihood that in the coming decades, a growing number of born-digital images initially (and long-) managed by photographers will subsequently enter into public collections, and that encouragement towards better practices (when truly best practices may be unattainable) during those earlier phases of personal image stewardship potentially has wider, long-term benefits.

- one promising avenue for building connections between the library community and UPDIG may be the Preserving Digital Images initiative of the American Society of Media Photographers, undertaken with Library of Congress support via the National Digital Information Infrastructure and Preservation Program (NDIIPP); http://www.asmp.org/pdi/index.php has more on the &quot;ASMP-PDI,&quot; as it&#039;s known.

- repository-focused work linked to UPDIG in some other key ways is happening under the auspices of ImageMuse (http://imagemuse.org).

And with that, I&#039;ll stop for real. Promise.</description>
		<content:encoded><![CDATA[<p>And three quick followups:</p>
<p>- another key framing factor is the likelihood that in the coming decades, a growing number of born-digital images initially (and long-) managed by photographers will subsequently enter into public collections, and that encouragement towards better practices (when truly best practices may be unattainable) during those earlier phases of personal image stewardship potentially has wider, long-term benefits.</p>
<p>- one promising avenue for building connections between the library community and UPDIG may be the Preserving Digital Images initiative of the American Society of Media Photographers, undertaken with Library of Congress support via the National Digital Information Infrastructure and Preservation Program (NDIIPP); <a href="http://www.asmp.org/pdi/index.php" rel="nofollow">http://www.asmp.org/pdi/index.php</a> has more on the &#8220;ASMP-PDI,&#8221; as it&#8217;s known.</p>
<p>- repository-focused work linked to UPDIG in some other key ways is happening under the auspices of ImageMuse (<a href="http://imagemuse.org" rel="nofollow">http://imagemuse.org</a>).</p>
<p>And with that, I&#8217;ll stop for real. Promise.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: the Jester</title>
		<link>http://dltj.org/article/jpeg-as-master/comment-page-1/#comment-30450</link>
		<dc:creator>the Jester</dc:creator>
		<pubDate>Wed, 06 Feb 2008 15:38:40 +0000</pubDate>
		<guid isPermaLink="false">http://dltj.org/article/jpeg-as-master/#comment-30450</guid>
		<description>A great clarification on the intent of the UPDIG document.  I didn&#039;t read through the whole thing, so it is possible I took the &quot;archive&quot; chapter out of context of the rest of the document and its intended audience.  I would agree that a JPEG2000 practice would take some effort given that it is not the native format of digital cameras.  Still, it would be useful (I think) if the document&#039;s archive chapter attempted to stratify the options from least-effort to gold-standard as a way to organize the options available to practitioners.

Thanks for the comment, rob, and for pointing the authors of the UPDIG to this discussion.</description>
		<content:encoded><![CDATA[<p>A great clarification on the intent of the UPDIG document.  I didn&#8217;t read through the whole thing, so it is possible I took the &#8220;archive&#8221; chapter out of context of the rest of the document and its intended audience.  I would agree that a JPEG2000 practice would take some effort given that it is not the native format of digital cameras.  Still, it would be useful (I think) if the document&#8217;s archive chapter attempted to stratify the options from least-effort to gold-standard as a way to organize the options available to practitioners.</p>
<p>Thanks for the comment, rob, and for pointing the authors of the UPDIG to this discussion.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
