What to have on the desk first
Gather five things before you open a single menu.
- The encoder, powered, with its web interface reachable from a laptop on the same network.
- A clean source: the SDI or HDMI output of your camera or switcher, at the resolution and frame rate you plan to air.
- A wired network port that lets the box make outbound connections to the internet.
- Your channel's RTMP address and its stream key. On a Get Stream Hosting video channel the control panel shows both, ready to paste.
- A second screen, ideally a mobile phone off the venue Wi-Fi, to see what viewers see.
If you have not opened a channel yet, the free plan exists for exactly this stage: the live video streaming plans describe it as the plan for wiring up your encoder and player.
The signal chain, end to end
Each link has one job; knowing which makes faults quick to find.
- Camera or vision mixer produces the picture, with programme sound embedded in SDI/HDMI or fed separately from the audio desk.
- The hardware encoder compresses picture and sound into H.264 and AAC and pushes them over RTMP to your channel's address.
- Our servers take that RTMP feed and package it for the web as HLS, up to 1080p, served over HTTPS.
- The embeddable player on your website, or your HLS link, plays it on phones, tablets, laptops and smart TVs. Paid plans add a Samsung and LG TV app of your own; the app publishing guides cover the store side.
Your settings live in step 2. Everything after it is ours to run.
Network settings for the box
The encoder needs an address, a working DNS server and a clear path out on the RTMP port. AJA's port notes for its HELO Plus put it plainly: RTMP leaves the box on TCP 1935 by default, and a different port can be written into the RTMP URL itself, as in rtmp://host:1935/live.
- Use the Ethernet port, not Wi-Fi.
- Give the box a DHCP reservation or a static address, so you can always find its web interface.
- Set a DNS server it can reach: if the ingest address is a hostname, the box must resolve it.
- Ask whoever runs the venue network to allow outbound TCP to the port in your RTMP address. Some managed networks block outbound ports by default.
- Change the encoder's default admin password, and keep its web interface on the local network. Never forward it to the internet.
Confirm it: from the encoder's own network or diagnostics page, check that it shows an address, a gateway and a DNS server. If the box offers a ping or connection test, run it against the hostname in your RTMP address.
Pasting the RTMP address and stream key
Every encoder asks for the same two values, under slightly different labels: usually a server address or URL, and a stream key or stream name.
- In the encoder's web interface, add a new stream or destination and choose RTMP (some boxes call it custom RTMP).
- Copy the address from your control panel into the server or URL field, including the
rtmp://prefix. - Copy the stream key into the stream name or key field. Paste it; do not retype it, and check there is no trailing space.
- Leave optional username and password fields empty unless your control panel gives you a login for them.
- Save, then start the stream from the encoder.
Guard the stream key as you would a password, since whoever has it can publish to your channel.
Confirm it: the encoder's status should change to streaming or connected, with an outgoing bitrate close to the one you set. Then open your player or HLS link and wait for the picture.
Settings to copy
These values follow Apple's HLS authoring specification, which governs how the stream plays on Apple devices once we package it, and the limits of your plan.
| Setting | Value | Why |
|---|---|---|
| Video codec | H.264 | Classic RTMP lacks HEVC, VP9 and AV1; only the newer enhanced RTMP spec adds them |
| Profile | High, at or below Level 4.1 | Apple prefers High Profile and names Level 4.1 or lower for widest compatibility |
| Keyframe (IDR) interval | 2 seconds: 60 frames at 30 fps, 50 at 25 fps | Apple asks for an IDR every two seconds, and each HLS segment must start on one |
| Frame rate | The source's own rate, never above 60 | Apple's spec rules out rates above 60 fps |
| Resolution | Up to 1080p | The paid video plans carry up to 1080p per channel |
| Total bitrate | Video plus audio under 5 Mbps | The paid plans take 5 Mbps of ingest per channel |
| Rate control | Constant or capped | Keeps peaks under the ingest limit |
| Audio | AAC, stereo, 32 to 160 kbit/s | Apple requires stereo AAC and lists that range for it |
If your box lists the keyframe interval in frames, multiply your frame rate by two. If it offers a separate GOP length and a keyframe interval, set both to the same two seconds.
Getting the programme sound into the stream
The encoder sends whatever audio source its menu selects, so choose that source deliberately. Hardware boxes usually offer the audio embedded in the SDI or HDMI input and an analog line input; Magewell's Ultra Encode, for example, takes eight channels embedded over HDMI or two from a line in, and encodes two-channel AAC.
- Desk feeding the camera or switcher: choose embedded audio and the channel pair that carries the programme mix, normally channels 1 and 2.
- Desk feeding the encoder directly: choose the line input, and leave embedded audio off so camera microphones do not leak in.
- Mono source: send it to both channels, or listeners on headphones hear it in one ear only.
- Set levels at the desk, not by turning up the encoder's gain.
Confirm it: watch the encoder's audio meters move on both channels, then listen on the second screen with headphones, not the speaker.
Checks before you go live
- Run a full test at the venue, on the same network, at the same hour of the day if you can.
- Leave the test running as long as your longest segment and watch the encoder's outgoing bitrate: it should hold steady.
- Play the stream on a mobile phone using its cellular connection, and in a laptop browser. Check picture, sound and lip sync.
- Check the embedded player on your own website page, not only the HLS link.
- Stop and restart the encoder once, so you know the stream comes back on its own.
- Write the encoder's IP address on the run sheet, so anyone on the crew can reach it.
If you keep a software encoder as a backup, the same address and key work there. Keep one encoder per stream key at any moment: stop one before starting the other. Stuck on a setting? Open a ticket in the help centre; paid plans also bring phone and live chat help, 24/7.
When it goes wrong
- Encoder never connects: check DNS on the box, the
rtmp://prefix, the port in the URL, and whether the venue network blocks outbound TCP on it. - Connects, then drops or stutters: usually the upload cannot carry the bitrate. Lower the video bitrate, move to a cable, or ask for a less busy network.
- Picture, no sound: the wrong audio source or channel pair is selected. Recheck embedded against line in.
- Slow start for viewers: check the keyframe interval is two seconds, not longer, since every HLS segment must open on a keyframe.
- Plays on a laptop, not on an older phone: check the H.264 level; Apple names High Profile, Level 4.1 or lower for the widest compatibility.
Where the limits are
The free plan caps the audience at 10 simultaneous viewers; it is for rehearsal and wiring. PRO and Platinum carry up to 1,000 simultaneous viewers, and traffic is not counted. Ingest tops out at 1080p and 5 Mbps per channel, so set a 4K box down to 1080p. Platinum adds a second channel with its own ingest and a CDN in five cities. Your channel is hosted in New York or in Bucharest, depending on availability.
If you need your own media server, with your own transcoding or recording, a whole machine from our dedicated servers in New York is the better home; the range runs up to Xeon machines with on-chip video encoding.