<?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: undvd: looking ahead. and back.</title>
	<atom:link href="http://www.matusiak.eu/numerodix/blog/index.php/2007/12/11/undvd-looking-ahead-and-back/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.matusiak.eu/numerodix/blog/index.php/2007/12/11/undvd-looking-ahead-and-back/</link>
	<description>A blog about nothing</description>
	<lastBuildDate>Tue, 31 Jan 2012 20:14:03 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: foobar</title>
		<link>http://www.matusiak.eu/numerodix/blog/index.php/2007/12/11/undvd-looking-ahead-and-back/#comment-42244</link>
		<dc:creator>foobar</dc:creator>
		<pubDate>Wed, 19 Dec 2007 10:49:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.matusiak.eu/numerodix/blog/index.php/2007/12/11/undvd-looking-ahead-and-back/#comment-42244</guid>
		<description>@ Dirk

MP4 is not a smaller container than AVI, it has much less overhead that AVI, thus for its smaller size. The thing is that AVI + h264 video is the worse thing you can ever do. The AVI container isn&#039;t designed to use B-Frames in the first place, and it cannot see that far when you use multiple frame references in H.264 - it uses ugly nasty hacks to allow B-Frames and even with the biggest hack, it cannot see beyond 8 frame references (h264 allows up to 16 framerefs). The MPEG and ITU groups strongly advise to stay away from the AVI container if you&#039;re going to encode to H.264 video. Preferred container for h264 video is MP4, but a lot of movie freaks, especially those from the Doom9 forum, will advise you to stay away from MP4 because of its limitations (can hold only a few audio codecs) and its closed nature and that&#039;s why you see a lot of MKVs on the Net holding h264 video. On the other hand though, MP4 is standardized and supported by hardware players. There are only a few of them that support the MKV container</description>
		<content:encoded><![CDATA[<p>@ Dirk</p>
<p>MP4 is not a smaller container than AVI, it has much less overhead that AVI, thus for its smaller size. The thing is that AVI + h264 video is the worse thing you can ever do. The AVI container isn&#8217;t designed to use B-Frames in the first place, and it cannot see that far when you use multiple frame references in H.264 &#8211; it uses ugly nasty hacks to allow B-Frames and even with the biggest hack, it cannot see beyond 8 frame references (h264 allows up to 16 framerefs). The MPEG and ITU groups strongly advise to stay away from the AVI container if you&#8217;re going to encode to H.264 video. Preferred container for h264 video is MP4, but a lot of movie freaks, especially those from the Doom9 forum, will advise you to stay away from MP4 because of its limitations (can hold only a few audio codecs) and its closed nature and that&#8217;s why you see a lot of MKVs on the Net holding h264 video. On the other hand though, MP4 is standardized and supported by hardware players. There are only a few of them that support the MKV container</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dirk R. Gently</title>
		<link>http://www.matusiak.eu/numerodix/blog/index.php/2007/12/11/undvd-looking-ahead-and-back/#comment-41994</link>
		<dc:creator>Dirk R. Gently</dc:creator>
		<pubDate>Fri, 14 Dec 2007 15:02:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.matusiak.eu/numerodix/blog/index.php/2007/12/11/undvd-looking-ahead-and-back/#comment-41994</guid>
		<description>These scripts I&#039;ll have to try out.  I&#039;ve spent alot of time researching the first time I&#039;d ripped straight from DVD and I wish I&#039;d seen these first.  Recently I&#039;ve learned to rip to MP4, it&#039;s container is smaller than that of avi.  Also I learned how to use ffmpeg in a single pass.  

http://gentoo-wiki.com/HOWTO_DVD_to_MP4</description>
		<content:encoded><![CDATA[<p>These scripts I&#8217;ll have to try out.  I&#8217;ve spent alot of time researching the first time I&#8217;d ripped straight from DVD and I wish I&#8217;d seen these first.  Recently I&#8217;ve learned to rip to MP4, it&#8217;s container is smaller than that of avi.  Also I learned how to use ffmpeg in a single pass.  </p>
<p><a href="http://gentoo-wiki.com/HOWTO_DVD_to_MP4" rel="nofollow">http://gentoo-wiki.com/HOWTO_DVD_to_MP4</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: numerodix</title>
		<link>http://www.matusiak.eu/numerodix/blog/index.php/2007/12/11/undvd-looking-ahead-and-back/#comment-41978</link>
		<dc:creator>numerodix</dc:creator>
		<pubDate>Fri, 14 Dec 2007 01:14:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.matusiak.eu/numerodix/blog/index.php/2007/12/11/undvd-looking-ahead-and-back/#comment-41978</guid>
		<description>Yes, that is all true. But in response, may I select a not-so-random paragraph? :)

&quot;Therefore, I think it’s fair to say that we have the Photoshop of DVD ripping in place. Personally I want to use Paint for this activity, because I have no deep interest in all the details.&quot;

There&#039;s absolutely no doubt that you will get better quality with a highly specialized setup. But that&#039;s.... okay with me :)</description>
		<content:encoded><![CDATA[<p>Yes, that is all true. But in response, may I select a not-so-random paragraph? <img src='http://www.matusiak.eu/numerodix/blog/wp-includes/images/smilies/smile.png' alt=':)' class='wp-smiley' /> </p>
<p>&#8220;Therefore, I think it’s fair to say that we have the Photoshop of DVD ripping in place. Personally I want to use Paint for this activity, because I have no deep interest in all the details.&#8221;</p>
<p>There&#8217;s absolutely no doubt that you will get better quality with a highly specialized setup. But that&#8217;s&#8230;. okay with me <img src='http://www.matusiak.eu/numerodix/blog/wp-includes/images/smilies/smile.png' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: microchip</title>
		<link>http://www.matusiak.eu/numerodix/blog/index.php/2007/12/11/undvd-looking-ahead-and-back/#comment-41977</link>
		<dc:creator>microchip</dc:creator>
		<pubDate>Fri, 14 Dec 2007 00:43:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.matusiak.eu/numerodix/blog/index.php/2007/12/11/undvd-looking-ahead-and-back/#comment-41977</guid>
		<description>Actually, an interactive ripper has huge advantages over one that is non-interactive. When you encode video, there&#039;s no such thing as &quot;one fits them all&quot; setting - this has been discussed by the MEncoder developers many times on their mailing list. Video encoding is always been very hard because each DVD content is different from the other, especially when you start considering cropping, deinterlacing, telecine (which is a complete mess), badly mastered DVDs which tend to mislead the encoder about their FPS values and force it to skip frames when one does not set or force the correct output frame rate... interactive rippers also offer the user enough options to produce very high quality encodes and also to &quot;correct&quot; something if needed (see above about badly mastered DVDs). Yes, with an interactive ripper you need to take the time to set your stuff, but in the end, you can be pretty sure that you will get a &quot;tweaked&quot; encoding optimized for (very) high quality or for a specific file size :)</description>
		<content:encoded><![CDATA[<p>Actually, an interactive ripper has huge advantages over one that is non-interactive. When you encode video, there&#8217;s no such thing as &#8220;one fits them all&#8221; setting &#8211; this has been discussed by the MEncoder developers many times on their mailing list. Video encoding is always been very hard because each DVD content is different from the other, especially when you start considering cropping, deinterlacing, telecine (which is a complete mess), badly mastered DVDs which tend to mislead the encoder about their FPS values and force it to skip frames when one does not set or force the correct output frame rate&#8230; interactive rippers also offer the user enough options to produce very high quality encodes and also to &#8220;correct&#8221; something if needed (see above about badly mastered DVDs). Yes, with an interactive ripper you need to take the time to set your stuff, but in the end, you can be pretty sure that you will get a &#8220;tweaked&#8221; encoding optimized for (very) high quality or for a specific file size <img src='http://www.matusiak.eu/numerodix/blog/wp-includes/images/smilies/smile.png' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>

