1. What is OBS's role?
OBS does not necessarily handle the mobile uplink. In many IRL setups, OBS instead receives a stream that has already been sent to the relay server. Scenes, browser sources, alerts, overlays, and audio can be put together there.
OBS works in three steps. Sources are the layers of a picture, scenes combine them into layouts, and the output sends the finished program to the platform. The sections below follow exactly that order.
2. Useful scenes for an IRL stream
For a mobile stream, OBS should not contain just one scene. A small, clearly named scene structure makes it easier to operate and allows automatic switches when the cellular signal gets weaker.
- LIVE: shows the current picture from the relay server plus the overlays and alerts you want.
- LOW: uses a calmer layout when data is still coming in but the bitrate drops sharply.
- OFFLINE or BRB: shows a prepared graphic or a local video when the mobile stream drops.
- START and END: avoid a hectic transition when you set up or end the stream.
| Scene | When it is active | Content |
|---|---|---|
| LIVE | The stream from the relay arrives normally | Relay picture, overlays, alerts |
| LOW | Data arrives, the bitrate drops sharply | calmer layout |
| OFFLINE / BRB | The mobile stream drops | prepared graphic or local video |
| START / END | when setting up and ending the stream | calm transition |
Programs like NOALBS can switch the LIVE, LOW, and OFFLINE scenes automatically based on the available stream data. Ready-made scenes to import are in the OBS IRL scene pack.
3. Sources, overlays, and browser sources
In the LIVE scene, the received IRL picture is the bottom layer. Above it can sit logos, chat, status information, and alerts. OBS distinguishes media, image, audio, video, and browser sources, among others. Browser sources are often used for alerts and chat overlays.
The order in the source list matters: a source higher up can cover elements below it. Recurring elements can be grouped in a scene of their own and then reused in several main scenes.
For tours and outdoor streams, StreamerHub or RealtimeIRL can also provide a GPS map, speed, route, altitude, or other movement data as a browser source. StreamerHub can also control scenes, sources, and audio through OBS Remote.
4. Keeping audio under control in the IRL workflow
The camera microphone, or the sound from Moblin, should reach OBS only once. If the same audio source is added both globally and inside a scene, you can get echo or doubled output. Alert sounds also must not get back into the stream microphone through OBS and the mobile alert box at the same time.
Before you start, a short test with speech, ambient noise, and a test alert is a good idea. Levels should clearly move but not sit in the red the whole time. If audio and video are out of sync, you can delay the source in question in the advanced audio properties.
How to plan the whole audio path is covered under IRL audio.
5. Output, profiles, and resilience
OBS usually sends the finished program to the target platform over RTMP or RTMPS. Resolution, frame rate, video bitrate, and keyframe interval have to fit the requirements of the platform in question. A hardware encoder can take load off the production computer, as long as it is available for the system you use. How to choose the bitrate is explained under Bitrate & quality.
Profiles store stream, video, and output settings, among other things. Scenes, by contrast, are managed through scene collections. So separate profiles can make sense for tests, the main stream, and a leaner emergency output. You should also test automatic reconnect and a local test recording before a longer outing.
| What | Stores | Meant for |
|---|---|---|
| Profile | Stream, video, and output settings | Test, main stream, leaner emergency output |
| Scene collection | Scenes and how they are built | Managing scenes |
Quick test before the stream
- Relay picture and sound reach the LIVE scene.
- The LOW and OFFLINE scenes can be activated manually or automatically.
- Alerts show up in the right position and are not played twice.
- Output resolution, FPS, and bitrate match the target platform.
- A short private test broadcast runs without picture or sound dropouts.
A general list for on-location use is in the IRL checklist.
6. Typical signal path
Camera → mobile encoder/Moblin → SRT/SRTLA → relay → OBS → RTMP/RTMPS → Twitch, YouTube, or another platform
That keeps the mobile side of the setup lean, while the actual production happens on a stationary system.
7. OBS plugins for the IRL workflow
A plugin should always solve a specific task and be tested on its own before you go live. Aitum remains the starting point for vertical and multistream output. The other tools add automation, audio, captions, individual recordings, and local scene transfer.
8. Official OBS documentation
You can find more detailed feature descriptions in the official OBS overview, the OBS guide to scenes and sources, and the audio mixer documentation.
9. Common questions
Does OBS receive the mobile uplink directly in IRL streams?
Not necessarily. In many setups OBS receives a stream that has already been sent to the relay server. How the relay is set up is covered under SRTLA relay server.
Which scenes do I need at minimum?
To start, LIVE, LOW, and OFFLINE or BRB are enough. START and END make setup and teardown calmer. Give the scenes unambiguous names so that you or a program like NOALBS can switch them reliably.
Why do viewers hear audio twice or with an echo?
Usually the same audio source reaches OBS more than once, for example globally and again inside a scene. Or alert sounds play through OBS and through the mobile alert box at the same time. Add each audio source only once and test with a test alert. More under IRL audio.
What is the difference between a profile and a scene collection?
Profiles store stream, video, and output settings, among other things. You manage scenes through scene collections. Separate profiles are worth it for tests, your main stream, and a leaner emergency output.
What should I test before a longer outing?
Test the relay picture and sound in the LIVE scene, switching to LOW and OFFLINE, alerts, the output settings for the target platform, automatic reconnect, and a local test recording. On location you also check the whole chain, as described under Checking your stream on the go.