GStreamer：udpsink/udpsrc与tcpserversink/tcpclientsrc使用问题求助

Hey there! I see you've got a working UDP pipeline but are hitting walls with TCP—let's break down what's going wrong and how to fix it.

The Core Problem: UDP vs. TCP Differences #

UDP is a packet-based protocol—each rtpjpegpay output gets sent as a discrete UDP packet, so your client's udpsrc can easily pick out individual RTP frames. But TCP is a byte-stream protocol: all those RTP packets get glued together into a continuous stream of bytes, and your tcpclientsrc has no way to know where one RTP frame ends and the next begins. That's why your pipeline is throwing those "internal data stream" errors—rtpjpegdepay can't parse the messy byte blob it's receiving.

Solution 1: Add Frame Boundary Handling to TCP Streams #

We can fix this by explicitly defining RTP caps and adding a jitter buffer to the client, which can reconstruct RTP frames from the TCP byte stream.

Working Server Pipeline (Raspberry Pi Zero, 192.168.2.1):

gst-launch-1.0 videotestsrc is-live=true ! jpegenc ! rtpjpegpay ! capsfilter caps="application/x-rtp, encoding-name=JPEG, payload=26" ! tcpserversink host=0.0.0.0 port=7001 sync=false

• capsfilter tells GStreamer exactly what RTP format we're sending, so the client knows how to decode it.
• host=0.0.0.0 lets the server listen on all network interfaces (so your PC can connect over the local network).
• sync=false prevents timing issues with live sources.

Working Client Pipeline (PC, 192.168.2.13):

gst-launch-1.0 tcpclientsrc host=192.168.2.1 port=7001 ! capsfilter caps="application/x-rtp, encoding-name=JPEG, payload=26" ! rtpjitterbuffer ! rtpjpegdepay ! jpegdec ! autovideosink sync=false

• rtpjitterbuffer is the key here—it takes the continuous TCP byte stream and splits it back into valid RTP frames by looking at the caps we defined.

Solution 2: Use RTSP (Recommended for Production) #

If you want a more robust setup (with support for pausing, seeking, and better error handling), use GStreamer's RTSP server. RTSP natively handles TCP streaming for RTP, so you don't have to mess with low-level byte stream issues.

First, install the RTSP server package on your Raspberry Pi:

sudo apt-get install gstreamer1.0-rtsp-server

Server Pipeline:

gst-rtsp-launch "( videotestsrc is-live=true ! jpegenc ! rtpjpegpay name=pay0 pt=26 )"

This starts an RTSP server on port 8554 (default) with a stream named /test.

Client Pipeline:

gst-launch-1.0 rtspsrc location=rtsp://192.168.2.1:8554/test ! application/x-rtp, encoding-name=JPEG ! rtpjpegdepay ! jpegdec ! autovideosink

Why Your Previous Attempts Failed #

• When you used tcpserversink host=localhost or 127.0.0.1, the server was only listening on the Pi's loopback interface—your PC couldn't reach it over the network.
• Without caps and a jitter buffer, the client couldn't split the TCP byte stream into valid RTP frames, leading to internal stream errors.

Hope this gets your TCP stream up and running! 😊

内容的提问来源于stack exchange，提问作者David Adams