[FFmpeg-devel] [RFC] libpostproc splitout

[Michael Niedermayer]

Hi Remi

On Sat, Nov 09, 2024 at 08:21:24PM +0200, Rémi Denis-Courmont wrote:
> Le lauantaina 9. marraskuuta 2024, 18.11.07 EET Michael Niedermayer a écrit :
> > > And sorry but while I am all for splitting postproc to a separate
> > > repository, it is at best a few hundreds euros worth of consulting time.
> > > The difficult part, if there is one, is to reach the agreement to do it,
> > > not to actually do it.
> > Iam sorry but spliting out libpostproc into a maintainable seperate source
> > tree with self tests and everything is not just "a few hundread euros work".
> 
> Your question was literally whether "should libpostproc be split out into a 
> seperate (sic) source repository". I maintain that that would be worth a 
> couple hundred eurors - if it had not already been done.
> 
> The question of maintaining libpostproc is mostly orthogonal. The value of 
> that work could be essentially anything from zero to hundred of thousands, 
> since it is completely dependent on how much additions and renovations are 
> taken up.
> 
> However if we assume that the library is to be split out, then this is no 
> longer a matter for FFmpeg-devel, making everybody here incompetent (in the 
> judicial sense) to answer the question.
> 
> On the other hand, if we assume that it does not get separated, I think the 
> lack of activity tells about the impopularity of the library. I don't see the 
> point in spending time and/or money if nobody cares anymore, unless this is a 
> research project but that does not seem to be what you are proposing.

libpostproc needs bugtracking, selftests, fuzzer support, documentation,
its API would need to be updated to match todays features.
(like any library would need)
It also needs to be possible to pull in updates from FFmpegs build system
and other parts.

What people here are fixed on is to kill teh library off. And this exactly
was always the disagreement from what i remember.

Just flip the sides, libavfilter doesnt need bugtracking ? doesnt need fuzzing ?
doesnt need documentation ?

libpostproc is part of FFmpeg it is not "outside" FFmpeg or "outside"
the STF scope.

The reason for me to consider to split libpostproc out is to be able to
work on the code without the eternal debates here. So i need it to be
maintainable and i need it to support a wider range of filters. Its not
writen in the contracts so I dont have to do any of that but it was a todo.

If everything stays in FFmpeg, and the debate problem is solved another way
thats great too.

Also about cost, this debate in this thread costs the same time that
writing code does.

thx

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

The real ebay dictionary, page 2
"100% positive feedback" - "All either got their money back or didnt complain"
"Best seller ever, very honest" - "Seller refunded buyer after failed scam"
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <https://ffmpeg.org/pipermail/ffmpeg-devel/attachments/20241111/103a2f2b/attachment.sig>