From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ffbox0-bg.mplayerhq.hu (ffbox0-bg.ffmpeg.org [79.124.17.100]) by master.gitmailbox.com (Postfix) with ESMTP id 1B4CD44A96 for ; Tue, 6 Dec 2022 15:08:39 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id A970568B060; Tue, 6 Dec 2022 17:08:36 +0200 (EET) Received: from btbn.de (btbn.de [136.243.74.85]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id A9A5D68B060 for ; Tue, 6 Dec 2022 17:08:29 +0200 (EET) Received: from [authenticated] by btbn.de (Postfix) with ESMTPSA id 1FFEC3AB7FD for ; Tue, 6 Dec 2022 16:08:27 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rothenpieler.org; s=mail; t=1670339307; 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=Hrw6ZIk7pYg9wyRuPo7UDcTD+i7MoPtCP+9hpIpzkII=; b=hK5NCJFV34aXQcsW2vLOa5bS4v0FN1jN/D85ev5ErSUS/Ii5/ApSiuW04WD2fBv/IqewEF E89Aa/UoTf9WskVnCebfDAurht0DS+QGd3P0Gxq6FUU4kXS4Zc0HQmiYI+uwobTp5q0S9h NRbl/HrPzhMuDJm/tGYJFqG2O3K6X7D0zUfVmZ9YIRHY2xccsvDTkkRzKTIvUz4F1LTE9Y GZ8rGMRXGdlvs3l8yyl+gPZPuoZG2fe03HApcL2OZLBrhdN+uxlNswVAPkGcU/Wt8gwOO/ dMpheCfC8Md0/Mlgm7mhkrT+Of41gsM3DiFckMW0koYHSFu3LpTuxvKbOTcIyQ== Message-ID: <07e70ef4-23ae-58fa-fab7-a346b806a29b@rothenpieler.org> Date: Tue, 6 Dec 2022 16:08:49 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.5.1 Content-Language: en-US, de-DE To: ffmpeg-devel@ffmpeg.org References: <20221205133938.505-1-timo@rothenpieler.org> <167033742725.26119.15040760416331150943@lain.khirnov.net> <167033778079.26119.6038146894846925847@lain.khirnov.net> From: Timo Rothenpieler In-Reply-To: <167033778079.26119.6038146894846925847@lain.khirnov.net> Subject: Re: [FFmpeg-devel] [PATCH 1/2] avcodec/thread: add support for frame threading receive_frame based decoders 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 06/12/2022 15:43, Anton Khirnov wrote: > Quoting Timo Rothenpieler (2022-12-06 15:39:50) >> On 06/12/2022 15:37, Anton Khirnov wrote: >>> Quoting Timo Rothenpieler (2022-12-05 14:39:37) >>>> This is fairly basic and makes a lot of assumptions, but it works >>>> for the most simple cases. >>>> >>>> For one, it only ever fetches exactly one packet per call to receive_frame. >>>> Right now it's impossible for there to ever be more than one, but the API >>>> allows for more, which might need handled in the future. >>>> >>>> It also basically translates the new API back to the old, since that's how >>>> the frame threading code operates. Which feels backwards in regards to >>>> the new API, but it was the path with least resistance in implementing this. >>> >>> If it only supports one packet to one frame, then it goes against the >>> whole point of using the receive_frame API. >> >> Otherwise the entirety of pthread_frame.c would need rewritten from >> scratch. It has that assumption coded into it. > > I told you on IRC I already have a mostly-finished branch that > implements threading with receive_frame(), so I don't really understand > what's the point of your writing this patch. > You said it wasn't even in a state to be tested. Do you have a link to it? Happy to help finishing it up. _______________________________________________ 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".