Re: [FFmpeg-devel] [PATCH 2/3] libavcodec: add NETINT Quadra HW decoders & encoders

From: Timo Rothenpieler <timo@rothenpieler.org>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH 2/3] libavcodec: add NETINT Quadra HW decoders & encoders
Date: Wed, 9 Jul 2025 14:04:46 +0200
Message-ID: <5569e4b0-8101-4e6e-a52b-fafea5de510d@rothenpieler.org> (raw)
In-Reply-To: <YT2PR01MB6673407723B99A4B521B64EBFE49A@YT2PR01MB6673.CANPRD01.PROD.OUTLOOK.COM>

On 09/07/2025 04:11, Desmond Liu wrote:
> Hi Ronald, thanks for your response.
> 
>> We previously had a similar debate regarding realmedia (search for "Codec
>> wrapper for librv11 and RMHD muxer/demuxer").
> 
> I couldn't find much in the way of debate when I searched for this except
> for a patch submission in Jan 2018. Was this debate in #ffmpeg-devel IRC?
> 
>> The debate comes down to this:
>> - it's clear that for the company, there's a huge advantage in patches
>> being upstream. For example, upstream does maintenance/upkeep for free.
>> - it's not clear whether there is any benefit to the community / project in
>> this patch being upstream. For example, how do we test this code in fate?
> 
> As far as I can tell, FATE doesn't test hwaccel codecs/filters. But
> we can donate some hardware for FATE testing if needed. We plan on
> continuous testing against master to ensure upstream FFmpeg changes
> don't break our specific changes. We may also have to donate some VMs to
> help with testing.
> 
>> The fact that something is for sale does not mean it's a general benefit to
>> the FFmpeg developer or user community.
> 
> There were some developers in #ffmpeg-devel IRC that thought we should upstream.
> 
> Our Netint Quadra hardware has been used by a large customer base including
> several large cloud service providers in production for high density video
> encoding and decoding.
> 
> There is a lot of interest in using FFmpeg with our ASIC hardware from regular
> developers. We've made our ASIC hardware available via Akamai cloud. You can
> provision a VM, then use our publicly available FFmpeg changes to work with our
> ASIC. Now regular developers can also easily build high density video encoding
> solutions with ffmpeg in the cloud.

I'm very much in favour of adding support. Assuming it is then also 
properly maintained and not just "dumped" on us.
Of course we can't reasonably add support for every single niche bit of 
hardware, but this seems mature and adopted enough to me to warrant it.
_______________________________________________
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".