From: Kieran Kunhya <kierank@obe.tv>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 2/2] web: add a news entry for VVC
Date: Fri, 5 Jan 2024 16:27:11 +0000
Message-ID: <CAK+ULv5a5G-PhvDRfrksZUQ7TZpZWXqL-NjezsFX6Du0fE898A@mail.gmail.com> (raw)
In-Reply-To: <20240105104936.10817-2-anton@khirnov.net>
On Fri, 5 Jan 2024 at 10:50, Anton Khirnov <anton@khirnov.net> wrote:
> ---
> src/index | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/src/index b/src/index
> index a2536ff..98cc516 100644
> --- a/src/index
> +++ b/src/index
> @@ -35,6 +35,14 @@
> News
> </h1>
>
> + <h3 id="vvcdec">January 3rd, 2024, native VVC decoder</h3>
> + <p>
> + The <code>libavcodec</code> library now contains a native VVC
> (Versatile Video Coding)
> + decoder, supporting a large subset of the codec's features. Further
> optimizations and
> + support for more features are coming soon. The code was written by Nuo
> Mi, Xu Mu,
> + Frank Plowman, Shaun Loo, and Wu Jianhua.
> + </p>
> +
> <h3 id="iamf">December 18th, 2023, IAMF support</h3>
> <p>
> The <code>libavformat</code> library can now read and write <a href="
> https://aomediacodec.github.io/iamf/">IAMF</a>
> --
> 2.42.0
>
LGTM
_______________________________________________
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:[~2024-01-05 16:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-05 10:49 [FFmpeg-devel] [PATCH 1/2] web: add a news entry for IAMF Anton Khirnov
2024-01-05 10:49 ` [FFmpeg-devel] [PATCH 2/2] web: add a news entry for VVC Anton Khirnov
2024-01-05 16:27 ` Kieran Kunhya [this message]
2024-01-06 1:13 ` Nuo Mi
2024-01-05 12:23 ` [FFmpeg-devel] [PATCH 1/2] web: add a news entry for IAMF James Almer
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=CAK+ULv5a5G-PhvDRfrksZUQ7TZpZWXqL-NjezsFX6Du0fE898A@mail.gmail.com \
--to=kierank@obe.tv \
--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