From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <ffmpeg-devel-bounces@ffmpeg.org>
Received: from ffbox0-bg.mplayerhq.hu (ffbox0-bg.ffmpeg.org [79.124.17.100])
	by master.gitmailbox.com (Postfix) with ESMTP id D8F6343F68
	for <ffmpegdev@gitmailbox.com>; Sat, 20 Aug 2022 12:30:38 +0000 (UTC)
Received: from [127.0.1.1] (localhost [127.0.0.1])
	by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 036E368B972;
	Sat, 20 Aug 2022 15:30:36 +0300 (EEST)
Received: from btbn.de (btbn.de [136.243.74.85])
 by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 4EEA268B82E
 for <ffmpeg-devel@ffmpeg.org>; Sat, 20 Aug 2022 15:30:30 +0300 (EEST)
Received: from [authenticated] by btbn.de (Postfix) with ESMTPSA id
 D17F335AED5; Sat, 20 Aug 2022 14:30:29 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rothenpieler.org;
 s=mail; t=1660998629;
 bh=5hvpks6AjZopW0t1/tJE2C3f5+Ax1/q2Pw9GYxQf9UU=;
 h=Date:Subject:To:References:From:In-Reply-To;
 b=m2aGZSi+ujSZbIR9j+S3VUKYT6mILCaeeFg+GLK5OoW7ZbZBi/g/vfDSS9GlGeC+O
 lierMLC7MTAugtPcdQJ6cW5YqbvkQOIidiDSjO8VCBMZyF8TBReQ+u3aMmZxuVkggT
 SGVROD7e8enAIX3l55xkcDoaInn1nBWbgpWmWBCSdXGDXwVDtRN5Pa0R6npee6mgVh
 SlSK5z3O/9csiM1R/hWqsX4a7oL5Yf+2AXZzkmqnsQdInJqoHvgLAYr2C9Lrcm2PYp
 SwtDuas92IXKtTaT7QxgbGuZD0dum8Qo1+K0Y/8z0/pNv+w25YBc7Zyx0S3tCoMCEL
 9vvRkpmx4FM3w==
Message-ID: <dd0c8f2e-83d4-4632-fd4f-a48aea3f7dd7@rothenpieler.org>
Date: Sat, 20 Aug 2022 14:30:29 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101
 Thunderbird/102.1.2
Content-Language: en-US
To: Brendan Hack <bendy@bendys.com>,
 FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
References: <5a1aa041-e791-17b0-4562-453ae1018b85@bendys.com>
 <847b318a-ae64-aef9-114d-79c1b1e5060b@rothenpieler.org>
 <6d8d57d0-c53a-56fd-41ed-65d924d5394e@bendys.com>
From: Timo Rothenpieler <timo@rothenpieler.org>
In-Reply-To: <6d8d57d0-c53a-56fd-41ed-65d924d5394e@bendys.com>
Subject: Re: [FFmpeg-devel] framepool width and potential patch for bug 9873
X-BeenThere: ffmpeg-devel@ffmpeg.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: FFmpeg development discussions and patches <ffmpeg-devel.ffmpeg.org>
List-Unsubscribe: <https://ffmpeg.org/mailman/options/ffmpeg-devel>,
 <mailto:ffmpeg-devel-request@ffmpeg.org?subject=unsubscribe>
List-Archive: <https://ffmpeg.org/pipermail/ffmpeg-devel>
List-Post: <mailto:ffmpeg-devel@ffmpeg.org>
List-Help: <mailto:ffmpeg-devel-request@ffmpeg.org?subject=help>
List-Subscribe: <https://ffmpeg.org/mailman/listinfo/ffmpeg-devel>,
 <mailto:ffmpeg-devel-request@ffmpeg.org?subject=subscribe>
Reply-To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Errors-To: ffmpeg-devel-bounces@ffmpeg.org
Sender: "ffmpeg-devel" <ffmpeg-devel-bounces@ffmpeg.org>
Archived-At: <https://master.gitmailbox.com/ffmpegdev/dd0c8f2e-83d4-4632-fd4f-a48aea3f7dd7@rothenpieler.org/>
List-Archive: <https://master.gitmailbox.com/ffmpegdev/>
List-Post: <mailto:ffmpegdev@gitmailbox.com>

On 20.08.2022 14:27, Brendan Hack wrote:
> Oh, I think I've got the wrong end of the stick here in regards to what 
> align does in ff_frame_pool_video_init. Frei0r only needs the start of 
> the buffer to be aligned to 16 bytes. It doesn't need each _line_ to be 
> explicitly aligned to 16 bytes since its requirement that the width be a 
> multiple of 8 enforces that (since every 8 pixels is 32 bytes).

Now that sounds like the align should be 8, not 16 or 1, in order for 
frames with odd sizes still work?
_______________________________________________
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".