On Wed, Feb 8, 2023 at 8:54 AM Anton Khirnov <an...@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.heitmuel...@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-requ...@ffmpeg.org with subject "unsubscribe".
