This guide explains the key terms you’ll encounter when setting up a live stream on Eventcube. Each plays a role in how your broadcast is delivered and viewed by attendees.
Why live stream terms matter
When running a live event, you need more than just video. You need the right mix of technology to ensure smooth delivery, reliable playback, and compatibility with Eventcube’s ticketed streaming system. Misunderstanding these terms can lead to setup issues, so let’s break them down.
Stream engines
Definition: A stream engine takes the raw feed from your camera or broadcasting software and converts it into a format suitable for online streaming.
Examples: Wowza, DaCast, Mux
Why it matters: Stream engines handle transcoding, stability, and scaling so your audience can watch without buffering. Unlike YouTube Live or Vimeo, they give you branding control and secure ticketed access.
YouTube & Vimeo vs Stream Engines
Short answer: YouTube Live and Vimeo are all-in-one platforms with their own players, rules, and branding. Stream engines (e.g., Wowza, Mux, DaCast) are infrastructure services you use behind your own player and page, giving you more control for white-label, ticket-gated events.
Key differences
Area | YouTube Live / Vimeo | Stream engines (Wowza, Mux, DaCast) |
Branding & player | Platform-branded player (limited customisation; Vimeo offers more than YouTube) | Fully white-label with your chosen player |
Access control | Links can be shared; Vimeo domain-privacy requires paid tiers | Signed URLs/tokens, domain/IP/geo rules |
Ads & outbound links | YouTube may show ads/recommendations; Vimeo is ad-free but platform-centric | No platform ads; you keep viewers on your Eventcube page |
Monetisation | Tied to platform models (subs/ads) | Built to work with external paywalls (Eventcube ticket gating) |
Data ownership | Limited viewer data; analytics live in the platform | Rich analytics via API; you own the data |
Reliability & scale | Huge scale, but limited SLAs/control; policy enforcement can interrupt | Enterprise SLAs, low-latency options |
Latency | Typically 15–30s | Tunable; supports low-latency streaming |
APIs & workflow | Basic embed + limited API | Full ingest/playback APIs; flexible workflows |
Cost model | Free or flat subscription | Usage-based (encoding, storage, egress) |
Compliance risk | Content rules can trigger takedowns | You define policies; fewer interruptions |
When to use which
Use YouTube/Vimeo when discoverability matters, budget is minimal, or you need a quick public stream.
Use a stream engine when you need white-label branding, strict access control, low latency, analytics, or reliable ticket-gated experiences.
What this means for Eventcube
For ticketed events, stream engines integrate more cleanly with Eventcube’s embed/iframe flow and give you stronger access control.
If you must use YouTube/Vimeo: set the video to unlisted/private, disable platform UI where possible, use Vimeo domain-level privacy (paid), and always test embedding before going live.
Live streaming video software
Definition: Software (like OBS Studio, Wirecast, or vMix) that captures your audio/video input and sends it to a stream engine.
Why it matters: This is your production hub. It lets you mix camera feeds, add graphics, and manage your broadcast before handing it to the engine. Think of it as the “studio” where you build the show.
Video embeds
Definition: An embed is a snippet of code that places your live video player inside your Eventcube event page.
Why it matters: Embeds allow your audience to view the stream directly in your Eventcube environment, without being redirected. It keeps attendees in one secure place while you deliver professional streaming.
iFrames
Definition: An iframe is a container of code used to display external content (like a video player) inside your Eventcube event page.
Why it matters: Embeds are usually delivered as iframes. This is why Eventcube asks for an iframe code from your streaming provider—it’s the wrapper that makes the video appear seamlessly inside your event page.
Putting it all together
Broadcast software (OBS, Wirecast, vMix) captures and mixes your video.
Stream engine (Wowza, DaCast, Mux) processes and delivers it at scale.
The engine provides you with a video embed (iframe code).
You paste this iframe into Eventcube so attendees can watch securely on your event page.
FAQs
Can I just use YouTube Live or Vimeo?
You can, but they come with branding restrictions, limited access control, and sometimes ads. Stream engines and embeds give you more control.
Do I need both software and a stream engine?
Yes—software creates the broadcast, the engine distributes it.
What if I only have the embed code?
That works—you can paste the embed (iframe) into Eventcube, as long as the stream engine supports it.
Related articles: