Keep the YouTube stream key on the YouTube-bound output—not on every field encoder. A clean Callaba workflow receives one verified source, monitors it, then sends a separate RTMPS output to YouTube. The venue or guest publisher uses a Callaba ingest credential; Callaba alone holds the platform credential.
This separation matters when several sources, backup paths or destinations are involved. You can replace a field publisher without resetting YouTube, and you can reset a compromised YouTube key without changing the contribution link.
Before the event
- Enable YouTube live streaming early. YouTube says first-time activation may take up to 24 hours. Do not discover that restriction during the production window.
- Confirm channel permissions. The operator needs access to create or schedule the stream. Only a channel owner or manager can reset a compromised stream key.
- Choose the contribution path. Send OBS, a hardware encoder, SRT or RTMP into Callaba and prove that source before configuring the YouTube output.
- Choose visibility deliberately. YouTube supports public, private and unlisted live streams. Use an unlisted or private rehearsal when the production policy allows it.
- Budget upload twice only when you mean to. A source should normally send one contribution feed to Callaba; Callaba then supplies YouTube and any additional destinations from the server layer.
1. Create or schedule the stream in YouTube
- Open YouTube Studio, select Create, then Go Live to enter Live Control Room.
- For an immediate stream, use the Stream tab. For a scheduled event, use Manage and create or select the scheduled stream.
- Set title, audience, visibility and any event-specific options. Check them again before the live start; reused settings can also reuse the previous stream key and metadata.
- In Stream settings, copy the stream URL and reveal/copy the stream key. Treat the key as a secret.
YouTube describes the key as the stream's password and address. Anyone who can publish with it may be able to place media into that YouTube stream. Do not paste it into a screenshot, chat transcript, public runbook or the configuration of a guest encoder.
2. Prove the source inside Callaba first
Create the incoming SRT or RTMP endpoint in Callaba and connect the source. Before adding YouTube, verify:
- the expected publisher or SRT session is connected;
- input bitrate remains non-zero and plausible;
- picture, motion and audio are correct in preview or Multiview;
- the source survives the planned rehearsal duration;
- a backup source or route is ready when the event requires failover.
This ordering creates a useful fault boundary. If YouTube later shows no preview, the team already knows whether a healthy programme reached Callaba.
3. Create the YouTube output in Callaba
- Open Re-streaming and create one job for the YouTube destination.
- Select the source that has already passed the Callaba preview and bitrate check.
- Use the YouTube Live server URL as the destination and enter the YouTube stream key in the destination credential field.
- Prefer the RTMPS endpoint offered by YouTube. YouTube recommends RTMPS because it protects the connection into and through Google's servers.
- Choose a YouTube-compatible output profile, save the job and start it only when the test window is ready.
Create a separate Restream job for each destination. Do not append several platform keys to one guest publisher profile. Independent jobs let an operator stop, replace or troubleshoot YouTube without disturbing the ingest source or another platform.
4. Use a compatible encoder profile
YouTube's current encoder guidance supports RTMP/RTMPS ingest and lists H.264, H.265 and AV1 video with AAC or MP3 audio, depending on the workflow. For the broadest conventional live-production path, H.264 video and AAC audio remain a practical starting point. YouTube recommends constant bitrate and a two-second keyframe interval, with keyframes not exceeding four seconds.
Choose bitrate from the current YouTube table for the actual resolution, frame rate and codec, then confirm the path has enough sustained headroom. Do not copy a 4K value into a 1080p production or use a speed-test peak as the reliable upload budget. YouTube explicitly recommends testing with audio and movement similar to the real event and monitoring stream-health messages during the broadcast.
For 1080p H.264, the current official table lists different recommended values for 30 and 60 fps. Refer to the live encoder settings, bitrate and resolution guide before every important event rather than preserving a copied table indefinitely.
5. Validate the preview before going public
- Start the Callaba Restream output.
- Wait for the YouTube preview to appear in Live Control Room.
- Confirm picture, audio, aspect ratio and motion—not only a green connection state.
- Review YouTube's stream-health messages and correct bitrate, keyframe or codec warnings at the Callaba output profile.
- Open the watch page on a second device when the visibility policy permits it.
- For a scheduled stream, click Go live in Live Control Room only after the correct preview is present.
YouTube's Normal, Low and Ultra low latency settings describe the audience-side delay between capture and playback. They do not replace the SRT latency or RTMP buffering choices on the contribution side. Tune each boundary for its own job.
6. End cleanly and protect the key
For a scheduled event, end the YouTube stream and then stop the Callaba destination job. Confirm the archive and visibility behave as intended. YouTube notes that streams under 12 hours are automatically archived; still keep an independent Callaba or local recording when the programme is important.
If the YouTube key was exposed, reset it in Live Control Room and update the Callaba Restream destination. According to YouTube's current settings guide, the reset control is in the Stream key section and requires owner or manager permission. A deleted screenshot does not restore secrecy.
Troubleshoot the three boundaries in order
| What you see | Boundary to inspect | Action |
|---|---|---|
| No media in Callaba | Source → Callaba | Fix the ingest URL/key or SRT settings, firewall and source output before touching YouTube. |
| Healthy Callaba source, no YouTube preview | Callaba → YouTube | Check the selected source, Restream job state, YouTube server URL and exact platform key. |
| YouTube reports an invalid key | Destination credential | Copy the key from the correct scheduled/current stream; if reset, replace the old value in Callaba. |
| Preview appears with health warnings | Output media profile | Match YouTube's current bitrate, codec, audio and keyframe guidance. |
| Correct preview, wrong audience access | YouTube event settings | Review visibility, audience, schedule and the selected event before clicking Go live. |
| Field encoder change breaks YouTube | Architecture | Keep the field source on a Callaba ingest identity and keep the YouTube key only on the downstream Restream job. |
