<?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: UNIX Scripts Bash Tips: transcoding converting video files Part 3</title>
	<atom:link href="http://www.thechangelab.com/toshiyas-blog/unix-scripts-bash-tips-transcoding-converting-video-files-part-3.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.thechangelab.com/toshiyas-blog/unix-scripts-bash-tips-transcoding-converting-video-files-part-3.html</link>
	<description>If it's not in the lab, you don't need it.</description>
	<lastBuildDate>Fri, 04 Jun 2010 07:37:44 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: toshiya</title>
		<link>http://www.thechangelab.com/toshiyas-blog/unix-scripts-bash-tips-transcoding-converting-video-files-part-3.html/comment-page-1#comment-1656</link>
		<dc:creator>toshiya</dc:creator>
		<pubDate>Thu, 24 Jul 2008 15:26:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.thechangelab.com/toshiyas-blog/unix-scripts-bash-tips-transcoding-converting-video-files-part-3.html#comment-1656</guid>
		<description>Hi David. Sorry for not getting back to you sooner.

In determining the compressibility of the original video, I assume you want to know how small you can make the final transcoded video file. I believe you&#039;d have to use something like xvid4conf. (It&#039;s available as a Debian package.) I think they&#039;re often referred to as &quot;bitrate calculators&quot;.

What you&#039;re describing in terms of &quot;output&quot; actually sounds like the Xvid passlog file. My understanding is that, the first pass is used to determine how much the file can be compressed, amongst other things of course. All the data is then dumped into the passlog file. The info. in the passlog file is then used in the second pass.

As an experiment, edit your script so that the transcoding from the first pass is not dumped to /dev/null :

mencoder â€œ$1â€³  -profile  pass1 -o pass1.avi

Run the script in near full screen and take a quick look at mencoder&#039;s stdout. Hit cntrl + c once it actually starts the transcoding. You should notice a line where it says that it ignores bitrate settings in the FIRST pass encoded video file.

Anyway, if you&#039;re goal is to shrink the file, but still make it look AND sound okay, you&#039;ll need to investigate all the other Mencoder options in the man page. There&#039;s a lot.

For starters, you can scale down the resolution, say from 720 pixels wide to 640 pixels wide or less. I think standard def TV is 480 px wide. Also, if the audio part of the video file is in AC3 or PCM, encode with libmp3lame. 

However, I find using the fixed quantizer option the easiest and fastest.</description>
		<content:encoded><![CDATA[<p>Hi David. Sorry for not getting back to you sooner.</p>
<p>In determining the compressibility of the original video, I assume you want to know how small you can make the final transcoded video file. I believe you&#8217;d have to use something like xvid4conf. (It&#8217;s available as a Debian package.) I think they&#8217;re often referred to as &#8220;bitrate calculators&#8221;.</p>
<p>What you&#8217;re describing in terms of &#8220;output&#8221; actually sounds like the Xvid passlog file. My understanding is that, the first pass is used to determine how much the file can be compressed, amongst other things of course. All the data is then dumped into the passlog file. The info. in the passlog file is then used in the second pass.</p>
<p>As an experiment, edit your script so that the transcoding from the first pass is not dumped to /dev/null :</p>
<p>mencoder â€œ$1â€³  -profile  pass1 -o pass1.avi</p>
<p>Run the script in near full screen and take a quick look at mencoder&#8217;s stdout. Hit cntrl + c once it actually starts the transcoding. You should notice a line where it says that it ignores bitrate settings in the FIRST pass encoded video file.</p>
<p>Anyway, if you&#8217;re goal is to shrink the file, but still make it look AND sound okay, you&#8217;ll need to investigate all the other Mencoder options in the man page. There&#8217;s a lot.</p>
<p>For starters, you can scale down the resolution, say from 720 pixels wide to 640 pixels wide or less. I think standard def TV is 480 px wide. Also, if the audio part of the video file is in AC3 or PCM, encode with libmp3lame. </p>
<p>However, I find using the fixed quantizer option the easiest and fastest.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David</title>
		<link>http://www.thechangelab.com/toshiyas-blog/unix-scripts-bash-tips-transcoding-converting-video-files-part-3.html/comment-page-1#comment-1577</link>
		<dc:creator>David</dc:creator>
		<pubDate>Thu, 17 Jul 2008 21:15:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.thechangelab.com/toshiyas-blog/unix-scripts-bash-tips-transcoding-converting-video-files-part-3.html#comment-1577</guid>
		<description>If you wanted to run with a constant quality factor in pass1 so as to determine the compressibility of the file, can you take its output and roll the resulting bitrate into pass2 using a script technique or other automated way?  If so, can you provide an example?  Thanks! If you ask me, the next MEncoder version should built in this functionality.</description>
		<content:encoded><![CDATA[<p>If you wanted to run with a constant quality factor in pass1 so as to determine the compressibility of the file, can you take its output and roll the resulting bitrate into pass2 using a script technique or other automated way?  If so, can you provide an example?  Thanks! If you ask me, the next MEncoder version should built in this functionality.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
