[FFmpeg-devel] [RFC]] swscale modernization proposal

Niklas Haas ffmpeg at haasn.xyz
Mon Jun 24 17:33:14 EEST 2024


On Sun, 23 Jun 2024 14:57:31 -0300 James Almer <jamrial at gmail.com> wrote:
> On 6/22/2024 7:19 PM, Vittorio Giovara wrote:
> > Needless to say I support the plan of renaming the library so that it can
> > be inline with the other libraries names, and the use of a separate header
> > since downstream applications will need to update a lot to use the new
> > library (or the new apis in the existing library) and/or we could provide a
> > thin conversion layer when the new lib is finalized.
> 
> I don't quite agree with renaming it. As Michael already pointed out, 
> the av prefix wouldn't fit a scaling library nor a resampling one, as 
> they only handle one or the other.

By this logic, both libswscale and libswsresample should be merged into
libavscale. The mathematics of resampling and scaling is the same :)

Anyway, renaming a library needs a really strong motivating reason, and
I don't see that reason being present here. As discussed further
up-thread, I will try and re-use the existing swscale public API, but
internally restructure things so that SwsContext is itself the
"high-level wrapper" that I intended <avscale.h> to be.

We are very fortunate that SwsContext is entirely private, so I'm not
too concerned about the code implications of this. At worst it will
involve a bunch of renaming commits.

> There's also the precedent of avresample, which was ultimately dropped 
> in favor of swresample, so trying to replace swscale with a new avscale 
> library will be both confusing and going against what was already 
> established.
> _______________________________________________
> ffmpeg-devel mailing list
> ffmpeg-devel at ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
> 
> To unsubscribe, visit link above, or email
> ffmpeg-devel-request at ffmpeg.org with subject "unsubscribe".


More information about the ffmpeg-devel mailing list