This is an old revision of the document!


Show the current PlayoutONE title on OnAirScreen

Aiir PlayoutONE can control OnAirScreen natively via Monitor → Metadata outputs (HTTP GET or UDP). The NOW footer line accepts NOW:TEXT.

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 licence:

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):

  • URL: http://<onairscreen-ip>:8010/?cmd=NOW:Artist - Title
  • Method: GET

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.

  • Protocol: UDP (not TCP)
  • IP: OnAirScreen host (or 127.0.0.1)
  • Port: 3310
  • Data: NOW:Artist - Title

No HTTP encoding. Firewall: UDP 3310. OnAirScreen has no TCP command port.

  • Replace IPs after 10s and WARN behave as on the other playout howtos (WARN hides NOW/NEXT).
  • Text File / FTP / Meta Radio XML outputs are the wrong receivers for OnAirScreen.
  • Questions: Contact
  • onairscreen/playoutone-en.1789400953.txt.gz
  • Last modified: 01.10.2026 17:43
  • (external edit)