<?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: Converting 16:9 content to QCIF ?</title>
	<atom:link href="http://mvstreaming.com/converting-169-ratio-content-to-qcif/feed/" rel="self" type="application/rss+xml" />
	<link>http://mvstreaming.com/converting-169-ratio-content-to-qcif/</link>
	<description>Demystifing mobile video streaming - I hope.</description>
	<lastBuildDate>Thu, 03 Jul 2008 19:42:46 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: weeklymg</title>
		<link>http://mvstreaming.com/converting-169-ratio-content-to-qcif/comment-page-1/#comment-4</link>
		<dc:creator>weeklymg</dc:creator>
		<pubDate>Mon, 21 May 2007 05:55:29 +0000</pubDate>
		<guid isPermaLink="false">http://mvstreaming.com/converting-169-ratio-content-to-qcif/#comment-4</guid>
		<description>It takes 2 or 3 passes to do it right.  If you don&#039;t know the dimensions you need to do a pass with ffmpeg or another program to parse the original dimensions (w and h) from the output.  Then you need a pass without setting the size but setting padtop and padbottom to p, where 4(h + 2p) = 3w.  And I think the default value for padcolor is black, which should be fine.  Then you have a video with a 4:3 aspect which you transcode to 3gp in another ffmpeg pass using -s qcif.

By the way, I haven&#039;t had much luck with Darwin streaming on mobile.  The presence of a hinted audio track caused weird and ugly effects on the mobiles I tested with.  I saw the same problem with streams from the site  www.zoovision.com. The site eyeka.com seems to deal with this issue by building their own J2ME player and only showing the streaming links to their player.  I don&#039;t have a phone which supports their player, though.  

One other issue which could block you is the operator.  See this cached page for someone&#039;s test results (though note that there&#039;s what I hope is a typo - the rtsp port is 554, not 551): http://tinyurl.com/2z37l9</description>
		<content:encoded><![CDATA[<p>It takes 2 or 3 passes to do it right.  If you don&#8217;t know the dimensions you need to do a pass with ffmpeg or another program to parse the original dimensions (w and h) from the output.  Then you need a pass without setting the size but setting padtop and padbottom to p, where 4(h + 2p) = 3w.  And I think the default value for padcolor is black, which should be fine.  Then you have a video with a 4:3 aspect which you transcode to 3gp in another ffmpeg pass using -s qcif.</p>
<p>By the way, I haven&#8217;t had much luck with Darwin streaming on mobile.  The presence of a hinted audio track caused weird and ugly effects on the mobiles I tested with.  I saw the same problem with streams from the site  <a href="http://www.zoovision.com" rel="nofollow">http://www.zoovision.com</a>. The site eyeka.com seems to deal with this issue by building their own J2ME player and only showing the streaming links to their player.  I don&#8217;t have a phone which supports their player, though.  </p>
<p>One other issue which could block you is the operator.  See this cached page for someone&#8217;s test results (though note that there&#8217;s what I hope is a typo &#8211; the rtsp port is 554, not 551): <a href="http://tinyurl.com/2z37l9" rel="nofollow">http://tinyurl.com/2z37l9</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
