Streams and networking

This group covers MPEG-TS and SRT path diagnostics: live bitrate snapshots, host networking helpers, transport-level TSDuck inspection, input probing, tap captures, and timing probes along the pipeline. These tools are for operators commissioning or troubleshooting ingest and egress — not for changing Marketplace licensing or restarting the whole stack (see Service and processing).

When to use which tool

Symptom	Start here
“Is anything moving on SRT?”	pixop-flow
Firewall, routes, listener ports	pixop-net
PAT/PMT, PID, or TS structure questions	tsduck-transport-info
Input not seen by LIVE / wrong elementary stream	pixop-probe-input
Short capture for support (mind sensitivity)	pixop-tap-input
Latency or timestamp drift along the chain	pixop-timing-probe

A practical first pass after pixop-preflight succeeds:

pixop-net summary
pixop-flow --secs 5
tsduckctl check main
tsduck-transport-info …   # see command page for your scenario

Pair transport tools with tsduckctl when you need to apply PID or latency fixes — this group is mostly observational.

Sensitive output

SRT passphrases, listener URLs with embedded secrets, and raw transport captures can appear in command output or tap files. Do not paste them into public tickets. pixop-support-bundle and pixop-pack-logs attempt redaction but are best-effort.

Platform notes

AWS and KVM guests share the same multicast hand-off (239.0.0.1) between TSDuck and LIVE. Host-only networking (bridges, VFIO) is documented under KVM quickstart; guest tools assume you are logged in as ec2-user on the appliance.

Commands documented here may not exist on older Marketplace AMIs. Confirm with pixop-version.

Command pages

Command	Page
pixop-flow	pixop-flow.md
pixop-net	pixop-net.md
tsduck-transport-info	tsduck-transport-info.md
pixop-probe-input	pixop-probe-input.md
pixop-tap-input	pixop-tap-input.md
pixop-timing-probe	pixop-timing-probe.md

Back to the CLI reference.