On Tue, 3 Jan 2023 at 03:13, Philip Langdale <phil...@overt.org> wrote:
> On Tue, 3 Jan 2023 02:39:19 +0300 > Dennis Mungai <dmng...@gmail.com> wrote: > > > Related, > > > > If this were to be implemented in mpv, can libplacebo pick up this > > feature spec as a filter in ffmpeg? Perhaps that would make such a > > feature easier to merge down the line, instead of re-implementing it > > directly in ffmpeg as an additional filter. > > > > Adding Niklaas to the thread. > > It doesn't make a difference. The licensing is fundamentally unusable > for an open-source project (and there are engineers at nvidia who know > this and wish they could write filters leveraging all their various > capabilities). The only thing with any nuance is what level of > `nonfree` a project is willing to have sitting in their repo. Most > projects (including mpv and libplacebo) would say "none", because it's > not worth the trouble. ffmpeg has gone back and forth on what exact > critera have to be met to qualify as mergeable vs unmergeable nonfree. > In the past we have accepted filters based around nvidia libraries with > prohibitive licensing - see the libnpp based filters, but I don't think > we have the appetite for that now. If we were to decide that this > filter was ok on that basis, I'd merge it, but honestly, the usability > benefit of it being in master is tiny vs all the other hoops you have > to jump through. > > Anyway - punchline: it is not easier to get this kind of thing merged > into other projects. > > --phil > Got it, thanks for the clarifications. _______________________________________________ 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".
