<?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: JPEGs &#038; Artifacts	</title>
	<atom:link href="https://exposure.software/blog/2012/jpegs-artifacts/feed/" rel="self" type="application/rss+xml" />
	<link>https://exposure.software/blog/2012/jpegs-artifacts/</link>
	<description>Simple Tools. Simply Beautiful.</description>
	<lastBuildDate>Mon, 23 Sep 2019 17:09:38 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: Jimmy		</title>
		<link>https://exposure.software/blog/2012/jpegs-artifacts/#comment-13553</link>

		<dc:creator><![CDATA[Jimmy]]></dc:creator>
		<pubDate>Wed, 06 Nov 2013 14:24:06 +0000</pubDate>
		<guid isPermaLink="false">http://blog.alienskin.com/?p=5268#comment-13553</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://exposure.software/blog/2012/jpegs-artifacts/#comment-13514&quot;&gt;shura&lt;/a&gt;.

Hi Shura,

Exactly! Working with a lossless format is just what the article is about. The more information the image has, the better. When exporting from Lightroom--it&#039;s best to render to a Tiff format before applying effects with Exposure, Snap Art, or any of our products. This ensures that our software will produce high quality results without the artifacting caused by the image format.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://exposure.software/blog/2012/jpegs-artifacts/#comment-13514">shura</a>.</p>
<p>Hi Shura,</p>
<p>Exactly! Working with a lossless format is just what the article is about. The more information the image has, the better. When exporting from Lightroom&#8211;it&#8217;s best to render to a Tiff format before applying effects with Exposure, Snap Art, or any of our products. This ensures that our software will produce high quality results without the artifacting caused by the image format.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: shura		</title>
		<link>https://exposure.software/blog/2012/jpegs-artifacts/#comment-13514</link>

		<dc:creator><![CDATA[shura]]></dc:creator>
		<pubDate>Tue, 05 Nov 2013 21:41:02 +0000</pubDate>
		<guid isPermaLink="false">http://blog.alienskin.com/?p=5268#comment-13514</guid>

					<description><![CDATA[But it would make sense to work on image in lossless tiff, but the save the final result as jpeg to save space. Currently in Lightroom you can only choose to send jpeg to AlienSkin and that is not what we want. We want to be able to start with tiff, and then save final result as jpeg, deleting the bloated tiff created by Lightroom.]]></description>
			<content:encoded><![CDATA[<p>But it would make sense to work on image in lossless tiff, but the save the final result as jpeg to save space. Currently in Lightroom you can only choose to send jpeg to AlienSkin and that is not what we want. We want to be able to start with tiff, and then save final result as jpeg, deleting the bloated tiff created by Lightroom.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Jimmy		</title>
		<link>https://exposure.software/blog/2012/jpegs-artifacts/#comment-3545</link>

		<dc:creator><![CDATA[Jimmy]]></dc:creator>
		<pubDate>Mon, 01 Oct 2012 14:06:05 +0000</pubDate>
		<guid isPermaLink="false">http://blog.alienskin.com/?p=5268#comment-3545</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://exposure.software/blog/2012/jpegs-artifacts/#comment-3534&quot;&gt;jack mckechnie&lt;/a&gt;.

Hi Jack,

I agree that it sounds crazy to resave an image hundreds of times, but it does happen. When I worked as an architect, I saw it happen to many common image files. Images like company logos would go through a lot of adjustments. Files routinely underwent hundreds of adjustments through the lifetime of the project. Sometimes the logos would be unreadable by the time the project was complete.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://exposure.software/blog/2012/jpegs-artifacts/#comment-3534">jack mckechnie</a>.</p>
<p>Hi Jack,</p>
<p>I agree that it sounds crazy to resave an image hundreds of times, but it does happen. When I worked as an architect, I saw it happen to many common image files. Images like company logos would go through a lot of adjustments. Files routinely underwent hundreds of adjustments through the lifetime of the project. Sometimes the logos would be unreadable by the time the project was complete.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Jimmy		</title>
		<link>https://exposure.software/blog/2012/jpegs-artifacts/#comment-3544</link>

		<dc:creator><![CDATA[Jimmy]]></dc:creator>
		<pubDate>Mon, 01 Oct 2012 13:54:32 +0000</pubDate>
		<guid isPermaLink="false">http://blog.alienskin.com/?p=5268#comment-3544</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://exposure.software/blog/2012/jpegs-artifacts/#comment-3542&quot;&gt;Jim Schimpf&lt;/a&gt;.

Hi Jim,

Generation loss is generation loss. It&#039;s going to happen regardless of the compression settings you use. Higher quality values can make things worse. Here is an example &lt;a href=&quot;http://www.youtube.com/watch?feature=player_embedded&amp;v=Fk6kV5N1rzs&quot; target=&quot;_blank&quot; rel=&quot;nofollow&quot;&gt;video&lt;/a&gt; from Reddit member Grundle, they used a high quality compression value of 10 out of 12.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://exposure.software/blog/2012/jpegs-artifacts/#comment-3542">Jim Schimpf</a>.</p>
<p>Hi Jim,</p>
<p>Generation loss is generation loss. It&#8217;s going to happen regardless of the compression settings you use. Higher quality values can make things worse. Here is an example <a href="http://www.youtube.com/watch?feature=player_embedded&#038;v=Fk6kV5N1rzs" target="_blank" rel="nofollow">video</a> from Reddit member Grundle, they used a high quality compression value of 10 out of 12.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Jim Schimpf		</title>
		<link>https://exposure.software/blog/2012/jpegs-artifacts/#comment-3542</link>

		<dc:creator><![CDATA[Jim Schimpf]]></dc:creator>
		<pubDate>Sun, 30 Sep 2012 11:08:46 +0000</pubDate>
		<guid isPermaLink="false">http://blog.alienskin.com/?p=5268#comment-3542</guid>

					<description><![CDATA[Ah not quite the problem you think it is.  If you have a picture up in Photoshop or something then save THAT as a JPEG.  Open that file again and save as a JPEG and so on with the quality set as Low you will get the effects you show.  (Setting on high quality would cause the same sort of problems but would take more cycles.)  Just saving the file as a file (like TimeMachine or just a disk copy does) would have no effect as that does a bit-by-bit copy.  It&#039;s the saving though the JPEG process that compresses the image and as you show causes a quality loss.]]></description>
			<content:encoded><![CDATA[<p>Ah not quite the problem you think it is.  If you have a picture up in Photoshop or something then save THAT as a JPEG.  Open that file again and save as a JPEG and so on with the quality set as Low you will get the effects you show.  (Setting on high quality would cause the same sort of problems but would take more cycles.)  Just saving the file as a file (like TimeMachine or just a disk copy does) would have no effect as that does a bit-by-bit copy.  It&#8217;s the saving though the JPEG process that compresses the image and as you show causes a quality loss.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: jack mckechnie		</title>
		<link>https://exposure.software/blog/2012/jpegs-artifacts/#comment-3534</link>

		<dc:creator><![CDATA[jack mckechnie]]></dc:creator>
		<pubDate>Fri, 28 Sep 2012 14:19:53 +0000</pubDate>
		<guid isPermaLink="false">http://blog.alienskin.com/?p=5268#comment-3534</guid>

					<description><![CDATA[Who goes in and adjusts a file even 200 times? That&#039;s crazy!

Show us before and after on files adjusted 10 to 20 times. If i use Jpegs I do everything i want to it at one time.  I switch only mainly between Corel aftershot pro or Corel 12 with Exposure 4.]]></description>
			<content:encoded><![CDATA[<p>Who goes in and adjusts a file even 200 times? That&#8217;s crazy!</p>
<p>Show us before and after on files adjusted 10 to 20 times. If i use Jpegs I do everything i want to it at one time.  I switch only mainly between Corel aftershot pro or Corel 12 with Exposure 4.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
