Reputation: 1
Description: I am trying to create a GStreamer pipeline that takes input from two different RTSP streams and processes them in parallel using separate branches. However, when I attempt to run the pipeline, one of the RTSP sources fails to connect, and the pipeline does not function as expected.
Both the streams work well independently on two different gstreamer pipelines.
Command being used:
gst-launch-1.0 \
rtspsrc location="rtsp://url_1" protocols=tcp ! queue ! rtph265depay ! h265parse ! kvssink stream-name="KVSStream1" storage-size=128 aws-region="ap-south-1" \
rtspsrc location="rtsp://url_2" protocols=tcp ! queue ! rtph265depay ! h265parse ! kvssink stream-name="KVSStream2" storage-size=128 aws-region="ap-south-1"
Expected Behavior: Both RTSP sources should be able to connect successfully, and the pipeline should stream both inputs in parallel without errors.
Observed Behavior: One of the RTSP sources fails to connect, and I receive the following error:
ERROR: from element /GstPipeline:pipeline0/GstRTSPSrc:rtspsrc1: Could not open resource for reading and writing. Additional debug info: gstrtspsrc.c(6842): gst_rtspsrc_retrieve_sdp (): /GstPipeline:pipeline0/GstRTSPSrc:rtspsrc1: Failed to connect. (Generic error) 2025-02-27 13:27:10 [140736842405632] Execution ended after 0:00:19.523974842 Setting pipeline to PAUSED ... Setting pipeline to READY ... Setting pipeline to NULL ... Freeing pipeline ... INFO - Freeing Kinesis Video Stream KVSStream2
Is there a known limitation when handling multiple rtspsrc elements in a single pipeline?
Upvotes: 0
Views: 10