Skip to content
Castreon
Channels

Live event — from the camera to YouTube and other platforms

Updated 11 Oct 2026

For a live event (a concert, a service, a conference, a match) you need a single broadcast from the venue. Castreon receives it and sends it at the same time to all video platforms and to your own viewers — without the laptop or encoder at the venue having to upload the same stream several times.

camera → OBS / vMix / encoder ──► Castreon ──► YouTube, Facebook, Twitch … (RTMP / RTMPS)
                                          └──► website, apps, Smart TV (HLS, DASH, HTTP-TS)

1. The event channel

  1. Channels → New channel, with a name (for example "Event").
  2. Source: RTMP in (OBS / encoder) — see Broadcasting from OBS, vMix and encoders. On an unstable link (mobile internet, Wi-Fi) use SRT.
  3. Profile:
    • no profile (passthrough) — if the broadcast already arrives in H.264 + AAC at the right bitrate; it uses no CPU;
    • with a profile — if you want several qualities for your own viewers (ABR), or if the broadcast arrives in H.265 / AV1 and the platforms want H.264.

2. The outputs

  • HLS (and, if you like, DASH or LL-HLS) — for your website and apps.
  • one RTMP push for each platform. The address is the platform's server address, followed by / and the stream key from the platform's page. Example:
rtmp://a.rtmp.youtube.com/live2/<stream-key>
rtmps://a.rtmps.youtube.com:443/live2/<stream-key>

The RTMPS variant (with rtmps://) sends encrypted; use it when the platform offers it — some require it. Always copy the address and the key from the platform's page: they differ from one platform to another, and the key may change for each event.

Each destination runs on its own: if one drops or refuses the broadcast, the others carry on, and it reconnects by itself.

A channel without a profile cannot have RTMP push together with LL-HLS (each needs a different picture tag): Castreon then stops the RTMP output and writes why in the log. Use regular HLS or a profile.

3. During the event

On the channel page, under Delivery, each RTMP push shows sending, reconnecting or dropped — you see at a glance whether it reaches every platform. The Broadcast from OBS (RTMP) card shows what Castreon receives from the venue.

Before the event — checklist

  • Test 15–30 minutes before, with the platforms in preview mode.
  • In OBS: CBR, keyframe interval 2 s, AAC 48 kHz — the video platforms require them.
  • The server's upload must carry all outputs at once: each platform receives a full copy of the stream (for example 3 platforms × 6 Mbit/s = 18 Mbit/s, plus your own viewers). Set the line upload in Network and upload.
  • The upload at the venue must be at least 1.5 times the broadcast bitrate.
  • With the "no signal" image, a short drop of the broadcast does not end the stream on the platforms: viewers see your image, and the program comes back by itself.

H.265 and AV1 to platforms

An RTMP output can send H.265 or AV1 (Enhanced RTMP) only if the platform accepts them. When the channel also has HLS / DASH outputs on the same quality, the RTMP output cannot carry H.265 — add an H.264 quality to the profile and select it on the RTMP output (Quality sent). See HEVC and AV1.

Delay

From the camera to the platforms, the delay comes mostly from the platforms (usually 5–30 seconds). Castreon adds only a few seconds. For your own viewers, LL-HLS goes down to 1–3 seconds and WebRTC below one second (Enterprise).

Privacy

Cookies & local storage

Strictly necessary cookies are always active. Analytics and marketing use Google services and only start if you accept them — until then nothing is sent to Google. You can withdraw your consent here at any time.

Strictly necessary

Without them, sign-in, forms and your chosen language don’t work. They don’t require consent (§ 25(2) no. 2 TDDDG).

Always active
Name Purpose Duration Type
castreon-session Keeps your session: sign-in and chosen language 2 hours, renewed on every visit Cookie
XSRF-TOKEN Protects forms against forged requests 2 hours, renewed on every visit Cookie
remember_web_… Only if you tick “Remember me” at sign-in Until you sign out, max. 400 days Cookie
__cf_bm Cloudflare: tells visitors and bots apart, only when traffic is being checked 30 minutes Cookie · Cloudflare
castreon:consent Remembers your cookie choice 12 months Local storage
theme Customer account appearance: light, dark or system Until you change it Local storage

Analytics

Google Analytics 4 (Google Ireland Ltd.): which pages are visited, where visits come from and on which type of device — with pseudonymous identifiers, without storing your IP address. Helps us improve the website.

Name Purpose Duration Type
_ga Google Analytics: recognises the visitor (pseudonymous ID) 13 months Cookie · Google Analytics
_ga_VHWQRPHPEF Google Analytics: keeps the state of the visit 13 months Cookie · Google Analytics

Marketing

Google Ads (Google Ireland Ltd.): measures whether visits from Google ads lead to a trial or a plan, and allows Castreon ads to be shown on other websites (remarketing).

Name Purpose Duration Type
_gcl_au, _gcl_aw Google Ads: links the visit to the ad click (conversions) 90 days Cookie · Google Ads
IDE, test_cookie Google Ads: remarketing and ad measurement, on Google domains (doubleclick.net) Up to 13 months Cookie · Google (third party)