From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ffbox0-bg.ffmpeg.org (ffbox0-bg.ffmpeg.org [79.124.17.100]) by master.gitmailbox.com (Postfix) with ESMTPS id 27B574E33E for ; Wed, 9 Jul 2025 12:04:37 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.ffmpeg.org (Postfix) with ESMTP id 1A40C68E90A; Wed, 9 Jul 2025 15:04:31 +0300 (EEST) Received: from btbn.de (btbn.de [144.76.60.213]) by ffbox0-bg.ffmpeg.org (Postfix) with ESMTPS id 0984268E7F5 for ; Wed, 9 Jul 2025 15:04:23 +0300 (EEST) Received: from [authenticated] by btbn.de (Postfix) with ESMTPSA id 664A827FFCCBE for ; Wed, 09 Jul 2025 14:04:22 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rothenpieler.org; s=mail; t=1752062662; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=ZRFJ3be8k4zQWEVO25LeKOEHJ8oCqmRYv4uG/43j/co=; b=qCNN72jv8GhJLpJ2vaGE0Ptw3GTsC4aykNs2GhwecWGqSCJMv5z8e6Vw+O8wrN1J9Ktack GTXO6NzasKCFxjylw9COSzVtzk+RUEg+INf8SnbLmN49hfUbBLoaylNlRy5jJl+3vR+W4U Mk1r73M7piqERLXlskVbdP3b/HhfGeONRqrwaPWjIZBhHek+ThivOnnyiZIarPPVSdU4yG R5Ay51KDAOWY3kP0NGsyW/cVEIOASuxZLjJgmfsX7BakJCgUw/GHEicS3v/LFUl0t9Gdj+ GDSD3qVfTBR9Oe2HPdoQnbclMTG6fd7qQ1ycLIcDTQL6Pno7k5VvDQkSsMeJZg== Message-ID: <5569e4b0-8101-4e6e-a52b-fafea5de510d@rothenpieler.org> Date: Wed, 9 Jul 2025 14:04:46 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird To: ffmpeg-devel@ffmpeg.org References: Content-Language: en-US, de-DE From: Timo Rothenpieler In-Reply-To: Subject: Re: [FFmpeg-devel] [PATCH 2/3] libavcodec: add NETINT Quadra HW decoders & encoders X-BeenThere: ffmpeg-devel@ffmpeg.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FFmpeg development discussions and patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: FFmpeg development discussions and patches Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: 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".