In this guide
Do not search everywhere at once
An IRL stream is a chain. The smartphone or encoder sends to the relay, and OBS receives the signal there and passes it on to the platform. Always check the chain from the source to the target.
1. Narrowing down the signal chain
- Does the sender app show an active connection and outgoing bitrate?
- Does the relay or its stats show incoming data?
- Does the outgoing bitrate to OBS rise there too?
- Does OBS receive the right URL, stream ID, or stream name?
- Does OBS send stably to the target platform?
2. Connected, but no picture
| Measuring point | Meaning | Next step |
|---|---|---|
| No incoming bitrate | Sender does not reach the relay | Check address, port, firewall, and stream ID. |
| Bitrate in, but not out | No receiver, or the wrong stream | Compare OBS URL and stream name. |
| OBS receives, platform does not | Problem behind OBS | Check OBS output and platform key. |
3. Stutter, gray frames, and blocks
- Match the bitrate to the upload rate you can hold continuously, not to a single speed test.
- Watch for packet loss, latency swings, and switches between cells.
- Check the keyframe interval and codec compatibility.
- Keep an eye on the temperature of the smartphone, modems, and encoder.
- With SRT/SRTLA, do not set latency and bonding settings to extremes without measuring.
4. Picture is there, audio is missing or doubled
Check levels first in the sender, then at the relay or decoder, and last in OBS. Doubled sources, a Bluetooth speaker plus OBS output, and wrong monitoring are common causes. The full check is in the IRL audio guide.
5. Documenting measurements and logs
Note the time, the networks used, bitrate, packet loss, stream ID, the affected path, and the visible symptom. Screenshots must not contain keys or tokens. Then change only one setting at a time and repeat the same test.
6. Emergency and backup scene
Troubleshooting does not prevent every signal drop. NOALBS or another monitored scene switch can put OBS on a BRB or offline scene in time. Your setup should include: mobile mute, a privacy scene, and a backup source you can reach by hand.
7. Common troubleshooting questions
Where do I start when troubleshooting?
At the start of the chain: does the sender app show an active connection and outgoing bitrate? Then check whether data arrives at the relay, whether it goes on to OBS, and whether OBS sends stably to the platform. That way you find the point where the signal ends.
What does it mean if bitrate reaches the relay but nothing shows up in OBS?
Usually a matching receiver is missing, or the stream is the wrong one. In OBS, compare the URL and the stream ID or stream name with the details in the sender. The order is in section 2. Connected, but no picture.
Why does my stream stutter even though the speed test looked good?
A single speed test only shows one moment. In a livestream, what counts is the upload rate you can hold continuously. Packet loss, latency swings, and cell changes can get in the way too. More under Mobile network & connection quality and Bitrate & quality.
Can I change several settings at once to be faster?
Better not. Change only one setting at a time and repeat the same test. That is the only way to see what really helped. Write down the time, networks, bitrate, and the symptom.
May I share screenshots of logs or settings?
Only if no keys or tokens are visible. Look closely at screenshots before sharing them, including URLs and stream IDs. Tips on protecting credentials are in IRL safety.
Setup service & consulting
If you want help with the setup or with troubleshooting, you can reach out in the IRL4YOU Discord.