{"id":2336,"date":"2010-03-27T20:29:19","date_gmt":"2010-03-28T04:29:19","guid":{"rendered":"http:\/\/multimedia.cx\/eggs\/?p=2336"},"modified":"2010-03-27T20:29:19","modified_gmt":"2010-03-28T04:29:19","slug":"compatibility-testing-with-fate","status":"publish","type":"post","link":"https:\/\/multimedia.cx\/eggs\/compatibility-testing-with-fate\/","title":{"rendered":"Compatibility Testing With FATE"},"content":{"rendered":"

Once upon a time, I made a valiant effort to create a compatibility page for FFmpeg<\/a>. The goal was simple– document how to use FFmpeg<\/a> to generate media files that would play back in the most common media players of the day. At the time, this included Windows Media Player and Apple QuickTime Player. The exercise was naturally obsolete quite quickly due to the fact that I used some random SVN revision (actually, this is so old that I think we were still using CVS at the time).<\/p>\n

I still think this is a worthwhile idea. I now realize that the idea can be improved by FATE<\/a>. Create a series of test specs that map to a certain encoding combination known to work on a popular media player (or even a popular media device– this could be used for testing, e.g., iPod profiles) and document the command lines on the website. When one of the command lines breaks for all configurations, it will be worth investigating to learn why and whether the website example needs to be updated, or whether FFmpeg needs to be fixed.<\/p>\n

Testing process:<\/p>\n