Aiir PlayoutONE can control OnAirScreen natively via Monitor → Metadata outputs (HTTP GET or UDP). The NOW footer line accepts NOW:TEXT.
ON AIR LED from the mixer: Drive LED1 from Data Controller GPI.
API reference: OnAirScreen API / UDP / HTTP / MQTT
Aiir docs: Metadata outputs in Monitor
| Channel | Target (default) | Example |
|---|---|---|
| UDP | Port 3310 | NOW:Artist - Title |
| HTTP | Port 8010 | http://<oas-ip>:8010/?cmd=NOW:Artist%20-%20Title |
Optionally the same for the second footer line: NEXT:…. Maximum 500 characters. OnAirScreen does not read Billboard text files.
On Windows test with oas_send.exe from the OnAirScreen license:
oas_send.exe --ip 192.168.23.5 "NOW:Artist - Title"
If OnAirScreen runs on the same PC, use 127.0.0.1.
Launcher → Type Manager: enable Billboard on the Song type (and any other types you want on the studio screen). Without Billboard, Monitor has nothing to send. Billboard setup
In Monitor → Station Settings → Metadata outputs add HTTP GET (not POST):
http://<onairscreen-ip>:8010/?cmd=NOW:Artist - Title
Format variables use two percent signs: Artist, Title (same as Audio Engine / text-file / Omnia outputs in the Aiir docs). Confirm names in Monitor’s format help.
A second output can send NEXT:… if your version exposes next-item variables.
Firewall: TCP 8010.
Same Metadata outputs list: TCP and UDP.
127.0.0.1)NOW:Artist - TitleNo HTTP encoding. Firewall: UDP 3310. OnAirScreen has no TCP command port.
mAirList · RadioBOSS · RadioDJ · PlayoutONE · StationPlaylist · ProppFrexx · Myriad Playout · RCS Zetta