Hi, On Wed, Nov 11, 2020 at 10:45 AM Anton Khirnov <an...@khirnov.net> wrote:
> Quoting James Almer (2020-11-11 14:13:07) > > I don't recall anything about splitting IO, but what does it achieve > > beyond making lavf lighter? Are there users out there that could care > > about linking to an hypothetical lavio while not caring about other lavf > > functionality? > > Yes, I recall several people expressing interest in a separate libavio. > > Also, I believe it would be good for us internally, since it would > - allow other libraries to do IO cleanly without depending on lavf > - force us to clean up avio public API, which is not in a great shape Avio public API would be great, regardless of library split. Certain companies using ffmpeg in their transcoding system want only their own I/O. I doubt they care much for the binary size saved from not linking to lavio, but stable public API is important. Ronald _______________________________________________ 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".
