Live transmission for events: one feed in, every platform out

You publish one stream from the venue: RTMP out of the encoder, the switcher or the software mixer your production already runs, pointed at the ingest endpoint we issue for the event. Where the connection at the venue is thin or lossy, contribute over SRT instead and the transport repairs itself rather than stalling in front of an audience.

That single feed lands at the core site nearest the venue, where it is normalised, transcoded into the ladder and packaged once. Everything downstream comes off that one ingest: the platforms, the playback links, the apps. The production uploads once, no matter how many destinations the event turns out to have.

Uplink at the venue is therefore sized for one contribution feed rather than for the audience: 8.4 Mbps nominal is comfortable on a business connection, and it does not grow when a second platform is added or when the tenth thousand viewer arrives, because the fan-out happens on our footprint rather than on yours.

While the transmission runs it is monitored the way a channel is: bitrate, frame rate and continuity per destination, alarmed to our NOC, with a shared channel to your production team on the day where you want one. A destination whose ingest fails is retried on its own and does not take the rest of the event down with it.

Most events are already committed somewhere before the distribution question is asked: a YouTube channel that has the subscribers, a Facebook page that has the reach, an account a sponsor negotiated into the contract. We push your feed to each of them in parallel, with the stream key you give us per destination, so nobody at the venue runs three encoders and three uplinks to do it.

Destinations are configuration rather than plumbing. One can be added or dropped while the event is running, keys are held per event and not shared between them, and because each push is independent a platform that throttles, refuses or drops the connection is retried by itself without interrupting the others or the link your own audience is watching.

Where the rights are yours the simulcast is yours to decide, and where they are not we would rather build the restriction in than leave it to whoever is standing at the switcher. A territory sold exclusively, or a platform carved out for a sponsor, is recorded in the event configuration per destination before the transmission starts.

Alongside the platforms, the same event is packaged as adaptive HLS / DASH: a manifest you can put behind a ticket page, embed in your own site, mail to a delegate list or hand to a partner broadcaster. It plays in a browser and in any standard player, and it is served from the delivery edge nearest each viewer rather than from the venue.

The ladder is four rungs from 1080p25 down to 360p, all at 25 fps, so a delegate on hotel wifi and one on fibre watch the same event at whatever quality their connection supports instead of watching a buffer. Access is yours to close: token, geography or MultiDRM per event where the transmission is not meant to be public.

And where the event belongs inside a product rather than on a page, it can run in your own branded app on phones, tablets, Samsung Tizen, LG webOS, Android TV and Apple TV, as a live entry beside the rest of the line-up. The apps are a separate product with a page of their own, so judge them there rather than on a claim made here.

WHITE-LABEL APPS Your brand on Tizen, webOS, Android TV, Apple TV, phones and tablets. SEE THE PAGE → HLS / DASH DELIVERY The ladder, the packaging and the manifests your viewers open. SEE THE PAGE → CDN AND EDGES 189 delivery edges, EUR 0.09 per GB, or bring your own CDN. SEE THE PAGE →

Tell us the date, where the feed comes from and which destinations it has to reach. We issue the ingest endpoint and the playback links ahead of the event, and we would rather spend an hour on a rehearsal stream the day before than discover a firewall rule at the moment the doors open.

A recurring transmission, such as a league, a conference season, or a weekly service, is configured once and reused. The second event is a date in a calendar rather than a new build. Pricing follows that: per event where it is one, per month where it is a series, with no setup fee for the destinations you add.

If you would rather see the delivery chain before you trust an event to it, take the free three-day trial on channels already on the headend. It ships encrypted SRT and adaptive HLS / DASH together, which is the quickest way to judge picture, latency and packaging before a date is in the diary.