>> In my mind, the real question is whether this is the straw that causes us
> to drop compatibility with some older ffmpeg versions - in order to clean out > some of the #ifdefs in the code. > > Yeah, I do want to do that because it will be too messy otherwise. One thing we could consider would be to keep the existing module but stop chasing API changes and add a new module that cuts straight to the newest API. Then, we could conditionally compile either one module or the other depending on what version of ffmpeg/libav is detected at compile time. This is a minor nit, but I've never been satisfied with the module name: "avformat". It really isn't very accurate since the module uses avcodec and other libraries from the libav suite. Maybe this would be a good time to make a new module with a new name: "libav" which would be a more accurate name, in my opinion. avformat could be marked as deprecated and eventually dropped (maybe in the 1.0 release or something like that). ~BM ------------------------------------------------------------------------------ Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev _______________________________________________ Mlt-devel mailing list Mlt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mlt-devel
