> > for libxml2 these problems are less likely to hit us as we likely never > need a > "new xml feature" but for a (de)muxer we quite likely will need the > latests version on every platform. > Also we have regression tests, external libs make that impossible > as the version of external libs can change the behavior. Again this > is a issue for mxf maybe less so libxml. You can also see that we have no > tests involving any of the external encoder libs, for that very reason. > With each external lib that is needed for core features this would > become a quickly growing problem > >
Going back to technical arguments instead of utopian pipedreams (replacing YouTube and Tiktok lol). You will never fit all the features of complex containers like MXF, MP4, TS (and for argument's sake XML) inside a generalised framework like FFmpeg. Likewise with dav1d, we have seen that an external lib has allowed them to introduced new paradigms such as mixed frame and sliced threads without having to redo the whole framework of dozens of codecs. There is value to this. There are also a lot of modern codec features which aren't easily fittable into FFmpeg such as dependent substreams. Kieran Sent from my mobile device _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
