<?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 on: Microsoft vs. JPEG</title>
	<atom:link href="http://thomashawk.com/2006/05/microsoft-vs-jpeg.html/feed" rel="self" type="application/rss+xml" />
	<link>http://thomashawk.com/2006/05/microsoft-vs-jpeg.html</link>
	<description></description>
	<lastBuildDate>Fri, 10 Feb 2012 02:09:43 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Anonymous</title>
		<link>http://thomashawk.com/2006/05/microsoft-vs-jpeg.html/comment-page-1#comment-14464</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Wed, 28 Nov 2007 06:55:00 +0000</pubDate>
		<guid isPermaLink="false">http://clients.emmense.com/thomashawk/?p=2037#comment-14464</guid>
		<description>This comment has been removed because it linked to malicious content. &lt;a href=&quot;http://www.blogger.com/content.g&quot;&gt;Learn more&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>This comment has been removed because it linked to malicious content. <a href="http://www.blogger.com/content.g">Learn more</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://thomashawk.com/2006/05/microsoft-vs-jpeg.html/comment-page-1#comment-14467</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Wed, 19 Jul 2006 11:43:00 +0000</pubDate>
		<guid isPermaLink="false">http://clients.emmense.com/thomashawk/?p=2037#comment-14467</guid>
		<description>shadow- sounds like you really are missing something if you&#039;re describing raw in the same terms as tiff. Raw really means RAW-information that has to be processed. You can&#039;t simply send a raw file to someone and expect them to read it without a decoder so the advantage of sending &#039;better&#039; raw data over smaller file size. There&#039;s not a real comparison there.</description>
		<content:encoded><![CDATA[<p>shadow- sounds like you really are missing something if you&#8217;re describing raw in the same terms as tiff. Raw really means RAW-information that has to be processed. You can&#8217;t simply send a raw file to someone and expect them to read it without a decoder so the advantage of sending &#8216;better&#8217; raw data over smaller file size. There&#8217;s not a real comparison there.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shadow</title>
		<link>http://thomashawk.com/2006/05/microsoft-vs-jpeg.html/comment-page-1#comment-14468</link>
		<dc:creator>Shadow</dc:creator>
		<pubDate>Wed, 31 May 2006 15:05:00 +0000</pubDate>
		<guid isPermaLink="false">http://clients.emmense.com/thomashawk/?p=2037#comment-14468</guid>
		<description>Caught T. Hawks comment over on a link from CNet and had to come over, sounded completely brain dead at first , so I figured I was missing something when he was talking about JPG and the new format replacing RAW.  Turns out to just be point of view.  RAW format is uncompressed, and you lose no quality at all, but, it&#039;s far to large to be used in most data related venues, once you get to the point where you want to send that 5 meg RAW image somewhere in email or publish it on the web, you&#039;re going to need to start looking at how you can bring that file size down to a more managable level while losing as little as possible.  JPG might bring a 5 meg uncompressed TIFF/RAW file down to say 128k without to much loss (this is wildly speculative), MS is saying they can do the same quality or better at 64k.  Will be interesting to see how it pans out.</description>
		<content:encoded><![CDATA[<p>Caught T. Hawks comment over on a link from CNet and had to come over, sounded completely brain dead at first , so I figured I was missing something when he was talking about JPG and the new format replacing RAW.  Turns out to just be point of view.  RAW format is uncompressed, and you lose no quality at all, but, it&#8217;s far to large to be used in most data related venues, once you get to the point where you want to send that 5 meg RAW image somewhere in email or publish it on the web, you&#8217;re going to need to start looking at how you can bring that file size down to a more managable level while losing as little as possible.  JPG might bring a 5 meg uncompressed TIFF/RAW file down to say 128k without to much loss (this is wildly speculative), MS is saying they can do the same quality or better at 64k.  Will be interesting to see how it pans out.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://thomashawk.com/2006/05/microsoft-vs-jpeg.html/comment-page-1#comment-14469</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Fri, 26 May 2006 12:51:00 +0000</pubDate>
		<guid isPermaLink="false">http://clients.emmense.com/thomashawk/?p=2037#comment-14469</guid>
		<description>Yea probably include some DRM, which isnt such a bad thing. It would allow companies to protect images they own. And would help open up an image market.</description>
		<content:encoded><![CDATA[<p>Yea probably include some DRM, which isnt such a bad thing. It would allow companies to protect images they own. And would help open up an image market.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mikem</title>
		<link>http://thomashawk.com/2006/05/microsoft-vs-jpeg.html/comment-page-1#comment-14470</link>
		<dc:creator>mikem</dc:creator>
		<pubDate>Fri, 26 May 2006 11:38:00 +0000</pubDate>
		<guid isPermaLink="false">http://clients.emmense.com/thomashawk/?p=2037#comment-14470</guid>
		<description>Why is this better than the jp2 (jpeg2000) file format? Besides the hype that is?&lt;br /&gt;&lt;br /&gt;Sounds like warmed over technology to me. Probably MS will just put more DRM into it.</description>
		<content:encoded><![CDATA[<p>Why is this better than the jp2 (jpeg2000) file format? Besides the hype that is?</p>
<p>Sounds like warmed over technology to me. Probably MS will just put more DRM into it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason Cross</title>
		<link>http://thomashawk.com/2006/05/microsoft-vs-jpeg.html/comment-page-1#comment-14471</link>
		<dc:creator>Jason Cross</dc:creator>
		<pubDate>Fri, 26 May 2006 11:08:00 +0000</pubDate>
		<guid isPermaLink="false">http://clients.emmense.com/thomashawk/?p=2037#comment-14471</guid>
		<description>Actually, it was a third-party device maker that said they can&#039;t see supporting it before 2008 (a cell phone maker, if I&#039;m not mistaken - they update chipsets on a long schedule). Microsoft will likely have support when Vista launches. But the real key is if Adobe will support it. If they do, it&#039;s a viable format. If not, they&#039;re sunk.&lt;br /&gt;&lt;br /&gt;I think having better quality in less size is important, even for pros. Note that the new format supports a lossless mode, and includes support for high dynamic range images. Let&#039;s say, for the sake of argument, that you could use a LOSSLESS compressed HDR format in 1/4 the size of your RAW. Would you?&lt;br /&gt;&lt;br /&gt;Storage space isn&#039;t the issue. You&#039;re right - that&#039;s growing exponentially. The issue is transfer speed, which affects shot speed. If you could shoot twice as fast, or take bursts of up to four times as many photos in burst mode, would that be worth it?&lt;br /&gt;&lt;br /&gt;I think so.&lt;br /&gt;&lt;br /&gt;It&#039;s a technology worth wathcing.</description>
		<content:encoded><![CDATA[<p>Actually, it was a third-party device maker that said they can&#8217;t see supporting it before 2008 (a cell phone maker, if I&#8217;m not mistaken &#8211; they update chipsets on a long schedule). Microsoft will likely have support when Vista launches. But the real key is if Adobe will support it. If they do, it&#8217;s a viable format. If not, they&#8217;re sunk.</p>
<p>I think having better quality in less size is important, even for pros. Note that the new format supports a lossless mode, and includes support for high dynamic range images. Let&#8217;s say, for the sake of argument, that you could use a LOSSLESS compressed HDR format in 1/4 the size of your RAW. Would you?</p>
<p>Storage space isn&#8217;t the issue. You&#8217;re right &#8211; that&#8217;s growing exponentially. The issue is transfer speed, which affects shot speed. If you could shoot twice as fast, or take bursts of up to four times as many photos in burst mode, would that be worth it?</p>
<p>I think so.</p>
<p>It&#8217;s a technology worth wathcing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://thomashawk.com/2006/05/microsoft-vs-jpeg.html/comment-page-1#comment-14472</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Thu, 25 May 2006 23:40:00 +0000</pubDate>
		<guid isPermaLink="false">http://clients.emmense.com/thomashawk/?p=2037#comment-14472</guid>
		<description>I think the reporters mix JPEG and JPEG2000 in an usual misleading way. Compared to JPEG, WindowsMediaPhoto may be smaller in size, but definitely not compared to JPEG2000 since JPEG2000 uses the L.O.D. wavelet algorithms that WindowsMediaPhoto directly compares to.&lt;br /&gt;&lt;br /&gt;It reminds me Microsoft made an acquisition of a small JPEG2000-related startup back in 2004 or so. Can&#039;t remember the name. I wouldn&#039;t be surprised that those guys are behind this move.</description>
		<content:encoded><![CDATA[<p>I think the reporters mix JPEG and JPEG2000 in an usual misleading way. Compared to JPEG, WindowsMediaPhoto may be smaller in size, but definitely not compared to JPEG2000 since JPEG2000 uses the L.O.D. wavelet algorithms that WindowsMediaPhoto directly compares to.</p>
<p>It reminds me Microsoft made an acquisition of a small JPEG2000-related startup back in 2004 or so. Can&#8217;t remember the name. I wouldn&#8217;t be surprised that those guys are behind this move.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gary Crabbe</title>
		<link>http://thomashawk.com/2006/05/microsoft-vs-jpeg.html/comment-page-1#comment-14473</link>
		<dc:creator>Gary Crabbe</dc:creator>
		<pubDate>Thu, 25 May 2006 19:49:00 +0000</pubDate>
		<guid isPermaLink="false">http://clients.emmense.com/thomashawk/?p=2037#comment-14473</guid>
		<description>(Wi)ndows (M)edia (P)hoto(s).&lt;br /&gt;&lt;br /&gt;WiMPs.&lt;br /&gt;&lt;br /&gt;Then, in 24 months, (once all the bugs are worked out) we&#039;ll get &quot;WiMPs 2.0; Bigger, Badder, WiMP-ier&quot;.</description>
		<content:encoded><![CDATA[<p>(Wi)ndows (M)edia (P)hoto(s).</p>
<p>WiMPs.</p>
<p>Then, in 24 months, (once all the bugs are worked out) we&#8217;ll get &#8220;WiMPs 2.0; Bigger, Badder, WiMP-ier&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: L.A. Price</title>
		<link>http://thomashawk.com/2006/05/microsoft-vs-jpeg.html/comment-page-1#comment-14474</link>
		<dc:creator>L.A. Price</dc:creator>
		<pubDate>Thu, 25 May 2006 14:11:00 +0000</pubDate>
		<guid isPermaLink="false">http://clients.emmense.com/thomashawk/?p=2037#comment-14474</guid>
		<description>I seriously doubt that even Microsoft can push a new and proprietary image format into wide acceptance. Especially with the proliferation of devices that have media codecs built in to hardware, all those phones and webpads and set-tops have .jpg built in. Even if MS were to put all their muscle into it, this format would not be a serious contender for at least 3 years.</description>
		<content:encoded><![CDATA[<p>I seriously doubt that even Microsoft can push a new and proprietary image format into wide acceptance. Especially with the proliferation of devices that have media codecs built in to hardware, all those phones and webpads and set-tops have .jpg built in. Even if MS were to put all their muscle into it, this format would not be a serious contender for at least 3 years.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason</title>
		<link>http://thomashawk.com/2006/05/microsoft-vs-jpeg.html/comment-page-1#comment-14475</link>
		<dc:creator>Jason</dc:creator>
		<pubDate>Thu, 25 May 2006 12:25:00 +0000</pubDate>
		<guid isPermaLink="false">http://clients.emmense.com/thomashawk/?p=2037#comment-14475</guid>
		<description>I don&#039;t think Microsoft intends on replacing RAW with this.  RAW formats will always be camera-centric, whereas formats like JPEG or this new Microsoft one aim to be usable in all different environments.&lt;br /&gt;&lt;br /&gt;It&#039;s too bad all cameras can&#039;t shoot in RAW mode.  Those who know the benefits of shooting in RAW mode will continue to use RAW mode.  Those that don&#039;t, either out of lack of necessity, lack of availability or lack of knowledge probably don&#039;t need it.  It&#039;s the old, &quot;if you know what it is, you know enough in how to use it&quot; adage.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t think Microsoft intends on replacing RAW with this.  RAW formats will always be camera-centric, whereas formats like JPEG or this new Microsoft one aim to be usable in all different environments.</p>
<p>It&#8217;s too bad all cameras can&#8217;t shoot in RAW mode.  Those who know the benefits of shooting in RAW mode will continue to use RAW mode.  Those that don&#8217;t, either out of lack of necessity, lack of availability or lack of knowledge probably don&#8217;t need it.  It&#8217;s the old, &#8220;if you know what it is, you know enough in how to use it&#8221; adage.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

