From: "Carotti, Elias" <eliascrt@amazon.it>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 2/2] lavc/libx264: add mb_info option
Date: Tue, 11 Jul 2023 10:46:20 +0000
Message-ID: <b5a68fd5de914849994633e24fcc1595@amazon.it> (raw)
In-Reply-To: <168890085522.542.1128745243112426352@lain.khirnov.net>
> From 5bdb624d8dbcff96493a63f02f68a3961cf72723 Mon Sep 17 00:00:00 2001
> From: Elias Carotti <eliascrt@amazon.it>
> Date: Tue, 20 Jun 2023 19:29:08 +0200
> Subject: [PATCH 2/2] lavc/libx264: add mb_info option
>
> Pass the information about unchanged parts of the frame by means of
> the AVVideoHint side data.
> ---
> Changelog | 1 +
> doc/APIchanges | 3 ++
> libavcodec/libx264.c | 94
> ++++++++++++++++++++++++++++++++++++++++++++
> libavcodec/version.h | 2 +-
> 4 files changed, 99 insertions(+), 1 deletion(-)
>
> diff --git a/Changelog b/Changelog
> index 3876082844..70b0fe94a3 100644
> --- a/Changelog
> +++ b/Changelog
> @@ -25,6 +25,7 @@ version <next>:
> - Raw VVC bitstream parser, muxer and demuxer
> - Bitstream filter for editing metadata in VVC streams
> - Bitstream filter for converting VVC from MP4 to Annex B
> +- support for the P_SKIP hinting to speed up libx264 encoding
>
> version 6.0:
> - Radiance HDR image support
> diff --git a/doc/APIchanges b/doc/APIchanges index
> bfe04556d2..89ff88af15 100644
> --- a/doc/APIchanges
> +++ b/doc/APIchanges
> @@ -2,6 +2,9 @@ The last version increases of all libraries were on
> 2023-02-09
>
> API changes, most recent first:
>
> +2023-06-21 - xxxxxxxxxx - lavc 60.23.100 - libx264.c
> + Add mb_info option.
> Do we actually need the option? If the encoder's caller bothered with adding the side data, then I'd think it should always be used, otherwise why is it even there?
I agree, I just thought I had to update that file as well, if that's not the case feel free to remove it.
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-11 10:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-21 15:57 Carotti, Elias
2023-07-03 15:55 ` Carotti, Elias
2023-07-09 11:07 ` Anton Khirnov
2023-07-11 10:46 ` Carotti, Elias [this message]
2023-07-11 22:01 ` Carotti, Elias
2023-08-08 8:11 ` Stefano Sabatini
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=b5a68fd5de914849994633e24fcc1595@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