[gst-devel] Upstream event or bus for RTCP info to video encoder?
Qin Chen
eric.qin.chen at gmail.com
Sun Mar 28 23:14:39 CEST 2010
Hi experts,
I am writing a video streaming application. I used gstrtpbin for RTP/RTCP
packet transmission.
Furthermore, at the sender side, I would like to adapt video encoding
parameters according to RTCP receiver report QoS statistics. The sender
pipeline is shown below. In the pipeline, identity element is used to probe
RTCP packets for QoS statistics.
* .-------. .-------. .-------. .----------. .-------.
* |v4l2 | |x264enc| |h264pay| | rtpbin | |udpsink| RTP
* | src->sink src->sink src->send_rtp send_rtp->sink |
port=5000
* '-------' '-------' '-------' | | '-------'
* | |
* | | .-------.
* | | |udpsink| RTCP
* | send_rtcp->sink |
port=5001
* .-------. .--------. | | '-------'
sync=false
* RTCP |udpsrc | |identity| | |
async=false
* port=5005 | src->sink src->recv_rtcp |
* '-------' '--------' '----------'
*/
My question is, what is the best way to send the QoS statistics obtained
from identity element to x264enc element (directly or indirectly)?
>From the GStreamer manual, it seems that upstream event could be a candidate
since it can be used for application-element interaction. And bus is used
for application-pipeline interaction. So which one is more suitable here and
where can I find similar examples? Thanks in advance.
Regards,
Qin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/gstreamer-devel/attachments/20100328/308f9eb7/attachment.htm>
More information about the gstreamer-devel
mailing list