GStreamer Pipeline

Context: $ARGUMENTS

Quick start

• Run a pipeline: -> Step 4 (launch -- <pipeline-desc>)
• Look up an element's properties: -> Step 2 (inspect --element <name>)
• Probe a file or URL: -> Step 3 (discover --uri <uri>)
• List cameras / mics / screens: -> Step 3 (devices)
• Copy-paste a ready-made recipe: -> Read references/pipelines.md

When to use

• User wants a running pipeline: "play this", "transcode", "publish RTSP", "receive WebRTC".
• User wants to verify an element exists locally AND is linkable with a given caps.
• User wants to enumerate cameras/mics with gst-device-monitor-1.0.
• User wants to probe a file's streams/caps/duration via gst-discoverer-1.0.
• User wants a gst-launch-1.0 one-liner for bench-testing before coding the C / Rust / Python client.