Studio clock, on-air lights, meters, and now-playing. Shop builds: OnAirScreen · Shop
oas_send
Any of these can drive the NOW / NEXT footer via HTTP GET or UDP (NOW:TEXT). No extra plugin.
Where the automation can read a desk GPI / fader / channel ON and fire HTTP GET or oas_send, LED1 (ON AIR) can follow the mixer. That is not the same as “this PC is the on-air studio”.
A desk dry contact into a Raspberry Pi is often shorter: User Manual (GPIO).
| System | How to |
|---|---|
| mAirList | Mixer GPI / ON AIR LED |
| ProppFrexx ONAIR | Mixer / ON AIR LED |
| Myriad Playout | Mixer / ON AIR LED |
| PlayoutONE | Mixer / ON AIR LED |
RadioBOSS, RadioDJ, StationPlaylist, and RCS Zetta have no documented mixer-tally → HTTP/UDP path that is solid enough for a howto. Use Pi GPIO, or send LED1:ON yourself if you already have a script.
The mixer sends Note or CC straight into OnAirScreen (Settings → GPIO → MIDI). No playout in between. The computer that runs OnAirScreen needs the USB cable.
| Mixer | How to |
|---|---|
| RØDECaster Pro II | Mute button / SMART Pad → ON AIR LED |
Forum threads from users wiring OnAirScreen to playout (LEDs, UDP, scripts):