IP sources Print

  • ip source, srt, rtmp, rtsp, hls, dash, multicast
  • 0

Medusa Panel › Stream › Add Stream

An IP source is any feed the engine pulls or receives over the network. You name it with a URL in the Source Stream field, and the scheme of that URL decides the protocol. Sources are tried in order, so put the preferred one first and backups below it.

Source forms

The engine recognises these Source Stream URL forms:

SourceUseExample
HTTP / HTTPSHLS, DASH or HTTP-TShttps://source.example/live/index.m3u8
UDP / RTPUnicast or multicast transport streamudp://239.10.10.10:5000?localaddr=192.0.2.10
RTSPCamera or contribution sourcertsp://user:password@source.example:554/path
RTMP / RTMPSAn existing RTMP publisherrtmp://source.example/app/name
SRTReliable contribution over an unreliable networksrt://source.example:9000?mode=caller&latency=120000
TCPRaw TCP contributiontcp://source.example:9000
DVBA service discovered by a tuner adapterdvb://server=1&adapter=2&sid=101
Local RTMP publishLet a publisher such as OBS push into the enginertmplocal://a-unique-token-at-least-16-characters
Local fileA file readable by the selected server/data/input.ts
A DVB source is normally added with the dish button rather than typed by hand — see DVB tuners. For a push publisher, set the source to rtmplocal://<token> (16–128 letters, numbers, dots, underscores or hyphens) and have the encoder publish to rtmp://server:port/stream/<token>.

Query parameters

You can append engine options to an HTTP(S) or manifest source as URL query parameters. Start with ?, or & if the URL already has a query. The engine removes the options it recognises before opening the source; any it does not recognise stay on the upstream URL. Names are case-sensitive.

https://source.example/manifest.mpd?token=value&ignore_subtitles=1
  • decryption_key — source decryption keys (a KID:KEY pair, or comma-separated pairs) for an encrypted source manifest.
  • ignore_subtitles — 0 or 1; drop the manifest subtitle tracks.
  • segment_with_manifest_params — 0 or 1; copy the manifest query onto segment requests.
  • segment_with_proxy — 0 or 1; fetch segments through the source proxy as well.
  • http_proxy — a proxy URL for this HTTP source; overrides the Proxies selection.
  • http_persistent — 0 or 1; keep the HTTP connection alive between requests.
  • headers — extra request headers, joined with the literal \r\n, for example headers=Name: value\r\nName2: value.
  • stream_loop — -1 for endless, or a count; loop a finite source such as a file.
  • language — a language tag for a .srt or .ass input.
Several of these have an equivalent form field (HTTP Headers, Proxies). The query form is handy when you keep sources as plain URLs, for example in an import list.

Backup sources

Add more URLs (URL #2, URL #3 …) as backups. If the active source drops, the engine fails over to the next one and back again when it recovers.

Source options (form fields)

  • HTTP User-Agent, HTTP Referer, HTTP Headers — sent when opening an HTTP(S) source that requires them.
  • Proxies — pull the source through a configured source proxy — see Add Proxy.
  • HTTP Local Address — bind outgoing HTTP(S) requests to a local interface; Auto lets the OS choose.
  • Format Flags — advanced FFmpeg input-format flags for awkward sources.
  • Timeshift, Sleep Schedule, Restart Schedule — timing controls for the input.

Once the source is set, transcode it or pass it through — see Codecs and passthrough.

Only ingest sources you are entitled to carry, and keep provider URLs and credentials private — never put them on a public page.

Related


Was this answer helpful?

« Back