I'd like to second Nicolas' points. Building and distributing FFmpeg is not
an
easy endeavor, regardless of hobby or commercial projects. Staying up to
date with master and keep rebasing your local filter changes, updating
documentation
so your clients or other hobbyists can build on their machines
Hi all,
Not sure if this should be directed at libav-user instead, feel free to
redirect
me if needed.
I've read the writing_filters.txt documentation and numerous StackOverflow
posts and everything indicates that in order to add your own custom filter,
the
Makefile in libavfilter needs to modifi
onality), but I see how this would break.
Would you see value in me trying to figure out a way to support
reconfiguring
the codec if the width/height/cropping changes mid-stream or would you
reject
the patch/feature regardless?
Thanks!
On Fri, Sep 20, 2024 at 7:18 AM Hendrik Leppkes wrote:
>
ld be curious
to check. Still, the biggest downside we see is GPU VRAM consumption, as
explained above :(
On Fri, Sep 20, 2024 at 9:34 PM Lynne via ffmpeg-devel <
ffmpeg-devel@ffmpeg.org> wrote:
> On 20/09/2024 20:41, Carlos Ruiz wrote:
> >> It's just that the cuviddec decod
> It's just that the cuviddec decoder is more of a relic, from before the
> native hwaccel existed.
> The only reason it's not straight up deprecated is that it's sometimes
> nice to have a "second opinion" when issues crop up, and there are a few
> specific features like hardware-deinterlacing tha
0x360). The values get ignored (as in
FFMpeg master) and I again get 1920x1080 yuvj420p frames out.
I'm not extremely familiar with hevcdec.c so I'm not sure if this would
accidentally break something else. Looking forward to hearing your thoughts!
>From 850afda5f6479064c75a4b905f
