<?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: FFMpeg strikes (again)</title>
	<atom:link href="http://blogs.gnome.org/bolsh/2008/12/05/ffmpeg-strikes-again/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.gnome.org/bolsh/2008/12/05/ffmpeg-strikes-again/</link>
	<description>Dave Neary's view of the world</description>
	<lastBuildDate>Wed, 25 Nov 2009 00:48:02 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: noname</title>
		<link>http://blogs.gnome.org/bolsh/2008/12/05/ffmpeg-strikes-again/comment-page-1/#comment-1890</link>
		<dc:creator>noname</dc:creator>
		<pubDate>Tue, 09 Dec 2008 12:42:05 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/bolsh/?p=748#comment-1890</guid>
		<description>so the ubuntu ffmpeg package lacks swscale.h in the correct place (or vxl looks in the wrong place or doesnt check for swscale.h during configure), and you blame upstream ffmpeg?</description>
		<content:encoded><![CDATA[<p>so the ubuntu ffmpeg package lacks swscale.h in the correct place (or vxl looks in the wrong place or doesnt check for swscale.h during configure), and you blame upstream ffmpeg?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Does FFmpeg Actually Suck? &#124; Breaking Eggs And Making Omelettes</title>
		<link>http://blogs.gnome.org/bolsh/2008/12/05/ffmpeg-strikes-again/comment-page-1/#comment-1889</link>
		<dc:creator>Does FFmpeg Actually Suck? &#124; Breaking Eggs And Making Omelettes</dc:creator>
		<pubDate>Tue, 09 Dec 2008 05:01:59 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/bolsh/?p=748#comment-1889</guid>
		<description>[...] discovered surprisingly few sites dedicated to hating FFmpeg. These stood out: FFMpeg strikes (again) and ffmpeg sucks. One comment even pointed out that there are no ffmpegsucks.tld domains registered [...]</description>
		<content:encoded><![CDATA[<p>[...] discovered surprisingly few sites dedicated to hating FFmpeg. These stood out: FFMpeg strikes (again) and ffmpeg sucks. One comment even pointed out that there are no ffmpegsucks.tld domains registered [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Dennedy</title>
		<link>http://blogs.gnome.org/bolsh/2008/12/05/ffmpeg-strikes-again/comment-page-1/#comment-1888</link>
		<dc:creator>Dan Dennedy</dc:creator>
		<pubDate>Mon, 08 Dec 2008 20:23:31 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/bolsh/?p=748#comment-1888</guid>
		<description>This is a general problem with interface versioning and not exclusive to ffmpeg. I use FFmpeg a lot, and it&#039;s changes are not exceedingly frequent or annoying IMO. People are claiming gstreamer&#039;s API is stable, but I remember in Phonon planning, KDE devs complaining that gstreamer would not guarantee a stable interface. And what is to prevent someone trying to build gst-ffmpeg to get their app to work from running into the same problem? So, that is not the solution. A software release is simply a check point in time with little guarantees about scarcity of bugs or build problems. Therefore, a Subversion revision number in a project where policy on trunk head is very strict with the more significant patches getting mailing list review is just as valid. I recommend someone trying to build a project against FFmpeg that does not include a snapshot or revision number to grab a revision from a week or two prior to the date of the app&#039;s release. I like Moonlight&#039;s solution; I will start doing that. I think most complaints here are about things changing and breaking. Well, I have learned that is quite the norm as a FOSS developer. Yeah, it sucks to deal with, but I try to maintain hope that it is just a sign of things evolving and progressing.</description>
		<content:encoded><![CDATA[<p>This is a general problem with interface versioning and not exclusive to ffmpeg. I use FFmpeg a lot, and it&#8217;s changes are not exceedingly frequent or annoying IMO. People are claiming gstreamer&#8217;s API is stable, but I remember in Phonon planning, KDE devs complaining that gstreamer would not guarantee a stable interface. And what is to prevent someone trying to build gst-ffmpeg to get their app to work from running into the same problem? So, that is not the solution. A software release is simply a check point in time with little guarantees about scarcity of bugs or build problems. Therefore, a Subversion revision number in a project where policy on trunk head is very strict with the more significant patches getting mailing list review is just as valid. I recommend someone trying to build a project against FFmpeg that does not include a snapshot or revision number to grab a revision from a week or two prior to the date of the app&#8217;s release. I like Moonlight&#8217;s solution; I will start doing that. I think most complaints here are about things changing and breaking. Well, I have learned that is quite the norm as a FOSS developer. Yeah, it sucks to deal with, but I try to maintain hope that it is just a sign of things evolving and progressing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tester</title>
		<link>http://blogs.gnome.org/bolsh/2008/12/05/ffmpeg-strikes-again/comment-page-1/#comment-1886</link>
		<dc:creator>Tester</dc:creator>
		<pubDate>Sun, 07 Dec 2008 17:57:21 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/bolsh/?p=748#comment-1886</guid>
		<description>The other problem with ffmpeg is that the various distributions that distribute it refuse to use the embedded version of ffmpeg into the various packages, but want to use a single version for everyone.. And this will guarantee pain.</description>
		<content:encoded><![CDATA[<p>The other problem with ffmpeg is that the various distributions that distribute it refuse to use the embedded version of ffmpeg into the various packages, but want to use a single version for everyone.. And this will guarantee pain.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris S.</title>
		<link>http://blogs.gnome.org/bolsh/2008/12/05/ffmpeg-strikes-again/comment-page-1/#comment-1885</link>
		<dc:creator>Chris S.</dc:creator>
		<pubDate>Sun, 07 Dec 2008 12:24:50 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/bolsh/?p=748#comment-1885</guid>
		<description>Now now there Dave, just remember that all &lt;i&gt;good&lt;/i&gt; apps &lt;a href=&quot;http://lists.mplayerhq.hu/pipermail/ffmpeg-devel/2005-August/002999.html&quot; rel=&quot;nofollow&quot;&gt;&lt;i&gt;statically&lt;/i&gt; link&lt;/a&gt; to ffmpeg.</description>
		<content:encoded><![CDATA[<p>Now now there Dave, just remember that all <i>good</i> apps <a href="http://lists.mplayerhq.hu/pipermail/ffmpeg-devel/2005-August/002999.html" rel="nofollow"><i>statically</i> link</a> to ffmpeg.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sam Morris</title>
		<link>http://blogs.gnome.org/bolsh/2008/12/05/ffmpeg-strikes-again/comment-page-1/#comment-1884</link>
		<dc:creator>Sam Morris</dc:creator>
		<pubDate>Sat, 06 Dec 2008 12:26:22 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/bolsh/?p=748#comment-1884</guid>
		<description>It amazes me that anyone still develops software against FFMPEG rather than GStreamer or other multimedia libraries with a sane release process. :)</description>
		<content:encoded><![CDATA[<p>It amazes me that anyone still develops software against FFMPEG rather than GStreamer or other multimedia libraries with a sane release process. <img src='http://blogs.gnome.org/bolsh/wp-content/mu-plugins/tango-smilies/tango/face-smile.png' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex</title>
		<link>http://blogs.gnome.org/bolsh/2008/12/05/ffmpeg-strikes-again/comment-page-1/#comment-1883</link>
		<dc:creator>Alex</dc:creator>
		<pubDate>Fri, 05 Dec 2008 18:41:11 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/bolsh/?p=748#comment-1883</guid>
		<description>Also, make sure you have 
libswscale-dev installed
on ubuntu that will put the header in /usr/include/ffmpeg/swscale.h</description>
		<content:encoded><![CDATA[<p>Also, make sure you have<br />
libswscale-dev installed<br />
on ubuntu that will put the header in /usr/include/ffmpeg/swscale.h</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: blibx</title>
		<link>http://blogs.gnome.org/bolsh/2008/12/05/ffmpeg-strikes-again/comment-page-1/#comment-1882</link>
		<dc:creator>blibx</dc:creator>
		<pubDate>Fri, 05 Dec 2008 18:38:47 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/bolsh/?p=748#comment-1882</guid>
		<description>Just install libswscale-dev.

Cheers</description>
		<content:encoded><![CDATA[<p>Just install libswscale-dev.</p>
<p>Cheers</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex</title>
		<link>http://blogs.gnome.org/bolsh/2008/12/05/ffmpeg-strikes-again/comment-page-1/#comment-1881</link>
		<dc:creator>Alex</dc:creator>
		<pubDate>Fri, 05 Dec 2008 18:17:48 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/bolsh/?p=748#comment-1881</guid>
		<description>@Victor 

It&#039;s the consensus of the ffmpeg developers that &quot;nobody but Michael passes the &#039;fork test&#039;&quot;. Who are you going to recruit to work on this new ffmpeg. None of the current developers seem to want to deal with the hassle of releases. 


If you want a stable interface to ffmpeg probably the best way to go is gstreamer-ffmpeg.</description>
		<content:encoded><![CDATA[<p>@Victor </p>
<p>It&#8217;s the consensus of the ffmpeg developers that &#8220;nobody but Michael passes the &#8216;fork test&#8217;&#8221;. Who are you going to recruit to work on this new ffmpeg. None of the current developers seem to want to deal with the hassle of releases. </p>
<p>If you want a stable interface to ffmpeg probably the best way to go is gstreamer-ffmpeg.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam Williamson</title>
		<link>http://blogs.gnome.org/bolsh/2008/12/05/ffmpeg-strikes-again/comment-page-1/#comment-1880</link>
		<dc:creator>Adam Williamson</dc:creator>
		<pubDate>Fri, 05 Dec 2008 18:11:37 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/bolsh/?p=748#comment-1880</guid>
		<description>Well, the error is actually pretty simple:

error: ffmpeg/swscale.h: No such file or directory

thanks to the multiple different versions of ffmpeg floating around, and different distribution policies, the ffmpeg headers can show up in lots of different places. Find out where your distro actually keeps swscale.h, and patch the build to look for it there. You may have to fix some other similar issues, but doing that should basically work.

However, overall, yes it is that hard. The ffmpeg guys really *do* break API compatibility all the time, they&#039;re not joking. So you can either keep a static copy of it in every fricking app that uses it, or build against the system one and hope it keeps working, which it probably won&#039;t. Neither&#039;s a good choice. We have a selection of both, in Mandriva.</description>
		<content:encoded><![CDATA[<p>Well, the error is actually pretty simple:</p>
<p>error: ffmpeg/swscale.h: No such file or directory</p>
<p>thanks to the multiple different versions of ffmpeg floating around, and different distribution policies, the ffmpeg headers can show up in lots of different places. Find out where your distro actually keeps swscale.h, and patch the build to look for it there. You may have to fix some other similar issues, but doing that should basically work.</p>
<p>However, overall, yes it is that hard. The ffmpeg guys really *do* break API compatibility all the time, they&#8217;re not joking. So you can either keep a static copy of it in every fricking app that uses it, or build against the system one and hope it keeps working, which it probably won&#8217;t. Neither&#8217;s a good choice. We have a selection of both, in Mandriva.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
