[FFmpeg-devel] [PATCH v5 00/25] Subtitle Filtering 2022

[Ronald S. Bultje]

Hi,

On Sun, Jul 24, 2022 at 11:10 PM Nicolas George <george at nsup.org> wrote:

> I do not recognize the project I started contributing to more than
> fifteen years ago. I do not even recognize the project that boasted the
> clever optimization framework that made FFVP9 possible, it has become
> increasingly hostile to trying new and more efficient ways of doing
> things in favor of a corporate never-take-risks style of coding.
>

We still do this, but currently outside FFmpeg (dav1d). So sadly, it's a
bit more out of the sphere of this mailinglist. So we take risks, and if
AV2-9 comes around, we might again. But we still consider ourselves part of
the FFmpeg community, and I still try to review ffvp9 patches when they
come up every once in a while. Don't lose hope, just find the positive
things and work on them. Ignore the rest. I know I did. I'm having fun
again.

I don't know if I should offer advice, but my $.02: maybe adding tests (I
don't mean ffmpeg invocations; some people would call this desired
outcomes) might help here. You probably remember how Michael tested patches
pre-FATE: for a particular patch, he'd send an FFmpeg commandline that
either A) gives (undesirable) different output before vs. after patch, or
B) should give some correct/desired output after the patch but (still)
doesn't (and this second would be what I'm inviting you to do). Tests don't
have to be scripted, they can simply be a list of features or behaviors
desired in the new design. It's true that perfection is the enemy of
progress, but I think you're right that we should try to strive for further
improvement if it is within reach, especially for base design or things
with API implications. (FFmpeg's API is a testament to poor design in some
places.) You're likely better at making a comprehensive list than anyone
else. Making the list public/explicit means other people can help
accomplish the full list of features.

<3
Ronald