> I checked with libav.org head, and it did not work. Your check is for > too recent a version. In libav, libx264 switched to encode2 with > 54.0.0. However, the struct was changed in version 53.34.0. See > ffmpeg/doc/APIchanges for that info. This change to MLT is not > dependent upon when libx264 codec was switched, it only needs the API > change. There are other codecs that switched to encode2 earlier than > x264. I revised your commit and applied it.
Do you have some kind of secret method to easily test MLT against various branches/releases of ffmpeg/libav? If so, I would like to know about it. By my count, we could be supporting 10 to 12 different variations (depending on how you count the older ones): * FFmpeg HEAD * FFmpeg 0.10 "Freedom" * FFmpeg 0.9.1 "Harmony" * FFmpeg 0.8.10 "Love" * FFmpeg 0.7.11 "Peace" * FFmpeg 0.6.5 "Works with HTML5" * FFmpeg 0.5.8 "half-way to world domination A.K.A. the belligerent blue bike shed" * Libav HEAD * Libav 0.8 "Forbidden Fruit" * Libav 0.7.4 "The Big Bump" * Libav 0.6.5 "Works with HTML5" (same as FFmpeg?) * Libav 0.5.7 "half-way to world domination A.K.A. the belligerent blue bike shed" (same as FFmpeg?) If we want to chases all of these variations, then I think some automation is in order. ~BM ------------------------------------------------------------------------------ Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 _______________________________________________ Mlt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mlt-devel
