Hi On Wed, May 14, 2025 at 11:41:35AM +0100, Kieran Kunhya via ffmpeg-devel wrote: > On Wed, May 14, 2025 at 11:21 AM Michael Niedermayer > <mich...@niedermayer.cc> wrote: > > > > Hi Andrew > > > > On Wed, May 14, 2025 at 05:54:54AM +0300, Andrew Randrianasulu wrote: > > > ср, 14 мая 2025 г., 03:55 Andrew Randrianasulu <randrianas...@gmail.com>: > > > > > > > > > > > > > > > вт, 6 мая 2025 г., 02:27 Michael Niedermayer <mich...@niedermayer.cc>: > > > > > > > >> This will be available in https://github.com/michaelni/libpostproc > > > >> either as a separate library or a ffmpeg source plugin whatever turns > > > >> out more convenient to maintain > > > >> > > > > > > > > > > > > > > > > Congratulations, you broke building cinelerra-gg with ffmpeg.git > > > > despite > > > > our best efforts :/ > > > > > > > > Why all this code movement?! > > > > > > > > For whom it "simple"? > > > > > > > > > > > > > For some reason this mail not arrived into my inbox (spam filter ate it?) > > > > > > https://ffmpeg.org/pipermail/ffmpeg-devel/2025-May/343192.html > > > > > > ===== > > > > > > The idea of course here is to expand this to filters and other > > > things. Which again is trivial, nothing really is needed except > > > people simply following this style of a source plugin > > > > > > > > > ===== > > > > > > I found this concerning. Because does this mean ffmpeg will be fragmented > > > like Python or Rust into million pieces users supposed to held together? > > libpostproc never really fit in FFmpeg,
libostproc implements part of ISO/IEC 14496-2 (MPEG-4) > has a lot of out of date code > and that's why it was removed. > > > > > simple awnser, no > > > > There is an increasing number of filters which do not fit into FFmpeg. > > For a wide range of reasons. ATM these are simply inaccessable and > > invissible to users. > > With plugins you will be able to use filters that have ugly dependancies, > > or cannot be in main FFmpeg for other reasons. > > Or you can also choose not to touch them. > > > > If there is interrest we can make releases with and without all plugins > > (in fact i intend to include libpostproc in the next relaase) > [...] > We should encourage users to upstream patches. we already do and will always continue to do that The problem is that many things "Dont fit" in someones view. to quote yourself from this very same email according to you "libpostproc never really fit in FFmpeg," And while libpostproc is old and out of date, this view is not limited to "old and out of date" code. We had encoders, and modern AI filters rejected. Some quite recently And when things cannot be developed in the main repository They will be developed elsewhere. Thats how free software works I always stood for innovation and for supporting a full set of features And when that cannot be done in the main repository sometimes for good (technical) reasons and sometimes for bad reasons. Plugins is the awnser where every developer can continue to work on what they are passionate about and love doing Though this is sliding a bit off topic Thx [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB If you think the mosad wants you dead since a long time then you are either wrong or dead since a long time.
signature.asc
Description: PGP signature
_______________________________________________ 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".
