From: "Carotti, Elias" <eliascrt@amazon.it>
To: "ffmpeg-devel@ffmpeg.org" <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] Optimization: support for libx264's mb_info
Date: Fri, 7 Jul 2023 16:27:33 +0000
Message-ID: <b0572c3b96bdd58b57e9385be1a8cb283a2d9283.camel@amazon.it> (raw)
In-Reply-To: <f40ff8f4cd5c8155ca7cffc476b17d4f6096b98d.camel@amazon.it>
On Mon, 2023-07-03 at 15:51 +0000, Carotti, Elias wrote:
> On Sat, 2023-07-01 at 10:33 +0200, Anton Khirnov 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 still nag you, but I just noticed that unlike
> > video_enc_params,
> > you do not store AVVideoRect size in AVVideoHint. This means that
> > no new fields can be added to AVVideoRect without an ABI break.
> > This
> > seems suboptimal, since I do see potential use for per-block
> > information.
> >
>
> Hi Anton,
> I do agree with you.
> Please find the updated (and rebased) patch attached to this email.
>
> Best,
> Elias
>
> P.S. By the way, I would be tempted (I didn't do that here) to
> declare
> the block_size field as
>
> const size_t block_size;
>
> and then when setting it into av_video_hint_alloc(...) cast away the
> const (it has to be assigned only once, upon allocation of the
> struct),
> just to enforce compiler checking against accidental assignments and
> for better clarity that this is a read-only field, in the general
> case.
>
> P.P.S.: I'm sending the second part of the patch for libavcodec as a
> separate email.
Hi Anton, Hi Stefano,
do you think this solves the issue?
Best
Elias
NICE SRL, viale Monte Grappa 3/5, 20124 Milano, Italia, Registro delle Imprese di Milano Monza Brianza Lodi REA n. 2096882, Capitale Sociale: 10.329,14 EUR i.v., Cod. Fisc. e P.IVA 01133050052, Societa con Socio Unico
_______________________________________________
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".
next prev parent reply other threads:[~2023-07-07 16:27 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-19 10:19 Carotti, Elias
2023-05-21 23:17 ` Stefano Sabatini
2023-05-22 9:19 ` Carotti, Elias
2023-05-29 17:56 ` Carotti, Elias
2023-06-04 15:29 ` Stefano Sabatini
2023-06-05 15:32 ` Carotti, Elias
2023-06-11 17:15 ` Stefano Sabatini
2023-06-12 8:23 ` Kieran Kunhya
2023-06-12 17:38 ` Carotti, Elias
2023-06-18 10:04 ` Stefano Sabatini
2023-06-12 17:28 ` Carotti, Elias
2023-06-18 10:18 ` Stefano Sabatini
2023-06-21 15:53 ` Carotti, Elias
2023-06-22 8:44 ` Anton Khirnov
2023-06-22 17:23 ` Carotti, Elias
2023-06-24 11:01 ` Anton Khirnov
2023-06-26 9:50 ` Carotti, Elias
2023-06-28 12:55 ` Anton Khirnov
2023-06-30 17:40 ` Carotti, Elias
2023-07-01 8:33 ` Anton Khirnov
2023-07-03 15:51 ` Carotti, Elias
2023-07-07 16:27 ` Carotti, Elias [this message]
2023-07-09 11:05 ` [FFmpeg-devel] [PATCH] lavu: add AVVideoHint API Anton Khirnov
2023-07-09 13:10 ` Lynne
2023-07-10 8:13 ` Carotti, Elias
2023-07-10 12:51 ` Carotti, Elias
2023-07-17 22:19 ` Stefano Sabatini
2023-07-23 23:27 ` Stefano Sabatini
2023-07-26 10:52 ` Carotti, Elias
2023-07-28 7:44 ` Stefano Sabatini
2023-08-02 5:36 ` Stefano Sabatini
2023-08-08 8:16 ` Stefano Sabatini
2023-07-10 8:09 ` Carotti, Elias
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b0572c3b96bdd58b57e9385be1a8cb283a2d9283.camel@amazon.it \
--to=eliascrt@amazon.it \
--cc=ffmpeg-devel@ffmpeg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git