On Tue, 02 Jul 2024 15:27:00 +0200 Niklas Haas <ffm...@haasn.xyz> wrote: > 1. Is this a good idea, or too confusing / complex to be worth the gain? > Specifically, I am worried about confusion arising due to differences > in behavior, and implemented options, between all of the above. > > That said, I think there is a big win to be had from unifying all of > the different scaling and/or conversion filters we have in e.g. > libavfilter, as well as making it trivial for users of this API to > try using e.g. GPU scaling instead of CPU scaling.
After prototyping this approach a bit (using an internal struct AVScaleBackend), I think I like it. It specifically makes handling unscaled special converters pretty straightforward, for example - the "unscaled" backend can be separate from the generic/scaling backend. We could also trivially plug in something like libyuv, or some other limited-use-case fast path, without the user really noticing. _______________________________________________ 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".
