On Sat, Feb 11, 2012 at 7:48 PM, Brian Matherly <pez4br...@yahoo.com> wrote: > Dan, > > I see that our friends at ffmpeg have changed the libavcodec interface: > http://git.videolan.org/?p=ffmpeg.git;a=commit;f=libavcodec/avcodec.h;h=52f82a11489af88960c8774c142cbde78063365f > > MLT git HEAD currently has two problems when compiled against ffmpeg git > HEAD (that I know of) > 1) MLT gets deprecation warnings for avcodec_encode_audio() and > avcodec_encode_video()
it should be ok for now unless it is needed to fix x264 > 2) MLT does not detect libx264 because it uses the new "encode2" field in > AVCodec but this is a problem > What's your policy on chasing ffmpeg API changes? Do it right away, or wait > for things to calm down? If it breaks something popular or really needed by some client, do it right away. > There are a lot of "#if LIBAVCODEC_VERSION_INT..." conditionals in the > libavformat module. How far back should MLT support with respect to old > libav API versions? I think I want to still support ffmpeg 0.5 a while longer. > Is this worth holding back whatever release you are working on? I could say yes, but at this rate, the day after release it can be broken again. Still, I do not like the idea of the new release being broken when using the build scripts. > Let me know if you want any help getting the avformat module updated. I'll > probably start hacking on it anyway since I would like to see libx264 > working again. go for it -- +-DRD-+ ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ Mlt-devel mailing list Mlt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mlt-devel
