![]() |
![]() |
![]() |
GStreamer Good Plugins 1.0 Plugins Reference Manual | ![]() |
---|---|---|---|---|
Top | Description | Object Hierarchy | Implemented Interfaces | Properties | Signals |
GObject +----GInitiallyUnowned +----GstObject +----GstElement +----GstBin +----GstRtpBin
"do-lost" gboolean : Read / Write "latency" guint : Read / Write "sdes" GstStructure* : Read / Write "ignore-pt" gboolean : Read / Write "autoremove" gboolean : Read / Write "buffer-mode" RTPJitterBufferMode : Read / Write "ntp-sync" gboolean : Read / Write "use-pipeline-clock" gboolean : Read / Write "rtcp-sync" GstRTCPSync : Read / Write "rtcp-sync-interval" guint : Read / Write "drop-on-latency" gboolean : Read / Write "do-sync-event" gboolean : Read / Write "do-retransmission" gboolean : Read / Write
"clear-pt-map" :Action
"get-internal-session" :Action
"on-bye-ssrc" :Run Last
"on-bye-timeout" :Run Last
"on-new-ssrc" :Run Last
"on-npt-stop" :Run Last
"on-sender-timeout" :Run Last
"on-ssrc-active" :Run Last
"on-ssrc-collision" :Run Last
"on-ssrc-sdes" :Run Last
"on-ssrc-validated" :Run Last
"on-timeout" :Run Last
"request-pt-map" :Run Last
"reset-sync" :Action
"payload-type-change" :Run Last
RTP bin combines the functions of GstRtpSession, GstRtpSsrcDemux, GstRtpJitterBuffer and GstRtpPtDemux in one element. It allows for multiple RTP sessions that will be synchronized together using RTCP SR packets.
GstRtpBin is configured with a number of request pads that define the functionality that is activated, similar to the GstRtpSession element.
To use GstRtpBin as an RTP receiver, request a recv_rtp_sink_%u pad. The session number must be specified in the pad name. Data received on the recv_rtp_sink_%u pad will be processed in the GstRtpSession manager and after being validated forwarded on GstRtpSsrcDemux element. Each RTP stream is demuxed based on the SSRC and send to a GstRtpJitterBuffer. After the packets are released from the jitterbuffer, they will be forwarded to a GstRtpPtDemux element. The GstRtpPtDemux element will demux the packets based on the payload type and will create a unique pad recv_rtp_src_%u_%u_%u on rtpbin with the session number, SSRC and payload type respectively as the pad name.
To also use GstRtpBin as an RTCP receiver, request a recv_rtcp_sink_%u pad. The session number must be specified in the pad name.
If you want the session manager to generate and send RTCP packets, request the send_rtcp_src_%u pad with the session number in the pad name. Packet pushed on this pad contain SR/RR RTCP reports that should be sent to all participants in the session.
To use GstRtpBin as a sender, request a send_rtp_sink_%u pad, which will automatically create a send_rtp_src_%u pad. If the session number is not provided, the pad from the lowest available session will be returned. The session manager will modify the SSRC in the RTP packets to its own SSRC and wil forward the packets on the send_rtp_src_%u pad after updating its internal state.
The session manager needs the clock-rate of the payload types it is handling and will signal the "request-pt-map" signal when it needs such a mapping. One can clear the cached values with the "clear-pt-map" signal.
Access to the internal statistics of rtpbin is provided with the get-internal-session property. This action signal gives access to the RTPSession object which further provides action signals to retrieve the internal source and other sources.