Stream with Moblin and IRL Pro
One-tap deep links from the panel, enter SRT/SRTLA manually, and publish on the go.
Phone encoder kit: IRL streaming from your phone
Short answer: For mobile IRL a phone kit is enough: an iPhone or Android device, the app Moblin (iOS) or IRL Pro (Android), a power bank and at least two independent internet paths for SRTLA bonding – typically mobile data plus Wi-Fi. Create the stream in the panel with SRT / SRTLA ingest, enter URL and stream key in the app via one-tap or manually, and use SRT latency of about 1,000–2,000 ms with a practical ceiling around 2,500 ms.
What the kit has to do
- A phone with stable sustained encoding performance; HEVC helps preserve quality at the same bitrate.
- An app with SRT/SRTLA support: Moblin on iPhone or IRL Pro on Android.
- At least two independent networks so bonding can actually do something.
- Power for several hours of streaming – encoding and the display drain the battery quickly.
- Mounting, audio and heat protection so nothing slips or throttles on the move.
Parts list
- Phone: iPhone (Moblin) or Android (IRL Pro); check that SRT/SRTLA and HEVC are supported.
- A second SIM or eSIM – or a Wi-Fi hotspot – ideally on a different carrier than your main card.
- A high-capacity USB-C PD power bank, plus a charger and a short cable.
- A mount: gimbal, magnetic or tripod holder, plus a safety lanyard.
- Audio: a wireless lavalier mic if you commentate – the phone mic picks up a lot of wind.
- Weather and heat protection: avoid direct sun, as many phones throttle during sustained encoding.
- Optional: a small USB-C hub if you want to attach a camera or audio interface.
Choosing networks for bonding
SRTLA bonds several paths between the app and the relay. On a phone those are typically mobile data and Wi-Fi. Both have to be independently usable, otherwise the bonding adds no real redundancy.
- Two SIMs from different carriers give more redundancy than two plans from the same provider.
- A Wi-Fi network that shares the same upstream as your mobile data is not a real second line.
- A hotspot from a second phone works as an additional interface, but consumes that phone's data allowance too.
More detail: how SRTLA balances paths is covered in the SRTLA bonding guide; getting started with the apps is in Moblin and IRL Pro.
Setup in short
- Create a stream in the panel with SRT / SRTLA ingest.
- Use “Open in Moblin” or “Open in IRL Pro” in the panel – or copy the SRTLA URL and stream key manually.
- Enable bonding in the app and add the interfaces you want, for example mobile data and Wi-Fi.
- Set SRT latency to 1,000–2,000 ms and increase carefully if needed.
- Pick a bitrate that fits the combined uplink capacity; prefer HEVC.
- Start streaming and watch bitrate, packet loss and RTT in the panel.
Latency starting points
| Situation | Sensible starting point |
|---|---|
| Very stable network (Wi-Fi or fixed line) | Start low and test against real RTT and packet loss |
| Good 5G/LTE | A few hundred milliseconds, watch for spikes |
| Mobile IRL with changing coverage | 1,000–2,000 ms |
| Difficult route | Increase gradually, staying below roughly 2,500 ms where possible |
Practical limit, not a protocol limit: around 2,500 ms is an IRL.com.de recommendation to keep the stream feeling genuinely live. Higher values are technically possible when stability matters more than low delay.
Common mistakes
- Only one interface active – SRTLA then behaves like a single connection.
- Wrong protocol in the panel (RTMP instead of SRT) – URL and protocol must match.
- A truncated key or stray spaces when pasting manually.
- Phone in direct sunlight – thermal throttling causes the effective bitrate to collapse.
- Wi-Fi and mobile data sharing the same upstream – then there is no real redundancy.
- RTMP/RTMPS as a fallback: if the app only supports RTMP, create an RTMP stream in the panel – for the road SRTLA is usually the better choice.