Relaying RTPS as an encoded stream over TCP

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Relaying RTPS as an encoded stream over TCP

jagdspyder
Hello,

I would like to figure out why this sender pipeline:
gst-launch-1.0 rtspsrc location=rtsp://192.168.1.108:8554/720.264 ! rtph264depay ! h264parse ! avdec_h264 ! x264enc ! tcpserversink port=4444

Would work with this receiver pipeline:
gst-launch-1.0 tcpclientsrc host=localhost port=4444 ! h264parse ! avdec_h264 ! nveglglessink

But this sender pipeline causes the receiver pipeline to be stuck after the PROPELLING phase (I see no data being passed to h264parser in the receiver with GST_DEBUG=4)
gst-launch-1.0 rtspsrc location=rtsp://192.168.1.108:8554/720.264 ! rtph264depay ! tcpserversink port=4444

also this sender pipeline works well:
gst-launch-1.0 videotestsrc horizontal-speed=5 ! x264enc tune="zerolatency" threads=1 ! tcpserversink port=4444

Why must the sender pipeline must encode (as in the working example)?