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 064E64461A for ; Tue, 20 Dec 2022 16:15:09 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 82C4E68BA81; Tue, 20 Dec 2022 18:15:06 +0200 (EET) Received: from mail-oi1-f177.google.com (mail-oi1-f177.google.com [209.85.167.177]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 8C6A868AF94 for ; Tue, 20 Dec 2022 18:14:59 +0200 (EET) Received: by mail-oi1-f177.google.com with SMTP id o66so9540452oia.6 for ; Tue, 20 Dec 2022 08:14:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:in-reply-to:from:content-language :references:to:subject:user-agent:mime-version:date:message-id:from :to:cc:subject:date:message-id:reply-to; bh=W2OzeAr4q25qjLrRhmQg3i7uytJR3yVsnXWrKL/HJIU=; b=QtAWTdC00Zrtk13X7LrJA5xxLc+2XLynqIhJvOr5AvQKAL42HrgL/IIwdR0iO0I3RR 5gJh6+KX8Do7UkhCx6tMDpsmop1yIRdlL/XRHo9lP1/pfCauQsoms3gDbdPeimIxxEFg b1vaaAXahYRztIk9u1V2dcnJNhgwUeeKIXqNPDe2B0aeHiuANfYeJM4Ng8GtJMN6dBm3 71JlrMplFPINwjv/sAtZ7s4toQK/GfPr6YJt8uJV7Buwz97YtyQxkYCRlHkIk1dAGfV3 P/rQUeuQyPHyPf386ZxlNbS/brwV77jSsLyxGSHE388mi0wkAEikNnRtGIzX/YhEtXr1 p1GA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:content-language :references:to:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=W2OzeAr4q25qjLrRhmQg3i7uytJR3yVsnXWrKL/HJIU=; b=3yqIpD8Lj5u0My2dU976AKpbUlJHQTrGboRmNZ5UU/G6vG7S6diNCeA+HTzn3ImDUV lLHxjGBxzdxsU7qzqyhWNwz0q/VZpKkcFm45Jo+HkgfiHSXC+o78i/1/fQupoCJFUBkZ 8GQlWEJbc3ohfwKks4HmM+Y7yL1Zbnr/2m8ecp11lZMXKWPkYMYgqt949pj20DEY63HZ ADpIDykigPxXIcEwU7KiFgre2qCFg4Ajj/YJJeSIb1Sdy9qYfsLwXKCPIBLn58VwB6tc XXr82VmgM8xKy9We8mBYBJobAPCaqEEirJI39Tc9XB5tCtgUr+XjojT3bO0ERYIP61rq Rsmw== X-Gm-Message-State: ANoB5pmiYkKjgf8RqC3z28mE6Ol1K5PfdpWPxqgrm//Uf/cp/sIcZ96f Tf3MBsvOTeQZPRToXQ4GS86RTRoK2Cc= X-Google-Smtp-Source: AA0mqf6DeR2w8ek20KE1xTDLu7a8pJhpUJ5vvWIuEV7DRVmjDCS775oVrHvXPRAxIVf4Xia96pfLdw== X-Received: by 2002:a54:4892:0:b0:35e:4002:d914 with SMTP id r18-20020a544892000000b0035e4002d914mr20490736oic.2.1671552897433; Tue, 20 Dec 2022 08:14:57 -0800 (PST) Received: from [192.168.0.11] (host197.190-225-105.telecom.net.ar. [190.225.105.197]) by smtp.gmail.com with ESMTPSA id q12-20020a9d7c8c000000b0067781a9292asm4321187otn.2.2022.12.20.08.14.56 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 20 Dec 2022 08:14:56 -0800 (PST) Message-ID: Date: Tue, 20 Dec 2022 13:15:24 -0300 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.6.0 To: ffmpeg-devel@ffmpeg.org References: <20221213181742.GK3806951@pb2> <20221214015059.35787-1-timo@rothenpieler.org> Content-Language: en-US From: James Almer In-Reply-To: Subject: Re: [FFmpeg-devel] [PATCH v6] lavc: convert frame threading to the receive_frame() pattern 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 12/20/2022 1:06 PM, Timo Rothenpieler wrote: >> >> Generally, I don't see the advantage of this. The only decoder that >> would benefit from it is SMVJPEG, yet for all other codecs it will just >> involve more allocs+frees. > > Being unable to support newer encoders because only the old (and I > thought deprecated, but apprently not, given encoders are getting ported > back to it??) is a pretty bad situation, and could hold back some progress. Decoders. And what was deprecated and removed was the public API, not the internal callback. For 1:1 decoders, or decoders with no delay or buffering, the decoupled input/output callback is overkill, so you'll keep seeing new decoders added using the old one in the future. But similarly, new decoders can and will be added using the decoupled IO callback, so this change is necessary so any future decoder that intends to have frame threading isn't forced to use the old callback when it could benefit from the new. An obvious case would be the (hopefully) eventual native AV1 decoder. > > So adding the ability for frame threading to work for everything seems > natural and neccesary to me. Yes. _______________________________________________ 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".