On 8/1/17, Clément Bœsch <u...@pkh.me> wrote: > On Tue, Aug 01, 2017 at 09:18:33AM +0000, Davinder Singh wrote: > [...] >> > In particular, the main policy of FFmpeg is to not depend on external >> > libraries for core features. Therefore, if your project is a separate >> > >> >> Just to be clear, it won't be "external" library like OpenCV... >> >> >> > library, it will definitely not be used by FFmpeg codecs like you wish >> > in your first paragraph. >> > >> > If you want a fighting chance of a project that is not stillborn, I >> > think you need to make it part of FFmpeg, and make sure important >> > >> >> .. it will be part of FFmpeg like libavfilter, just a new module - >> libmotion. >> > > yeah, but not a good idea. Just make it an optional component of > libavutil.
Why not keep the code in libavcodec? I think that (I)DCT was also given standard API and it is still there. Also some me_cmp_fn use (I)DCT. Best Regards _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
