BELABOX as a mobile hardware encoder
A BELABOX connects camera and audio to several network paths and sends the encoded stream to a compatible destination. This guide puts the complete setup in order. Specific menu names and supported hardware can change with the image and version.
Check before you buy: Camera output, capture hardware, USB power draw, modem support, the codec you want and the destination server have to fit together.
1. The BELABOX principle
Camera or capture device → BELABOX encoder → several cellular/network connections → bonding server or compatible destination → OBS and platform.
| Stage | Job |
|---|---|
| Camera or capture device | sends picture and sound to the BELABOX |
| BELABOX encoder | encodes the stream and spreads it across several network paths |
| Modems and networks | carry the partial streams |
| Bonding server or compatible destination | puts the paths back together |
| OBS and platform | take in the stream and pass it on |
Which encoder platforms are worth considering at all is covered on the Encoders for IRL streaming page.
2. Camera, capture and audio
Start at the input. Picture and sound need to reach the BELABOX clean and the same way every time, before you set up modems and servers.
| Area | What you make sure of |
|---|---|
| Camera | The HDMI output is clean and holds the resolution constant. |
| Capture device | It's been tested with your BELABOX version. |
| Audio | Sound comes in through the camera/HDMI or through a separate, clearly defined input. |
| USB | You keep track of the bandwidth and power draw of all devices together. |
| Cables | They sit firmly, and you have a spare in your bag. |
3. Modems and bonding
Several modems only help if they really use different or complementary networks. Antenna position, cell, provider, plan and thermal load all affect stability. Bonding doesn't make up for too little total bandwidth.
4. Destination server and OBS
Take the server address, port, stream ID and latency values from the documentation of the receiver you use. Before you head out, check that the signal reaches the server and that OBS receives exactly that stream. Prepare a separate BRB or outage scene.
5. Power supply and cooling
Encoder, capture device, modems and camera all put a constant load on the power supply. Pick a power bank by watt-hours and supported output power. Don't block airflow, don't stack devices tightly on top of each other, and plan extra temperature headroom in the sun.
6. Local controls and Remote UI
The local web interface is for checking on things within your own network. For self-hosted remote access, the community project BelaRemoteUI can set up an outgoing tunnel to your own VPS. Setup and security are covered in the BelaRemoteUI guide.
7. Test the whole setup
| Step | Check |
|---|---|
| 1 | Check camera, audio and network one by one first. |
| 2 | Send for at least 30 minutes under realistic load. |
| 3 | Unplug a modem and watch how the stream recovers. |
| 4 | Log temperature and power use. |
| 5 | Pull the signal into OBS and check picture and sound. |
Several cameras in one picture
For the BELABOX, the IRL4YOU BOX is a free add-on for picture-in-picture with up to four cameras. It is a beta.
8. Common questions about BELABOX
What hardware should I check before buying?
Camera output, capture hardware, USB power draw, modem support, codec and destination server have to fit together. Menu names and supported hardware change with the image and version, so read the current documentation first. For an overview of encoders, see Encoders for IRL streaming.
Does another modem always help?
No. A second modem on the same weak network adds little. It only really helps when the modems use different networks. Antenna position, cell, provider, plan and heat all affect stability. And bonding doesn't turn too little bandwidth into enough. Background is on SRTLA & bonding.
What do I enter for the destination?
Server address, port, stream ID and latency values are in your receiver's documentation. Copy them from there. Before you go out, test that the signal reaches the server and that OBS receives exactly that stream.
Do I need the Remote UI?
Not necessarily. The local web interface lets you control the BELABOX on your own network. If you want self-hosted access from afar, the community project BelaRemoteUI can set up an outgoing tunnel to your own VPS. The BelaRemoteUI guide explains setup and security.
How long should I test the setup?
Send for at least 30 minutes under realistic load. Unplug a modem along the way and keep an eye on temperature and power use. For the final polish there's the start checklist, and for problems the troubleshooting guide.
Setup service & consulting
If you'd like support with the setup or with troubleshooting, reach out in the IRL4YOU Discord.