Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: James Almer <jamrial@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH 1/2] web: add a news entry for IAMF
Date: Fri, 5 Jan 2024 09:23:14 -0300
Message-ID: <4bca5af7-5523-4488-bef2-3da75def9e53@gmail.com> (raw)
In-Reply-To: <20240105104936.10817-1-anton@khirnov.net>

On 1/5/2024 7:49 AM, Anton Khirnov wrote:
> ---
>   src/index | 7 +++++++
>   1 file changed, 7 insertions(+)
> 
> diff --git a/src/index b/src/index
> index 9a21161..a2536ff 100644
> --- a/src/index
> +++ b/src/index
> @@ -35,6 +35,13 @@
>       News
>     </h1>
>   
> +  <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>
> +  (Immersive Audio) files. The <code>ffmpeg</code> CLI tool can configure IAMF structure with the new
> +  <code>-stream_group</code> option. IAMF support was written by James Almer.
> +  </p>
> +
>     <h3 id="cli_threading">December 12th, 2023, multi-threaded <code>ffmpeg</code> CLI tool</h3>
>     <p>
>     Thanks to a major refactoring of the <code>ffmpeg</code> command-line tool, all the major

LGTM, thanks.
_______________________________________________
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".

      parent reply	other threads:[~2024-01-05 12:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-05 10:49 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
2024-01-06  1:13     ` Nuo Mi
2024-01-05 12:23 ` James Almer [this message]

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=4bca5af7-5523-4488-bef2-3da75def9e53@gmail.com \
    --to=jamrial@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