Streaming to other platforms
During a Vivastream event, Studio can send the same program to YouTube, Twitch, Facebook, the other services of the catalogue, or your own RTMP server. Those destinations are called relays.
What Vivastream never sees
Your relay keys stay in your computer's vault. They are never sent to Vivastream, and the platform does not know where you relay to.
Saving a destination
Settings › Broadcast destinations › Add a destination. Pick a service from the catalogue, or a custom server if you stream to a machine of your own, then paste the key that platform gave you. The key is asked once: it never reappears in clear text, not even to you.
Studio only accepts rtmp or rtmps addresses, with no credentials inside the address — the same rules as a Vivastream event ingest.
Joining a relay to the event
Every destination has a Join the broadcast checkbox. Tick the ones that should receive your next event; the others stay saved and receive nothing. A destination never joins by itself.
One quality for all
The program is encoded once, then sent as is to each destination. Your processor therefore does no more work with three relays than with none.
In exchange, they all receive the same quality, and the lowest ceiling decides: if one platform caps at 6,000 kb/s, the event and the other relays go out at 6,000 kb/s too.
What it costs in upload
Each relay sends as much data as the event itself. The Upload needed line adds up the event and the joined relays: three sends at 6,000 kb/s need about 18.5 Mb/s of real upload, not of advertised bandwidth.
Check that margin before going live. Studio does not watch it during the broadcast.
During the broadcast
The set of relays is fixed at launch, because they share the event's encoders. Adding or removing one means stopping the broadcast. The checkboxes and edit buttons are disabled while you are on air.
When a relay fails
Studio retries three times, then sets that relay aside and tells you — with the reason the platform gave: key refused, address unreachable, format rejected.
The Vivastream event and your local recording are not interrupted. Nothing in a relay can stop a broadcast: each one has its own send, and their fates are independent.
Monitoring names every relay with its state, beside the health of the Vivastream stream. A refused key is corrected in the settings, once the broadcast has ended.