On Sun, Dec 13, 2020 at 3:03 PM Michael Niedermayer <mich...@niedermayer.cc> wrote:
> On Sun, Dec 13, 2020 at 02:02:33PM +0100, Anton Khirnov wrote: > > Quoting Paul B Mahol (2020-12-13 13:40:15) > > > Why? Is it so hard to fix them work with latest API? > > > > It is not exactly obvious, since coded_frame is gone. I suppose you > > could instantiate an encoder and a decoder to work around that, but it > > all seems terribly inefficient. Lavfi seems to have some ME code, so > > perhaps that could be used for mcdeint. Or if not, maybe someone could > > get motivated to port something from avisynth or vapoursynth. Similarly > > for uspp, surely one can do a snow-like blur without requiring a whole > > encoder. > > > > In any case, seems to me like a good opportunity to find out whether > > anyone cares enough about those filters to keep them alive. I don't > > think we should keep code that nobody is willing to maintain. > > I might do the minimal changes needed to keep these working when i > find the time and if noone else does. Certainly i would not be sad > if someone else would do it before me ;) > > Also if redesign happens, what looks interresting to me would be to > be able to export the needed information from encoders. > Factorizing code from one specific encoder so only it can be used > is less general but could be done too of course > > if OTOH encoders in general could export their internal buffers for filters > or debuging that seems more interresting. > > Are there other issues with these filters which need work besides this > coded_frame use ? > > I think that adding extra API to workaround this issues in filters is ugly direction. IMHO filters should not use lavc code at all. For example what uspp needs/steals from lavc to post-process frames? Also what mcdeint uses from snow encoder in lavc to motion interpolate frames? > thx > > -- > Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB > > Republics decline into democracies and democracies degenerate into > despotisms. -- Aristotle > _______________________________________________ > 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". _______________________________________________ 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".