ProppFrexx ONAIR can control OnAirScreen natively via an OnTrackPlay command (HTTP GET). The NOW footer line accepts NOW:TEXT.
ON AIR LED from the mixer: Drive LED1 from a ProppFrexx fader / channel ON.
API reference: OnAirScreen API / UDP / HTTP / MQTT
Forum example: EXEC_SEND_HTTP_GET
| 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.
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.
General settings → Events/Commands. Assign to the global Playlist.OnTrackPlay event:
EXEC_SEND_HTTP_GET http://<onairscreen-ip>:8010/?cmd=NOW:${artist} - ${title}
Placeholders (User Manual appendix / overlay docs): ${artist}, ${title}, or ${trackname} for a combined “artist – title” string.
ProppFrexx must URL-encode the query (spaces, &, non-ASCII). If titles arrive truncated or cut at &, use the encoded variants from the appendix (often a _enc / URL-encoded form of the same names).
Firewall: TCP 8010.
A second command can send NEXT:… if your version exposes next-item tokens (overlay docs list next-track fields such as type/duration; confirm the artist/title next names in your build).
EXEC_SEND_HTTP_POST — OnAirScreen commands are GET only; do not POST XML/JSON to port 8010.EXEC_SEND_TCP — OnAirScreen has no TCP command port. Prefer HTTP GET, or UDP if a send-UDP command exists in your appendix.Gate the command on track type (music vs. jingle/spot) in the event/script so beds do not overwrite the footer.
EXEC_UPLOAD_FILE cannot feed OnAirScreen.mAirList · RadioBOSS · RadioDJ · PlayoutONE · StationPlaylist · ProppFrexx · Myriad Playout · RCS Zetta