Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Christian Bartnik <chris10317h5@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: [FFmpeg-devel] [PATCH v5 0/1] Add support for H266/VVC encoding
Date: Wed,  5 Jun 2024 21:51:45 +0200
Message-ID: <20240605195146.11763-1-chris10317h5@gmail.com> (raw)

This patch is based on the latest patchset from Thomas Siedel
(thomas.ff@spin-digital.com).

The libvvenc patch has been changed with following changes:
  avcodec: add external encoder libvvenc for H266/VVC
- sort includes alphabetically
- remove unneeded cast
- do not separate variables declaration and definition
- change if ((ret = func()) != 0) to: ret = func(); if (ret != 0)
- remove check for correct pix_fmt
- remove call of ff_side_data_set_encoder_stats

Christian Bartnik (1):
  avcodec: add external enc libvvenc for H266/VVC

 configure                 |   4 +
 doc/encoders.texi         |  64 +++++
 fftools/ffmpeg_mux_init.c |   2 +-
 libavcodec/Makefile       |   1 +
 libavcodec/allcodecs.c    |   1 +
 libavcodec/libvvenc.c     | 492 ++++++++++++++++++++++++++++++++++++++
 6 files changed, 563 insertions(+), 1 deletion(-)
 create mode 100644 libavcodec/libvvenc.c

-- 
2.34.1

_______________________________________________
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".

             reply	other threads:[~2024-06-05 19:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-05 19:51 Christian Bartnik [this message]
2024-06-05 19:51 ` [FFmpeg-devel] [PATCH v5 1/1] avcodec: add external enc libvvenc for H266/VVC Christian Bartnik
2024-06-12 13:36   ` Nuo Mi
2024-06-15 13:07     ` Nuo Mi

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=20240605195146.11763-1-chris10317h5@gmail.com \
    --to=chris10317h5@gmail.com \
    --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