<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments for Passing on the Left</title>
	<link>http://www.schleef.org/blog</link>
	<description>Just another WordPress weblog</description>
	<pubDate>Thu, 28 Aug 2008 23:08:12 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.2</generator>

	<item>
		<title>Comment on Dirac news by Caroliano</title>
		<link>http://www.schleef.org/blog/2008/07/15/dirac-news/#comment-1062</link>
		<author>Caroliano</author>
		<pubDate>Mon, 04 Aug 2008 14:24:13 +0000</pubDate>
		<guid>http://www.schleef.org/blog/2008/07/15/dirac-news/#comment-1062</guid>
		<description>It is not OGM. OGM was a hack to permit any VFW codecs in ogg. Dirac and Theora use their own especification to be correctly embebed in ogg.

Still, I preffer matroska. AFAIK, much lower overhead, more formats suported (especialy important for subtitles), etc. It is too much to list. 

Looking foward to something easily testable in windows.</description>
		<content:encoded><![CDATA[<p>It is not OGM. OGM was a hack to permit any VFW codecs in ogg. Dirac and Theora use their own especification to be correctly embebed in ogg.</p>
<p>Still, I preffer matroska. AFAIK, much lower overhead, more formats suported (especialy important for subtitles), etc. It is too much to list. </p>
<p>Looking foward to something easily testable in windows.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Dirac news by Recent URLs tagged Cheese - Urlrecorder</title>
		<link>http://www.schleef.org/blog/2008/07/15/dirac-news/#comment-1061</link>
		<author>Recent URLs tagged Cheese - Urlrecorder</author>
		<pubDate>Sun, 03 Aug 2008 16:00:10 +0000</pubDate>
		<guid>http://www.schleef.org/blog/2008/07/15/dirac-news/#comment-1061</guid>
		<description>[...] recorded first by mcommercial on 2008-07-27&#8594; David Schleef: Dirac news [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] recorded first by mcommercial on 2008-07-27&rarr; David Schleef: Dirac news [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Dirac news by windlass</title>
		<link>http://www.schleef.org/blog/2008/07/15/dirac-news/#comment-1050</link>
		<author>windlass</author>
		<pubDate>Sat, 26 Jul 2008 01:03:23 +0000</pubDate>
		<guid>http://www.schleef.org/blog/2008/07/15/dirac-news/#comment-1050</guid>
		<description>Hi there,

I've been researching Dirac / Schroedinger today; I'm weirdly obsessed with the idea of using Dirac for my intermediate codec in FCP. In the last hour or so I've been running some tests with my Canon HV30 and JES Deinterlacer, doing simple comparisons between ProRes 422 and Dirac. I'm happy to say that Dirac (thanks to your SchroQT plugin) is having a laugh at ProRes. However, as you mentioned on the Dirac Wiki, playback is a significant problem and makes the codec impossible to work with at the moment. A smattering of my results are here: http://blog.windlassfilms.com/

I can't wait to see it in action!</description>
		<content:encoded><![CDATA[<p>Hi there,</p>
<p>I&#8217;ve been researching Dirac / Schroedinger today; I&#8217;m weirdly obsessed with the idea of using Dirac for my intermediate codec in FCP. In the last hour or so I&#8217;ve been running some tests with my Canon HV30 and JES Deinterlacer, doing simple comparisons between ProRes 422 and Dirac. I&#8217;m happy to say that Dirac (thanks to your SchroQT plugin) is having a laugh at ProRes. However, as you mentioned on the Dirac Wiki, playback is a significant problem and makes the codec impossible to work with at the moment. A smattering of my results are here: <a href="http://blog.windlassfilms.com/" rel="nofollow">http://blog.windlassfilms.com/</a></p>
<p>I can&#8217;t wait to see it in action!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Dirac news by Chaz6</title>
		<link>http://www.schleef.org/blog/2008/07/15/dirac-news/#comment-1048</link>
		<author>Chaz6</author>
		<pubDate>Mon, 21 Jul 2008 14:45:18 +0000</pubDate>
		<guid>http://www.schleef.org/blog/2008/07/15/dirac-news/#comment-1048</guid>
		<description>Bring back Test Card F!

I would really like to see a directshow filter capable of encoding and decoding raw Dirac streams.

I am curious as to why OGM was chosen as the container format over Matroska, since OGM was based on a hack and Matroska was designed from the ground up.</description>
		<content:encoded><![CDATA[<p>Bring back Test Card F!</p>
<p>I would really like to see a directshow filter capable of encoding and decoding raw Dirac streams.</p>
<p>I am curious as to why OGM was chosen as the container format over Matroska, since OGM was based on a hack and Matroska was designed from the ground up.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Dirac news by Joseph</title>
		<link>http://www.schleef.org/blog/2008/07/15/dirac-news/#comment-1046</link>
		<author>Joseph</author>
		<pubDate>Thu, 17 Jul 2008 14:25:34 +0000</pubDate>
		<guid>http://www.schleef.org/blog/2008/07/15/dirac-news/#comment-1046</guid>
		<description>I'm with those calling "awesome".

Looking forward to a very worthy Free format.</description>
		<content:encoded><![CDATA[<p>I&#8217;m with those calling &#8220;awesome&#8221;.</p>
<p>Looking forward to a very worthy Free format.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Dirac news by fraggle</title>
		<link>http://www.schleef.org/blog/2008/07/15/dirac-news/#comment-1042</link>
		<author>fraggle</author>
		<pubDate>Wed, 16 Jul 2008 09:11:34 +0000</pubDate>
		<guid>http://www.schleef.org/blog/2008/07/15/dirac-news/#comment-1042</guid>
		<description>Dirac is a BBC project, right?  Surely you should be showing Test Card F.</description>
		<content:encoded><![CDATA[<p>Dirac is a BBC project, right?  Surely you should be showing Test Card F.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Dirac news by dré</title>
		<link>http://www.schleef.org/blog/2008/07/15/dirac-news/#comment-1041</link>
		<author>dré</author>
		<pubDate>Wed, 16 Jul 2008 07:38:04 +0000</pubDate>
		<guid>http://www.schleef.org/blog/2008/07/15/dirac-news/#comment-1041</guid>
		<description>some nice projects! direct links would've been cool though...</description>
		<content:encoded><![CDATA[<p>some nice projects! direct links would&#8217;ve been cool though&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Dirac news by Frank</title>
		<link>http://www.schleef.org/blog/2008/07/15/dirac-news/#comment-1040</link>
		<author>Frank</author>
		<pubDate>Wed, 16 Jul 2008 04:19:34 +0000</pubDate>
		<guid>http://www.schleef.org/blog/2008/07/15/dirac-news/#comment-1040</guid>
		<description>In one word: Awesome!

Thanks,
Frank</description>
		<content:encoded><![CDATA[<p>In one word: Awesome!</p>
<p>Thanks,<br />
Frank</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Introducing Orc by admin</title>
		<link>http://www.schleef.org/blog/2008/05/23/introducing-orc/#comment-1006</link>
		<author>admin</author>
		<pubDate>Sat, 24 May 2008 02:40:10 +0000</pubDate>
		<guid>http://www.schleef.org/blog/2008/05/23/introducing-orc/#comment-1006</guid>
		<description>It's not entirely clear from the text that orc is part of the liboil source.</description>
		<content:encoded><![CDATA[<p>It&#8217;s not entirely clear from the text that orc is part of the liboil source.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Introducing Orc by admin</title>
		<link>http://www.schleef.org/blog/2008/05/23/introducing-orc/#comment-1002</link>
		<author>admin</author>
		<pubDate>Fri, 23 May 2008 20:43:25 +0000</pubDate>
		<guid>http://www.schleef.org/blog/2008/05/23/introducing-orc/#comment-1002</guid>
		<description>llvm: LLVM is a good tool, and a very general version of what Orc does.  However, I was not able to get it to produce code that was as fast as liboil code.  In addition, Orc is much more extensible in the exact areas I need and I think other people need.

As much as I dislike NIH syndrome, this project definitely borders on it.  My defense is that I now have a working runtime compiler with features I need, rather than still attempting to hack those features onto LLVM.</description>
		<content:encoded><![CDATA[<p>llvm: LLVM is a good tool, and a very general version of what Orc does.  However, I was not able to get it to produce code that was as fast as liboil code.  In addition, Orc is much more extensible in the exact areas I need and I think other people need.</p>
<p>As much as I dislike NIH syndrome, this project definitely borders on it.  My defense is that I now have a working runtime compiler with features I need, rather than still attempting to hack those features onto LLVM.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
