<?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"
	>
<channel>
	<title>Comments on: JPEG&#8217;s Reply to Microsoft WMP: Better JPEG?</title>
	<atom:link href="http://www.c10n.info/archives/427/feed" rel="self" type="application/rss+xml" />
	<link>http://www.c10n.info/archives/427</link>
	<description>All about the most recent compression techniques, algorithms, patents, products, tools and events.</description>
	<pubDate>Sun, 14 Mar 2010 08:28:42 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: donkey7</title>
		<link>http://www.c10n.info/archives/427#comment-28938</link>
		<dc:creator>donkey7</dc:creator>
		<pubDate>Tue, 19 Sep 2006 13:24:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.c10n.info/archives/427#comment-28938</guid>
		<description>http://www.cs.tut.fi/~foi/SA-DCT/results.html#ref_deblock - improves visual quality of jpeg images.

i think jpeg2000 isn't superior to jpeg. it doesn't suffer from blocking artifacts but usually removes much more detailt and introduces much more blurring. standard jpeg with right preprocessing (smoothing of luma and chroma planes and downsampling if necessary), optimized quantization tables, dct position dependent entropy coder and good postprocessing filter (like this presented above) gives much higher visual quality than jpeg2000 at usual bitrates (0.5 bpp and above).

the biggest advantage of jpeg2000 over standard jpeg is its scalability (jpeg2000 doesn't need to downsample input data to compress better). the biggest disdvantage is poor performance - todays jpeg2000 coders are much slower (about 5x or so) and requires much more memory than baseline jpeg.

overall, jpeg2000 isn't worth consideration. better improve baseline jpeg and use stuffit technology instead of simple huffman coder and old jpeg will be working fine.</description>
		<content:encoded><![CDATA[<p><a href="http://www.cs.tut.fi/~foi/SA-DCT/results.html#ref_deblock" rel="nofollow">http://www.cs.tut.fi/~foi/SA-DCT/results.html#ref_deblock</a> - improves visual quality of jpeg images.</p>
<p>i think jpeg2000 isn&#8217;t superior to jpeg. it doesn&#8217;t suffer from blocking artifacts but usually removes much more detailt and introduces much more blurring. standard jpeg with right preprocessing (smoothing of luma and chroma planes and downsampling if necessary), optimized quantization tables, dct position dependent entropy coder and good postprocessing filter (like this presented above) gives much higher visual quality than jpeg2000 at usual bitrates (0.5 bpp and above).</p>
<p>the biggest advantage of jpeg2000 over standard jpeg is its scalability (jpeg2000 doesn&#8217;t need to downsample input data to compress better). the biggest disdvantage is poor performance - todays jpeg2000 coders are much slower (about 5x or so) and requires much more memory than baseline jpeg.</p>
<p>overall, jpeg2000 isn&#8217;t worth consideration. better improve baseline jpeg and use stuffit technology instead of simple huffman coder and old jpeg will be working fine.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pieter</title>
		<link>http://www.c10n.info/archives/427#comment-15793</link>
		<dc:creator>pieter</dc:creator>
		<pubDate>Wed, 02 Aug 2006 13:30:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.c10n.info/archives/427#comment-15793</guid>
		<description>Jpeg can be improved by using two simple additional processes.

1st. low bit rates can improved by using downsampling. Less artifact are visual if you resize the image to 70 % of the original and compress it using jpeg. You have to resize it back to the original size to see the results.

2nd. You can remove the artifact by using a postprocessing filter.
This one works very well.
http://www.compression.ru/video/deblocking/smartdeblocking_en.html</description>
		<content:encoded><![CDATA[<p>Jpeg can be improved by using two simple additional processes.</p>
<p>1st. low bit rates can improved by using downsampling. Less artifact are visual if you resize the image to 70 % of the original and compress it using jpeg. You have to resize it back to the original size to see the results.</p>
<p>2nd. You can remove the artifact by using a postprocessing filter.<br />
This one works very well.<br />
<a href="http://www.compression.ru/video/deblocking/smartdeblocking_en.html" rel="nofollow">http://www.compression.ru/video/deblocking/smartdeblocking_en.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sandman</title>
		<link>http://www.c10n.info/archives/427#comment-5566</link>
		<dc:creator>sandman</dc:creator>
		<pubDate>Mon, 19 Jun 2006 18:56:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.c10n.info/archives/427#comment-5566</guid>
		<description>A transcoder is already available and they are atleast planning for integration in the popular IJG library.

The real question is if IE7 and Vista will support it.</description>
		<content:encoded><![CDATA[<p>A transcoder is already available and they are atleast planning for integration in the popular IJG library.</p>
<p>The real question is if IE7 and Vista will support it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Krisjohn</title>
		<link>http://www.c10n.info/archives/427#comment-5377</link>
		<dc:creator>Krisjohn</dc:creator>
		<pubDate>Fri, 16 Jun 2006 06:16:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.c10n.info/archives/427#comment-5377</guid>
		<description>A transcoding personal proxy (along the lines of my half-baked http://www.halfbakery.com/idea/Compression_20Proxy ) with a good plug-in system, and matching apache mods could greatly speed up the adoption of these new image formats.  I wish people would care about image optimisation, particularly on the web.</description>
		<content:encoded><![CDATA[<p>A transcoding personal proxy (along the lines of my half-baked <a href="http://www.halfbakery.com/idea/Compression_20Proxy" rel="nofollow">http://www.halfbakery.com/idea/Compression_20Proxy</a> ) with a good plug-in system, and matching apache mods could greatly speed up the adoption of these new image formats.  I wish people would care about image optimisation, particularly on the web.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
