Re: [FFmpeg-devel] [PATCH] lavu: add AVVideoHint API

2023-08-08 Thread Stefano Sabatini
On date Wednesday 2023-08-02 07:36:43 +0200, Stefano Sabatini wrote: > On date Friday 2023-07-28 09:44:37 +0200, Stefano Sabatini wrote: > > On date Wednesday 2023-07-26 10:52:57 +, Carotti, Elias wrote: [...] > > > Agreed. > > > For clarity I am attaching again the patch with Anton's changes

Re: [FFmpeg-devel] [PATCH] lavu: add AVVideoHint API

2023-08-01 Thread Stefano Sabatini
On date Friday 2023-07-28 09:44:37 +0200, Stefano Sabatini wrote: > On date Wednesday 2023-07-26 10:52:57 +, Carotti, Elias wrote: > > On Mon, 2023-07-24 at 01:27 +0200, Stefano Sabatini wrote: > > > CAUTION: This email originated from outside of the organization. Do > > > not click links or

Re: [FFmpeg-devel] [PATCH] lavu: add AVVideoHint API

2023-07-28 Thread Stefano Sabatini
On date Wednesday 2023-07-26 10:52:57 +, Carotti, Elias wrote: > On Mon, 2023-07-24 at 01:27 +0200, Stefano Sabatini wrote: > > CAUTION: This email originated from outside of the organization. Do > > not click links or open attachments unless you can confirm the sender > > and know the content

Re: [FFmpeg-devel] [PATCH] lavu: add AVVideoHint API

2023-07-26 Thread Carotti, Elias
On Mon, 2023-07-24 at 01:27 +0200, Stefano Sabatini wrote: > CAUTION: This email originated from outside of the organization. Do > not click links or open attachments unless you can confirm the sender > and know the content is safe. > > > > > > sorry to nitpick, but if we have this

Re: [FFmpeg-devel] [PATCH] lavu: add AVVideoHint API

2023-07-23 Thread Stefano Sabatini
On date Tuesday 2023-07-18 00:19:40 +0200, Stefano Sabatini wrote: > On date Monday 2023-07-10 12:51:25 +, Carotti, Elias wrote: > > On Mon, 2023-07-10 at 08:13 +, Carotti, Elias wrote: > > > > > > > > AVVideoHint is a bad name for something like this. > > > Could you borrow some wording

Re: [FFmpeg-devel] [PATCH] lavu: add AVVideoHint API

2023-07-17 Thread Stefano Sabatini
On date Monday 2023-07-10 12:51:25 +, Carotti, Elias wrote: > On Mon, 2023-07-10 at 08:13 +, Carotti, Elias wrote: > > > > > AVVideoHint is a bad name for something like this. > > Could you borrow some wording from graphics and call it > > AVVideoDamagedHint or maybe

Re: [FFmpeg-devel] [PATCH] lavu: add AVVideoHint API

2023-07-10 Thread Carotti, Elias
On Mon, 2023-07-10 at 08:13 +, Carotti, Elias wrote: > > AVVideoHint is a bad name for something like this. > Could you borrow some wording from graphics and call it > AVVideoDamagedHint or maybe AVVideoChangedAreaHint or a combination > of both? > I'd prefer the former, damage is standard

Re: [FFmpeg-devel] [PATCH] lavu: add AVVideoHint API

2023-07-10 Thread Carotti, Elias
-Original Message- From: ffmpeg-devel On Behalf Of Lynne Sent: Sunday, July 9, 2023 3:11 PM To: FFmpeg development discussions and patches Subject: RE: [EXTERNAL][FFmpeg-devel] [PATCH] lavu: add AVVideoHint API CAUTION: This email originated from outside of the organization. Do

Re: [FFmpeg-devel] [PATCH] lavu: add AVVideoHint API

2023-07-10 Thread Carotti, Elias
-Original Message- From: ffmpeg-devel On Behalf Of Anton Khirnov Sent: Sunday, July 9, 2023 1:05 PM To: ffmpeg-devel@ffmpeg.org Subject: [EXTERNAL] [FFmpeg-devel] [PATCH] lavu: add AVVideoHint API CAUTION: This email originated from outside of the organization. Do not click links

Re: [FFmpeg-devel] [PATCH] lavu: add AVVideoHint API

2023-07-09 Thread Lynne
Jul 9, 2023, 13:05 by an...@khirnov.net: > From: Elias Carotti > > Add side data type to provide hint to the video encoders about unchanged > portions of each frame. > > Signed-off-by: Anton Khirnov > --- > I've made couple small changes: > * rebased against current master > * consistently

[FFmpeg-devel] [PATCH] lavu: add AVVideoHint API

2023-07-09 Thread Anton Khirnov
From: Elias Carotti Add side data type to provide hint to the video encoders about unchanged portions of each frame. Signed-off-by: Anton Khirnov --- I've made couple small changes: * rebased against current master * consistently refer to rectangles or AVVideoRect, not blocks * use size_t