From: Marvin Scholz <epirat07@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] doc/metadata.texi: Start documenting keys
Date: Tue, 04 Mar 2025 17:18:20 +0100
Message-ID: <3D0CC9A3-7242-455B-9D6E-71E86C324AA6@gmail.com> (raw)
In-Reply-To: <AS8P250MB0744A3DD69129EAFF4282F9A8FC82@AS8P250MB0744.EURP250.PROD.OUTLOOK.COM>
On 4 Mar 2025, at 12:36, Andreas Rheinhardt wrote:
> Tomas Härdin:
>> +@item ref-frame-config @tab @tab @tab
>> +@item reverb @tab S @tab argo_cvg @tab
>
> The first is libvp9enc-only, the second argo_cvg only. IMO it is better
> to document this at the documentation of the relevant encoder and demuxer.
>
IMHO it is useful to have a centralised list somewhere, to know what 'custom'
metadata to expect from FFmpeg in some cases, without having to check every
possibly relevant components docs.
> - Andreas
>
> _______________________________________________
> 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".
_______________________________________________
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".
prev parent reply other threads:[~2025-03-04 16:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-19 15:42 Tomas Härdin
2025-03-04 11:28 ` Tomas Härdin
2025-03-04 11:36 ` Andreas Rheinhardt
2025-03-04 16:18 ` Marvin Scholz [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=3D0CC9A3-7242-455B-9D6E-71E86C324AA6@gmail.com \
--to=epirat07@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