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 C71524E3FF for ; Mon, 9 Jun 2025 20:59:46 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.ffmpeg.org (Postfix) with ESMTP id 446B168CF23; Mon, 9 Jun 2025 23:59:44 +0300 (EEST) Received: from btbn.de (btbn.de [144.76.60.213]) by ffbox0-bg.ffmpeg.org (Postfix) with ESMTPS id 1B21268CEC8 for ; Mon, 9 Jun 2025 23:59:37 +0300 (EEST) Received: from [authenticated] by btbn.de (Postfix) with ESMTPSA id 93CD0281911FD for ; Mon, 09 Jun 2025 22:59:36 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rothenpieler.org; s=mail; t=1749502776; 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=Y8ixq8nEAQX9EZwRiJgDiRmrrnaCawsrmk4ofD9Bm/w=; b=YlMioX2QzKxwdka3rH78E7K6bdq7Cy4QLrALn1eq7+8ilPuQiEt4v7KmD+6fpkrBD+Icg2 /ylM761fRPVxOxDZNB7A/AUm8E4EaLpnWGWDYUreFJnnJHN0mftDU5lCzuCV2QLADrhx/H FbzMxT2HNBHox6Su6cTa6asm/gJLke6WBjm1rpjASo3ofVJTc46iSHTf++EtV3eizo4fX0 HjqLTNemE7dsvCVnRleJlu6uqHEFNhzIDcipvraIEcrw5U5AxFM+YgWwohdXwwmWkuZ2Bn cdCEVAcy9yXE8Y4SwLpalf6ob2V13CJCiGEu07bNJQE++LNLjhSfPAgAMlnGUQ== Message-ID: <224b0f55-d991-4098-a12b-ddd4a85b226b@rothenpieler.org> Date: Mon, 9 Jun 2025 22:59:36 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird To: ffmpeg-devel@ffmpeg.org References: <20250607213509.16424-1-timo@rothenpieler.org> <57ffc654-1acf-4bb4-8304-e30646ed427d@gmail.com> Content-Language: en-US From: Timo Rothenpieler In-Reply-To: <57ffc654-1acf-4bb4-8304-e30646ed427d@gmail.com> Subject: Re: [FFmpeg-devel] [PATCH 1/7] avutil: add an API to handle 3D Reference Displays Information 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 08.06.2025 17:45, James Almer wrote: > On 6/8/2025 11:29 AM, Andreas Rheinhardt wrote: >> Timo Rothenpieler: >>> From: James Almer >>> >> I don't like that you add another allocator for this; instead we should >> add a generic allocator for the frame side-data types. > > Wont work for packet side data. And i purposely didn't add yet another > allocator that inserts the result into a frame, like there's in so many > other modules, because eventually the generic one would be introduced. > > You said you wanted to take over my work on the generic allocator, but > not sure if you did anything with it. The core issue was handling more > complex types that didn't just have an extra nb_blocks argument. So, what is the conclusion here? I'd like to push this set if you can come to an agreement. I haven't looked into it much, but implementing av_tdrdi_alloc() in a generic way does seem a bit hacky. And other types might need even more info for the allocation. _______________________________________________ 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".