On Mon, Feb 13, 2012 at 5:48 AM, Brian Matherly <pez4br...@yahoo.com> wrote: >> 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. >
No, I just have git repos and several release tarball dirs. Then, I manually cd ffmpeg-foo, make uninstall, cd ../ffmpeg-bar, make install, cd ../mlt, make -C src/modules/avformat clean all, sometimes make encoding test or just run melt -query codecs, etc. > 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. If you recall, for the longest time, releases were far and few between, and there was only ffmpeg. In that mode, all I needed to do is update things as the head creeps along being careful to not break the older code. That combined with user feedback and testing against distro packages on a few different personal systems and sometimes a couple of VMs seemed sufficient. The releases are still rather superficial as far as how it affects that mode of operation. However, the forking and rate of change has become a problem. Thanks to you we have begun some automation now. However, I am not certain how much you should expand it. You could reduce the frequency to daily, supply an argument to the script to use a release tarball, and cache the downloaded tarball. Thoughts? -- +-DRD-+ ------------------------------------------------------------------------------ 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 Mlt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mlt-devel
