Configure bitrate, RTT, packet loss, dropped frames, and two stream sources with a priority you choose.
The generator itself sends no data. Only the downloaded local OBS file queries the stats address you enter. For that, your stats server has to allow browser access from local files, or CORS.
The optional history only keeps the last twenty seconds inside the open overlay. The more tightly spaced data points glide smoothly to the left between polls, so no extra server requests are made. The scale starts at 1,000 kbit/s and raises its upper limit automatically. No measurements are sent to IRL4YOU.
Pick the format your stats server actually delivers. You enter the URL including port and the publisher or stream ID separately. The two sources can use different formats and servers.
The whole JSON stats output always lives at the same address. The publisher is then looked up in the response.
http://stats.example.net:8080/statsPublisherpublish/handy_1234567You enter the base address and the ID. The overlay then builds the full request address from them automatically.
http://stats.example.net:8080Publisherhandy_1234567Resulting pathhttp://stats.example.net:8080/handy_1234567For nginx-rtmp stats with a stream name and incoming bitrate. RTT, packet loss, and frame drops aren't available here.
http://rtmp.example.net/statStream IDdrohne_1234567Priority only decides which source is shown once both deliver data. It doesn't say which stream is your actual main stream. Source 1 takes priority. If it isn't available, source 2 stays visible.
Drone example: Source 1 is the drone, source 2 is the Moblin main stream that runs all the time. While the drone is sending, it takes priority. Once it's gone, the overlay shows Moblin again.
Backup example: Source 1 can also be your main source and source 2 an alternative stream or a backup. You choose the labels yourself.
Note: example.net is only a placeholder. Use the stats address and ID of your own server.
Packet loss counts lost network packets. Frame drops counts discarded video frames. You can show both values separately or together, and they aren't converted into each other.
Not every stats source delivers both figures. If a value you switched on is missing, only that entry stays empty. The tool doesn't invent measurements.
You can show or hide bitrate, RTT, packet loss, frame drops, and the stream label independently of each other. For the stream label, the overlay shows only your own short name, for example "Moblin", "Drone", "Main source", or "Alternative stream". The technical stats path stays in the generator. With the preview state, you can check green, yellow, and red before downloading. In the finished overlay, the status switches automatically based on the bitrate received. You can also adjust the visible messages separately for each state. So instead of Signal stable, you could show Signal good, Connection running, or another short message. The text only changes the display. The switching is still driven by the bitrate thresholds you set.
Examples: "Signal stable", "Connection running", or "Live". A calm, positive message is enough.
Examples: "Bitrate low", "Connection unsteady", or "Quality reduced". Don't use an unnecessarily dramatic warning.
Examples: "Offline", "No signal", or "Reconnecting". The text should be clear at a glance even on a small smartphone.
Short texts stay more readable on stream. Check each message in the OBS preview and test whether it fits fully in the browser source when the state changes.
The bitrate shows how much video data your stats server is receiving right now. RTT describes the round-trip time of a connection in milliseconds. Both values help you keep an eye on a mobile IRL stream, but neither one alone explains the actual picture quality.
Always judge the overlay together with the OBS stats, the relay log, and a controlled check of the picture.
This tool works locally in your browser. IRL4YOU neither transmits nor stores what you enter. Still, keep credentials out of screenshots and public support messages.