From: Devin Heitmueller <devin.heitmueller@ltnglobal.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: Wed, 8 Feb 2023 10:59:43 -0500
Message-ID: <CAHGibzFs8u0iK8vJN0ydWSeXks8DZr1UJpx=+2KOe_YsO=8DrQ@mail.gmail.com> (raw)
In-Reply-To: <167586443457.10789.2692464169788454295@lain.khirnov.net>
On Wed, Feb 8, 2023 at 8:54 AM Anton Khirnov <anton@khirnov.net> wrote:
> Muxers are fundamentally consume-only, I don't see what stats could
> possibly be printed after muxing, even conceptually.
I can offer some examples, in particular because I generate lots of
such statistics after muxing in my private tree.
- Decklink output statistics - late arrival and drop counts for audio
and video packets, pipeline latency (time between submission to the
hardware and the callback indicating frame was played out), FIFO
levels within the module, video frames actually played out in last
second, audio samples played out in last second.
- SRT output - various SRT related statistics (lost packets,
retransmits, connection RTT, etc)
- HLS output - counters for various HTTP recoverable events (HTTP
redirects, resends, etc), packets written
Devin
--
Devin Heitmueller, Senior Software Engineer
LTN Global Communications
o: +1 (301) 363-1001
w: https://ltnglobal.com e: devin.heitmueller@ltnglobal.com
_______________________________________________
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-08 16:00 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
2023-02-08 13:53 ` Anton Khirnov
2023-02-08 15:59 ` Devin Heitmueller [this message]
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='CAHGibzFs8u0iK8vJN0ydWSeXks8DZr1UJpx=+2KOe_YsO=8DrQ@mail.gmail.com' \
--to=devin.heitmueller@ltnglobal.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