Get desktop application:
View/edit binary Protocol Buffers messages
Used in:
required - The SSRC of the audio stream associated with the playout event.
Used in:
required - Synchronization source (stream identifier) to be received.
required - Sender SSRC used for sending RTCP (such as receiver reports).
RTP header extensions used for the received audio stream.
Used in:
required - Synchronization source (stream identifier) for outgoing stream.
RTP header extensions used for the outgoing audio stream.
Used in:
required - Bandwidth estimate (in bps) after the update.
required - Fraction of lost packets since last receiver report computed as floor( 256 * (#lost_packets / #total_packets) ). The possible values range from 0 to 255.
TODO(terelius): Is this really needed? Remove or make optional? required - Total number of packets that the BWE update is based on.
Maps decoder names to payload types.
Used in:
required
required
Maps encoder names to payload types.
Used in:
required
required
Used in:
required - Elapsed wallclock time in us since the start of the log.
required - Indicates the type of this event
optional - but required if type == RTP_EVENT
optional - but required if type == RTCP_EVENT
optional - but required if type == AUDIO_PLAYOUT_EVENT
optional - but required if type == BWE_PACKET_LOSS_EVENT
optional - but required if type == VIDEO_RECEIVER_CONFIG_EVENT
optional - but required if type == VIDEO_SENDER_CONFIG_EVENT
optional - but required if type == AUDIO_RECEIVER_CONFIG_EVENT
optional - but required if type == AUDIO_SENDER_CONFIG_EVENT
The different types of events that can occur, the UNKNOWN_EVENT entry is added in case future EventTypes are added, in that case old code will receive the new events as UNKNOWN_EVENT.
Used in:
This is the main message to dump to a file, it can contain multiple event messages, but it is possible to append multiple EventStreams (each with a single event) to a file. This has the benefit that there's no need to keep all data in memory.
Used in:
,Used in:
required - True if the packet is incoming w.r.t. the user logging the data
required
required - The whole packet including both payload and header.
Maps RTP header extension names to numerical IDs.
Used in:
, , ,required
required
Used in:
required - True if the packet is incoming w.r.t. the user logging the data
required
required - The size of the packet including both payload and header.
required - The RTP header only.
RTX settings for incoming video payloads that may be received. RTX is disabled if there's no config present.
Used in:
required - SSRC to use for the RTX stream.
required - Payload type to use for the RTX stream.
Used in:
required
required
TODO(terelius): Video and audio streams could in principle share SSRC, so identifying a stream based only on SSRC might not work. It might be better to use a combination of SSRC and media type or SSRC and port number, but for now we will rely on SSRC only.
Used in:
required - Synchronization source (stream identifier) to be received.
required - Sender SSRC used for sending RTCP (such as receiver reports).
required - RTCP mode to use.
required - Receiver estimated maximum bandwidth.
Map from video RTP payload type -> RTX config.
RTP header extensions used for the received stream.
List of decoders associated with the stream.
Compound mode is described by RFC 4585 and reduced-size RTCP mode is described by RFC 5506.
Used in:
Used in:
Synchronization source (stream identifier) for outgoing stream. One stream can have several ssrcs for e.g. simulcast. At least one ssrc is required.
RTP header extensions used for the outgoing stream.
List of SSRCs for retransmitted packets.
required if rtx_ssrcs is used - Payload type for retransmitted packets.
required - Encoder associated with the stream.