From: Tim Harris <tha@meta.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 2/2] fftools/ffmpeg: add an option for writing pre-muxing stats
Date: Tue, 7 Feb 2023 17:19:48 +0000
Message-ID: <CO1PR15MB4828C26146D195537F806428D5DB9@CO1PR15MB4828.namprd15.prod.outlook.com> (raw)
In-Reply-To: <dc72461e-209a-3b91-a92b-bb19124eb6de@mail.de>
> > Am 07.02.23 um 10:41 schrieb Anton Khirnov:
> > Also, I'm wondering if we shouldn't rename the options to
> > -stats_{mux,enc_pre,enc_post}[_fmt] for consistency.
> > They were added just recently, so it should be fine if done before the
> > release.
> >
> > Opinions?
>
> I'd like that. Can't comment on the code itself, though.
>
-stats_mux_pre (in case we want to report stats post muxing in the future?)
-Tim
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel<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".
next prev parent reply other threads:[~2023-02-07 17:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-07 9:33 [FFmpeg-devel] [PATCH 1/2] fftools/ffmpeg: store output packet timebases in the packet Anton Khirnov
2023-02-07 9:33 ` [FFmpeg-devel] [PATCH 2/2] fftools/ffmpeg: add an option for writing pre-muxing stats Anton Khirnov
2023-02-07 9:41 ` Anton Khirnov
2023-02-07 10:50 ` Thilo Borgmann
2023-02-07 17:19 ` Tim Harris [this message]
2023-02-08 13:53 ` Anton Khirnov
2023-02-08 15:59 ` Devin Heitmueller
2023-02-08 16:10 ` Anton Khirnov
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=CO1PR15MB4828C26146D195537F806428D5DB9@CO1PR15MB4828.namprd15.prod.outlook.com \
--to=tha@meta.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