Skip to main content
Not sure yet whether OmniPlayer fits your setup? See OmniPlayer on visualradioassist.live. OmniPlayer MultiPlayer sends now playing data to VRA through an OmniPlayer JSON HTTP POST export.

​
Before you start

  • VRA Core runs for your studio. See Machine specs.
  • The OmniPlayer machine can reach the VRA Core machine on the Core API port, 3002 by default.

​
Add the OmniPlayer connection in VRA Cloud

  1. Go to Settings → Studio → Automations in VRA Cloud.
  2. Click Add Automation and pick Omni Player.
  3. Turn on Enabled. A new connection starts switched off.
  4. Copy the URL under API endpoint. OmniPlayer sends its data to this URL.
  5. Click Add connection.
The host in the URL must be an address the OmniPlayer machine can reach. If it reads 0.0.0.0, replace it with the IP address of the VRA Core machine, for example 192.168.1.20.

​
Set up OmniPlayer to send now playing data

  1. Open the MultiPlayer settings and open Exports.
  2. Add a new OmniPlayer JSON HTTP POST.
  3. Paste the URL from VRA Cloud as URL in the properties window.
  4. Select OmniPlayerBroadcastJSONRPC format.
  5. Click Ok twice.

​
Check that VRA receives OmniPlayer data

Start an item in OmniPlayer, then check two places:
  • Settings → Studio → Automations: the OmniPlayer connection shows a green status dot, the title and artist of the playing item, and the time of the last update.
  • AutomationLink in the main menu: the item shows under On air, and the upcoming items under Next and Rundown.

​
Troubleshoot OmniPlayer

​
The OmniPlayer connection stays idle

VRA Core receives nothing from OmniPlayer. Check, in this order:
  1. Enabled is on in the connection, and AutomationLink Enabled is on at the top of Settings → Studio → Automations.
  2. The URL in OmniPlayer uses the IP address of the VRA Core machine, not 0.0.0.0.
  3. A firewall on the VRA Core machine allows incoming connections on the Core API port, 3002 by default.