Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Gyan Doshi <ffmpeg@gyani.pro>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] doc/muxers: add ffmetadata
Date: Tue, 12 Mar 2024 16:33:20 +0530
Message-ID: <ee6bc482-1ebb-4dcd-8697-538e7a864771@gyani.pro> (raw)
In-Reply-To: <20240312105517.342536-1-stefasab@gmail.com>



On 2024-03-12 04:25 pm, Stefano Sabatini wrote:
> ---
>   doc/metadata.texi |  1 +
>   doc/muxers.texi   | 16 ++++++++++++++++
>   2 files changed, 17 insertions(+)
>
> diff --git a/doc/metadata.texi b/doc/metadata.texi
> index be91059a98..e081da7735 100644
> --- a/doc/metadata.texi
> +++ b/doc/metadata.texi
> @@ -1,3 +1,4 @@
> +@anchor{metadata}
>   @chapter Metadata
>   @c man begin METADATA
>   
> diff --git a/doc/muxers.texi b/doc/muxers.texi
> index a697e4b153..0aaef2b520 100644
> --- a/doc/muxers.texi
> +++ b/doc/muxers.texi
> @@ -1429,6 +1429,22 @@ Use @command{ffmpeg} to convert the input:
>   ffmpeg -i INPUT -s:v 720x480 -pix_fmt yuv411p -r 29.97 -ac 2 -ar 48000 -y out.dv
>   @end example
>   
> +@section ffmetadata
> +FFmpeg metadata muxer.
> +
> +This muxer writes the streams metadata in the @samp{ffmetadata}
> +format.
> +
> +See @ref{metadata,,the Metadata chapter,ffmpeg-formats} for
> +information about the format.
> +
> +@subsection Example
> +Copy an input file and insert metadata information from an @file{metadata.ffmeta} file in
> +@samp{ffmetadata} format:
> +@example
> +ffmpeg -i INPUT -i metadata.ffmeta -map_metadata 1 -codec copy OUTPUT
> +@end example
> +

The above example is for the demuxer only. Better to include an initial 
step showing export.

Regards,
Gyan

_______________________________________________
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-03-12 11:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-12 10:55 Stefano Sabatini
2024-03-12 11:03 ` Gyan Doshi [this message]
2024-03-12 17:09   ` 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=ee6bc482-1ebb-4dcd-8697-538e7a864771@gyani.pro \
    --to=ffmpeg@gyani.pro \
    --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