Push instructions for the venue
Copy this sheet, fill in the angle brackets from the input’s Ingest panel in the operator UI, delete the sections that do not apply, and send it to whoever runs the venue’s encoder.
Event: <event name> — tech check: <date, time and zone>
Please send your feed to us as below. The address is fixed for the event:
configure it once, and you can test against it any time
<"before the event" / "between <from> and <to>">.
SRT (caller)
Section titled “SRT (caller)”| Setting | Value |
|---|---|
| Mode | caller |
| Host | <relay host> |
| Port | <srt port, e.g. 5001> |
| Stream ID | #!::r=<route>,u=<your user name> |
| Passphrase | <your passphrase> (sent separately) |
| Key length | AES-128 or AES-256 (either; follow your encoder’s default) |
| Latency | <e.g. 500 ms> |
| Container | MPEG-TS |
| Video | <e.g. H.264 or HEVC> |
| Audio | <e.g. AAC> |
If your encoder has no separate Stream ID field, append it to the URL:
srt://<relay host>:<port>?streamid=#!::r=<route>,u=<user>&passphrase=<passphrase>
(some encoders want the #, ! and : written as %23, %21, %3A).
The user name and passphrase are yours alone: please do not share them with another site. If one is ever exposed, tell us and we will replace it without affecting anyone else.
TS over UDP (alternative)
Section titled “TS over UDP (alternative)”| Setting | Value |
|---|---|
| Destination | udp://<relay host>:<your port> |
| Payload | MPEG-TS, 7 × 188-byte packets per datagram (1316 bytes) |
| Source address | <the address you will send from, if we restrict it> |
On the day
Section titled “On the day”- Start sending at least
<n>minutes before air. We can see your feed arrive and will confirm. - If your encoder restarts, it can reconnect at once with the same settings; there is nothing to re-arrange with us.
- If we ask you to stop and reconnect, please do: it frees the route for a clean reconnection.
Our contact on the day: <name, phone, chat>