Live streaming: encoding, bitrate and multistreaming.

Your set sounds good in the booth, but the live stream brings familiar problems: video pixelates when smoke arrives, chat reports brief interruptions and the platform warns of instability. The camera or mixer is almost never at fault; the bottleneck is the encoding chain between programme output and the platform server.

This guide orders quality decisions: encoder, codec, resolution, frame rate, bitrate, keyframe interval, audio codec and multistream distribution to YouTube, Twitch, TikTok Live or Instagram/Meta without multiplying failures.

Hardware versus software encoders: where encoding happens

First decide where compression happens. A dedicated hardware encoder takes HDMI or SDI video and outputs encoded RTMP or SRT without a computer: it starts in seconds, unaffected by updates or other applications. Software encoders use PC CPU or GPU and offer more scene, graphics, audio and automation flexibility.

• Hardware versus software: hardware wins stability and consumption; software wins control and cost when you already own a powerful computer.
• OBS: the reference free option, with scenes, filters, multiple audio tracks and simultaneous outputs.
• vMix: mixer and encoder together, with NDI inputs, keyers, macros and multitrack recording.
• Wirecast: layered production and templates for multiple destinations from one machine.
• ATEM streaming: models with integrated streaming broadcast programme directly from the switcher, without an intermediate PC.
• Hardware encoders: compact appliances configured once to broadcast alone, useful when nobody monitors the computer during the set.

On a modern laptop, GPU encoding distinguishes 1080p60 from being limited to 720p. CPU x264 usually gives better quality per bitrate but consumes cores needed by video software, players and the system. On a stretched machine, closing browser and chat tabs during testing matters as much as the profile.

Encoder, bitrate and keyframes

The encoder decides how much information to discard per frame. Bitrate is the data budget per second: insufficient for movement produces blocks in smoke and lights; too high for the line makes the server reject or degrade the connection. Keyframe interval determines how often a complete reference frame is sent: shorter helps late joiners or packet-loss recovery but consumes unnecessary bitrate.

Practically, raise bitrate before resolution, use two-second keyframes unless the platform says otherwise, and avoid mixing profiles between destinations. CBR (constant bitrate) makes consumption predictable; VBR (variable bitrate) improves average quality but risks saturating domestic upload with peaks.

In multicamera work, encoding should not be the weak link. Programme output arrives the same way, but insufficient CPU headroom drops frames, producing visible stutters precisely at transitions.

Video codecs: H.264, H.265/HEVC and AV1

H.264 remains the common denominator: accepted everywhere, quick to encode and good-looking at reasonable bitrates. H.265/HEVC offers equivalent quality with less bitrate, but inconsistent browser compatibility and greater encoding load. Introducing AV1: better quality per bitrate and a medium-term direction, though today it needs a recent GPU and not every service accepts it live.

The simple rule: H.264 for reaching everybody now; H.265/HEVC when supported by the destination and bandwidth saving matters; AV1 when GPU-accelerated hardware and compatible audience apps permit. A codec half your audience cannot decode quickly loses viewers for no apparent reason.

Resolution, frame rate and bitrate

Resolution and frame rate determine pixels compressed per second. 1080p50 or 1080p60 double 1080p25’s information, while 4K quadruples encoder work. Constantly moving lights and smoke benefit from 50 or 60 fps, requiring proportionately increased bitrate.

A reasonable H.264 starting point is 6–9 Mbps at 1080p50, 3.5–5 Mbps at 720p50 and no less than 20 Mbps at 4K. If upload cannot sustain it, lower resolution or frame rate instead of starving bitrate: stable 720p looks better than artifact-filled 1080p, and chat forgives softness before a failing stream.

CBR/VBR, keyframe interval and stability

Configure bitrate mode and keyframes together. CBR maintains a constant predictable ceiling, avoiding upload saturation with flashes, rapid transitions or full-intensity LED walls. VBR allocates data better in quiet scenes but needs real line headroom; a connection at its limit has none.

Use CBR with a target and nearby maximum, two-second keyframes and H.264 High profile. Audio is separate: 128–160 kbps suffices for stereo music; do not reduce it to save bandwidth when video is already at its limit.

Audio codec, latency and synchronisation

AAC-LC at 44.1 or 48 kHz is the usual live audio codec. For music, avoid below 128 kbps and voice-oriented codecs, which destroy bass and muddy cymbals. When combining mixer audio and camera video, measure lip offset: a few milliseconds show up sooner on a cymbal than conversation.

Total latency combines capture, encoding, network, CDN and viewer buffering. YouTube and Twitch commonly accumulate 5–20 seconds; platform low-latency mode reduces this at the cost of more interruptions on weak networks. TikTok Live has similar figures; Instagram/Meta depends on format and viewing device.

ABR and CDN: reaching the audience

Automatic player quality changes come from ABR (adaptive bitrate): the player selects among platform-prepared qualities according to available bandwidth. You send one stream; the CDN replicates it to thousands. No CDN fixes failing source upload: it distributes what it receives.

Separate the problems: encoding quality is measured at ingestion; audience interruptions by network packet loss and jitter. If your own player looks good but a viewer’s mobile looks poor, distribution rather than your configured bitrate is the problem.

Platforms and multistreaming: YouTube, Twitch, TikTok Live and Instagram/Meta

YouTube accepts up to 1080p60 with RTMP or SRT ingestion and allows keyframe adjustment; live help specifies limits and recommendations. Twitch favours high bitrate—up to 6000 kbps for most accounts—and penalises interruptions: prioritise stability over resolution. TikTok Live works best vertically with moderate bitrate. Where applicable on Instagram/Meta, use a professional profile and check formats and durations before treating it as your main destination.

Multistreaming sends the same signal to several destinations, each consuming bandwidth and CPU. Per-platform re-encoding multiplies load; send one master to a redistribution service for copies, or accept identical profiles when target bitrates agree. Before a third destination, test a full private broadcast with the final configuration.

Next step

Encoding, codec, bitrate and destinations are arranged; the network must sustain them for hours. Internet and live redundancy: bonding and failover explains combining connections, when bonding helps and handling primary-link failure mid-set.

If you are still building the audio and latency chain, revisit Broadcast your DJ set live: audio, encoder and latency. As production grows, Operating a DJ broadcast: platforms, copyright, ISO recording and backup covers the work surrounding the stream.