<?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:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments for picturation</title>
	<atom:link href="http://picturation.wordpress.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://picturation.wordpress.com</link>
	<description>Miscellaneous, mostly technical, topics related to digital photography</description>
	<lastBuildDate>Thu, 01 Mar 2007 23:40:27 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on © Copyrighting Photographs by picturation</title>
		<link>http://picturation.wordpress.com/2006/03/30/copyrighting-photographs/#comment-70</link>
		<dc:creator>picturation</dc:creator>
		<pubDate>Thu, 01 Mar 2007 23:40:27 +0000</pubDate>
		<guid isPermaLink="false">https://picturation.wordpress.com/2006/07/16/copyrighting-photographs/#comment-70</guid>
		<description>You&#039;re quite welcome.  My article focuses mainly on US Copyright law, so you may want to take that into consideration.</description>
		<content:encoded><![CDATA[<p>You&#8217;re quite welcome.  My article focuses mainly on US Copyright law, so you may want to take that into consideration.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on © Copyrighting Photographs by steve heaton</title>
		<link>http://picturation.wordpress.com/2006/03/30/copyrighting-photographs/#comment-69</link>
		<dc:creator>steve heaton</dc:creator>
		<pubDate>Thu, 01 Mar 2007 16:43:05 +0000</pubDate>
		<guid isPermaLink="false">https://picturation.wordpress.com/2006/07/16/copyrighting-photographs/#comment-69</guid>
		<description>thank u for the information it was most useful
bye steve in northwest england.</description>
		<content:encoded><![CDATA[<p>thank u for the information it was most useful<br />
bye steve in northwest england.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on JPEG Compression &#8212; Devil or Angel? by picturation</title>
		<link>http://picturation.wordpress.com/2006/04/21/3/#comment-5</link>
		<dc:creator>picturation</dc:creator>
		<pubDate>Tue, 25 Apr 2006 00:46:47 +0000</pubDate>
		<guid isPermaLink="false">https://picturation.wordpress.com/2006/04/20/3/#comment-5</guid>
		<description>Thanks, red dreamer</description>
		<content:encoded><![CDATA[<p>Thanks, red dreamer</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on JPEG Compression &#8212; Devil or Angel? by picturation</title>
		<link>http://picturation.wordpress.com/2006/04/21/3/#comment-4</link>
		<dc:creator>picturation</dc:creator>
		<pubDate>Tue, 25 Apr 2006 00:45:27 +0000</pubDate>
		<guid isPermaLink="false">https://picturation.wordpress.com/2006/04/20/3/#comment-4</guid>
		<description>Hi Johno

I agree.  Changes to the image will result in a different JPEG compression and thus a different result.  I intended to mention that in the article.  But, as you also say, it&#039;s difficult to devise a way to test the extent of this effect. 

Years ago, before I learned about JPEG losses, I had an image I modified and saved many times.  At the time I didn&#039;t noticed any harm done by this repeated change and save.  But, I was less descriminating then.  :)</description>
		<content:encoded><![CDATA[<p>Hi Johno</p>
<p>I agree.  Changes to the image will result in a different JPEG compression and thus a different result.  I intended to mention that in the article.  But, as you also say, it&#8217;s difficult to devise a way to test the extent of this effect. </p>
<p>Years ago, before I learned about JPEG losses, I had an image I modified and saved many times.  At the time I didn&#8217;t noticed any harm done by this repeated change and save.  But, I was less descriminating then.  <img src='http://s.wordpress.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on JPEG Compression &#8212; Devil or Angel? by .i dream in red.</title>
		<link>http://picturation.wordpress.com/2006/04/21/3/#comment-3</link>
		<dc:creator>.i dream in red.</dc:creator>
		<pubDate>Mon, 24 Apr 2006 23:16:56 +0000</pubDate>
		<guid isPermaLink="false">https://picturation.wordpress.com/2006/04/20/3/#comment-3</guid>
		<description>Cool article. Thanks for the link on your site. I shall return the honor. =D</description>
		<content:encoded><![CDATA[<p>Cool article. Thanks for the link on your site. I shall return the honor. =D</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on JPEG Compression &#8212; Devil or Angel? by berk</title>
		<link>http://picturation.wordpress.com/2006/04/21/3/#comment-2</link>
		<dc:creator>berk</dc:creator>
		<pubDate>Mon, 24 Apr 2006 21:50:07 +0000</pubDate>
		<guid isPermaLink="false">https://picturation.wordpress.com/2006/04/20/3/#comment-2</guid>
		<description>There are other ways to reduce file size without resorting to extreme JPEG compression (I define as 30+% compression). When I shoot, I start with the highest JPEG setting on my camera. I have the option of shooting RAW, but I don&#039;t know how to utilize that and it&#039;s not important for my hobbyist needs. I make a copy and archive the original. With the copy, I first reduce the DPI from 300 to 72 since I am only displaying on the web and not printing them. Next, I&#039;ll reduce the physical size of the image to about 1000 x whatever (gets it close to the resolution of my monitor). Just these two steps shaved a huge chunk off file size. I usually save the JPEG to 80-85%. The initial JPEGs start at 2-4 mb and end up at 150-250k.</description>
		<content:encoded><![CDATA[<p>There are other ways to reduce file size without resorting to extreme JPEG compression (I define as 30+% compression). When I shoot, I start with the highest JPEG setting on my camera. I have the option of shooting RAW, but I don&#8217;t know how to utilize that and it&#8217;s not important for my hobbyist needs. I make a copy and archive the original. With the copy, I first reduce the DPI from 300 to 72 since I am only displaying on the web and not printing them. Next, I&#8217;ll reduce the physical size of the image to about 1000 x whatever (gets it close to the resolution of my monitor). Just these two steps shaved a huge chunk off file size. I usually save the JPEG to 80-85%. The initial JPEGs start at 2-4 mb and end up at 150-250k.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on JPEG Compression &#8212; Devil or Angel? by Johno</title>
		<link>http://picturation.wordpress.com/2006/04/21/3/#comment-1</link>
		<dc:creator>Johno</dc:creator>
		<pubDate>Mon, 24 Apr 2006 02:54:00 +0000</pubDate>
		<guid isPermaLink="false">https://picturation.wordpress.com/2006/04/20/3/#comment-1</guid>
		<description>This all sounds pretty reasonable.  The artifacts in JPEG come about from the approximations in fitting to particular combinations that are possible in JPEG with a certain number of pixels.  Thus, using the same encoding algorithm again and again by opening and saving will result in exactly the same file.  The uncertain thing is more when there are significant changes made to the image, such as doing a curves adjustment over the whole image or a rotation/scale.  In that case it will have to be re-fitted to a different represenation, and is thus open to another round of degredation.  It is a bit harder to do objective tests on such a scenario though.</description>
		<content:encoded><![CDATA[<p>This all sounds pretty reasonable.  The artifacts in JPEG come about from the approximations in fitting to particular combinations that are possible in JPEG with a certain number of pixels.  Thus, using the same encoding algorithm again and again by opening and saving will result in exactly the same file.  The uncertain thing is more when there are significant changes made to the image, such as doing a curves adjustment over the whole image or a rotation/scale.  In that case it will have to be re-fitted to a different represenation, and is thus open to another round of degredation.  It is a bit harder to do objective tests on such a scenario though.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
