You can view all the accumulative statistics for a connected input stream in real-time. It is possible to reset the counters by clicking Reset. The statistics may differ between the various stream types.

To View Stream Statistics:

On the Inputs page of Zixi Broadcaster, click the desired input stream for which you want to view statistics for. The stream’s statistics are displayed on the bottom of the screen.

Field	Description
Bitrate (kbps)	Displays the current bitrate of the input stream.
Last Connected	Displays the date and time in which the stream was connected.
Uptime	Displays the amount of time the stream has been active.
Reconnections	Displays the number of reconnection attempts.
RTT (ms)	Displays the Round Trip Time (RTT) from the source (in milliseconds).
Jitter (ms)	Displays the current Jitter, measured in milliseconds.
Congestion	Displays an estimation of the communication's congestion level – '0' means congestion free, '100' means fully congested.
Latency (ms)	Displays the stream latency configured on the source Feeder.
Total Packets	Displays the total number of packets that have been transmitted.
Packet Rate	Displays the current number of packets per second
Merged Packets	Displays number of missing packets recovered using content-based matching (not 2022-7 mode)
Late Packets	Displays the packets thrown away on failover group output, because they were stuck for significantly longer than the search window time (typically performance issues)
Packet Loss %	Displays current percentage of the packets that were dropped on route from the source.
Consecutive Drops	The number of packets that were dropped in a row. When consecutive packets are dropped that could imply burst loss, as opposed to a sustained % of loss that would imply congestion.
Dropped Packets	Displays the total number of packets dropped between the Feeder and the Broadcaster since the beginning of the stream.
Queue Overflows	Displays the number of packets thrown away on failover group entry, because there is no space in the buffer (typically max bitrate too low)
Stream Switches	Displays the number of times a failover group has switched between different streams (not relevant when streams are identical)
SMPTE-2022-7 Mode	Indicates that the streams in a failover group are being merged based on RTP sequences
RTP Drops	Displays the number of missing packets according to RTP sequences
RTP Restarts	Displays the number of time that the RTP stream had a discontinuity, due to a large jump in sequence numbers or in timestamps
Remuxing Resets	Remuxing resets can occur when remuxing to CBR (i.e value of ‘Remux to bitrate’ field is set). In this case, the value is not high enough to remux the video+audio+other PIDs data. A possible solution is to increase value of the ‘Remux to bitrate’ parameter.
Remuxing Overflows	This indicates that the multiplexer internal queues are full.
Smoothing Drops	The Smoothing feature uses a buffer to time packets according to the stream's clock. This is useful when there are bursts in the rate in which the stream arrives. The smoothing drops indicator indicates that the stream is too "bursty".
Recovered Packets	Displays the number of dropped packets that have been recovered since the beginning of the stream.
Not Recovered Packets	Displays the number of non-recovered packets.
FEC Packets	Displays the number of FEC packets transmitted.
FEC Recovered	Displays the number of FEC packets recovered.
ARQ Requests	Displays the number of requests for retransmission of dropped packets made with ARQ.
ARQ Recovered	Displays the number of dropped packets recovered via ARQ.
ARQ Out of Credit	Displays the number of retransmission requests skipped because it hits a limit, which protects from floods of retransmissions when many packets are missing.
ARQ Duplicates	Displays the number of duplicate recovery packets received via ARQ.
Overflows	The number of packets lost due to buffer overflow. Note: Overflow is usually the result of the Max Bitrate being too low.
Consecutive Not Recovered	Displays the maximal number of consecutive "not recovered packets" in the last measurement period (1 second). This measurement this can help identify long streaks of unrecovered packets, which it is not possible to see by just looking at the global "not recovered" counter.

Browser not supported