On 1 August 2017 at 12:30, 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. > > -- > Clément B. > > _______________________________________________ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org > http://ffmpeg.org/mailman/listinfo/ffmpeg-devel > > I think I'd rather have it as a separate module. The part of the code could grow to be quite big and the API quite complex depending on the needs of encoders and filters. _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
