[FFmpeg-devel] lavfi AVOption redundancy, ffmpeg code cleanup [GSoC]

[FFmpeg-devel] lavfi AVOption redundancy, ffmpeg code cleanup [GSoC]

[Niklas Haas]

Hi,

There was some discussion recently about the possibility of reducing the
amount of ad-hoc file loading in filters by introducing common syntax
for loading AV_OPT_TYPE_BINARY options from files. (vf_libvmaf,
vf_frei0r, vf_libplacebo, vf_vidstabtransform, ...)

Another source of redundancy currently is the code is redundancy of
colorspace configuration options. (vf_colorspace, vf_vectorscope,
vf_libplacebo, vf_setparams, vf_zscale(?)) These could also benefit
from being unified somehow.

The idea was raised to gather more such cleanup work and turn it into a
GSoC project. But I don't think these two tasks alone are enough to fill
the 50-100 hours needed for a project. Does anybody have additional
ideas for low-hanging fruit type cleanup / redundancy elimination work
that needs to be done?
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-devel] lavfi AVOption redundancy, ffmpeg code cleanup [GSoC]

[Paul B Mahol]

On Tue, Mar 1, 2022 at 2:28 PM Niklas Haas <ffmpeg@haasn.xyz> wrote:

> Hi,
>
> There was some discussion recently about the possibility of reducing the
> amount of ad-hoc file loading in filters by introducing common syntax
> for loading AV_OPT_TYPE_BINARY options from files. (vf_libvmaf,
> vf_frei0r, vf_libplacebo, vf_vidstabtransform, ...)
>
> Another source of redundancy currently is the code is redundancy of
> colorspace configuration options. (vf_colorspace, vf_vectorscope,
> vf_libplacebo, vf_setparams, vf_zscale(?)) These could also benefit
> from being unified somehow.
>
> The idea was raised to gather more such cleanup work and turn it into a
> GSoC project. But I don't think these two tasks alone are enough to fill
> the 50-100 hours needed for a project. Does anybody have additional
> ideas for low-hanging fruit type cleanup / redundancy elimination work
> that needs to be done?
>

Rewrite it so various warnings while compiling are finally gone?


> _______________________________________________
> ffmpeg-devel mailing list
> ffmpeg-devel@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>
> To unsubscribe, visit link above, or email
> ffmpeg-devel-request@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-request@ffmpeg.org with subject "unsubscribe".