{"id":2210,"date":"2010-02-11T23:18:40","date_gmt":"2010-02-12T07:18:40","guid":{"rendered":"http:\/\/multimedia.cx\/eggs\/?p=2210"},"modified":"2010-02-13T11:13:22","modified_gmt":"2010-02-13T19:13:22","slug":"indeo-5-and-partial-bink-in-ffmpeg","status":"publish","type":"post","link":"https:\/\/multimedia.cx\/eggs\/indeo-5-and-partial-bink-in-ffmpeg\/","title":{"rendered":"Indeo 5 and Partial Bink in FFmpeg"},"content":{"rendered":"

There have been some great additions to FFmpeg<\/a> in recent weeks. Most notable is an Indeo 5<\/a> video decoder. Congratulations to everyone who worked hard to reverse engineer this codec that was used in quite a few video games. The sample I selected for a FATE test spec is called Educ_Movie_DeadlyForce.avi<\/a>:<\/p>\n


\n\"SWAT
\n<\/center><\/p>\n

The video is much funnier in its original context<\/a> (though it’s no longer posted there). Thankfully, the math behind Indeo 5 is bit exact which allows me to enter a test spec right away.<\/p>\n

While Indeo 5 was used in quite a few PC games through the years, no game-related format can touch Bink<\/a>. FFmpeg now includes a Bink file demuxer. Further, FFmpeg now has decoders for both variations of Bink audio<\/a> (designated DCT and RDFT), which can also occur in Smacker files<\/a>.<\/p>\n

So I added new FATE<\/a> test specs to cover those new additions. I also went through the FATE test coverage wiki page<\/a> and eliminated a bunch of low-hanging fruit. Sometimes, there were samples (some difficult to find) at the samples archive<\/a>; other times, it was necessary to do a Google search for “filetype:<file extension>”. To give you an idea of the current trends in the shifting sands of the internet, such searches invariably seem to yield Facebook pages as their top hits.<\/p>\n

These are the new FATE tests:<\/p>\n