On Sat, Sep 29, 2018 at 6:04 AM Rostislav Pehlivanov <atomnu...@gmail.com> wrote: > I'd much rather go with the original intent which was to merge the decoder > into lavc.
Ronald can correct me if I'm wrong, but I suspect a key goal behind the decoder was to have a standalone library which could be shared across a variety of projects (both open and closed source). Merging it in directly will create a maintenance headache as the two source trees diverge. It also makes unit testing more difficult, since Ronald/VideoLAN can write unit tests for the library (which will presumably be consumed by a number of projects/products) and be confident that those same unit tests apply to the version that is used by ffmpeg. I don't think having libx264/libx265 out of tree hasn't been a nightmare for anyone. I don't think this case would be any different. Devin -- Devin J. Heitmueller - Kernel Labs http://www.kernellabs.com _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel