Third-Party Systems Setup

In this article, you will find the essential information you need for understanding the setup of third-party systems in Rapid.

In this article, you will find the presentation of the configuration details for receiving content from and publishing content to third-party systems.

ENCO DAD

The ENCO DAD broadcast automation software provides a variety of methods to deliver metadata to downstream applications such as Rapid.
In this example of Rapid, consider a radio station with a dashboard that showcases the Playout Source with four distinct inputs (methods) that could drive Rapid with data from ENCO DAD.

Configuring the Playout Source so that Rapid will accept data from ENCO DAD

For the given example of Rapid, in the dialog named Edit Playout Source, there are four Automation Systems (of the Playout Source Type ENCO DAD) that have been added to the Input Mixer.

In the subsections that follow, the settings for each input (ENCO DAD Method) will be illuminated:

• Rapid driven by PADapult via a TCP Connection
• Rapid driven by PADapult via a UDP Connection
• Rapid driven by PADapult with Files
• Rapid driven directly with files by ENCO DAD

Rapid driven by PADapult via a TCP Connection

Rapid dialog: Edit Playout Source
For your station of interest in Rapid, access the dialog named Edit Playout Source and enable your input for “Rapid driven by PADapult via a TCP Connection”.

Rapid dialog: Edit Input
For the chosen input --- “Rapid driven by PADapult via a TCP Connection” --- select the vertical ellipsis to access the dialog named Edit Input.

Select/set the parameters for the TCP Connection

• Enter a list of the Group Names that you want Rapid to treat as type=SONG, in the “Music Group Names” field
• Enter a list of the Group Names that you want Rapid to treat as type=SPOT, in the “Spot Group Names” field
• Transport Type will be Tcp
• Listen IP Address will match that in PADapult
• Port number will match that in PADapult: this will be the port you want to use to push track information to Rapid

PADapult UI
As an example, the corresponding PADapult setup page for the TCP connection specified in the Edit Input dialog in Rapid is given.

Note that the checkbox for the TCP/IP Socket is selected.
IP Address for the TCP connection needs to match the address that was set in the dialog named Edit Input in your Rapid.
Number for the Port needs to match the port that was set in the dialog named Edit Input in your Rapid.
Note that the checkbox for the “Close IP Socket after each Send” option is selected.
Note that the checkbox for XML is selected for the Default Output Format Template for IP Socket.
XML Style needs to be set to RAW.

Rapid driven by PADapult via a UDP Connection

Rapid dialog: Edit Playout Source
For your station of interest in Rapid, access the dialog named Edit Playout Source and enable your input for “Rapid driven by PADapult via a UDP Connection”.

Rapid dialog: Edit Input
For the chosen input --- “Rapid driven by PADapult via a UDP Connection” --- select the vertical ellipsis to access the dialog named Edit Input.

Select/set the parameters for the UDP Connection

• Enter a list of the Group Names that you want Rapid to treat as type=SONG, in the “Music Group Names” field
• Enter a list of the Group Names that you want Rapid to treat as type=SPOT, in the “Spot Group Names” field
• Transport Type will be Udp
• Source IP Address will match that in PADapult
• Port number will match that in PADapult
• Listen IP Address will match that in PADapult

PADapult UI
As an example, the corresponding PADapult setup page for the UDP connection specified in the Edit Input dialog in Rapid is given.

Note that the checkbox for the UDP Datagram is selected.
IP Address for the UDP connection needs to match the address that was set in the dialog named Edit Input in your Rapid.
Number for the Port needs to match the port that was set in the dialog named Edit Input in your Rapid.
Note that the checkbox for XML is selected for the Default Output Format Template for UDP Datagram.
XML Style needs to be set to RAW.

Rapid driven by PADapult with Files

Rapid dialog: Edit Playout Source
For your station of interest in Rapid, access the dialog named Edit Playout Source and enable your input for “Rapid driven by PADapult with Files”.

Rapid dialog: Edit Input
For the chosen input --- “Rapid driven by PADapult with Files” --- select the vertical ellipsis to access the dialog named Edit Input.

Select/set the parameters for the Files Connection

• Enter a list of the Group Names that you want Rapid to treat as type=SONG, in the “Music Group Names” field
• Enter a list of the Group Names that you want Rapid to treat as type=SPOT, in the “Spot Group Names” field
• Transport Type will be File
• Path could be C:\Files_to_Rapid\PADapult_to_Rapid_via_Files.xml
• Polled checkbox will be selected

PADapult UI
As an example, the corresponding PADapult setup page for the Files connection specified in the Edit Input dialog in Rapid is given.

Note that the checkbox for the ftp/file transfer is selected.
Note that the checkbox for the Local file is selected.
As in Rapid, the Directory needs to match C:\Files_to_Rapid and the Filename needs to match PADapult_to_Rapid_via_Files.xml.
Note that the selection for the XML/File Style is RAW.

Rapid driven directly with files by ENCO DAD

Rapid dialog: Edit Playout Source
For your station of interest in Rapid, access the dialog named Edit Playout Source and enable your input for “Rapid driven directly with files by ENCO DAD”.

Rapid dialog: Edit Input
For the chosen input --- “Rapid driven directly with files by ENCO DAD” --- select the vertical ellipsis to access the dialog named Edit Input.

Select/set the parameters for the direct ENCO DAD Method

• Enter a list of the Group Names that you want Rapid to treat as type=SONG, in the “Music Group Names” field
• Enter a list of the Group Names that you want Rapid to treat as type=SPOT, in the “Spot Group Names” field
• Transport Type will be File
• Path could be C:\DAD\ENCO.xml
• Polled checkbox will be selected

PADapult UI
In this use case, it is imperative that PADapult not be running, as it will also look for the file C:\DAD\ENCO.xml.
PADapult deletes the XML file as soon as it reads it, and it may not be read by Rapid before it is deleted.

win-OMT iMediaTouch

In the iMediaTouch On-Air computer, select the Admin 3 configuration option and click the Internet settings.

In the XML file output, create the name of the XML file in a shared directory on the On-Air computer.

When completed, restart the iMediaTouch On-Air computer and the XML file will be created.

In Rapid, select "OMT" as the Playout Source type.

RCS NexGen

RCS NexGen should be configured as per the screenshot.

Using the Export Formats configuration, select:

• “XML” as the Format
• “TCP/IP” as the Output
• “3” for the option named “Export the next events”
• Check the following Types to Export:
  • Songs
  • Spots
  • Promos
• Select the Output Fields as:
  • Artist
  • Title
  • Audio Number
  • Length [hh:mm:ss]
  • Song Category
  • Album Title
  • Time
• Check the “Truncate Milliseconds from Length” option
• Check the “Remove Header” option

NOTE
When configuring Rapid, set the Transport to “TCP” and select the “Listen” option checkbox.

Wide Orbit

Wide Orbit should be configured as per the screenshots below.

Setup an Event Driver with two Events

1. An Event “Start Play” with an export type of XML and configured as per the given screen shot
2. An Event “Stack Change” with an export type of XML

Select the “Event Rule Set Mappings” tab and add a new “event rule set”

Select the Event Driver you’ve just created and choose Mapping Type of “TCP” and assign the TCP Port to a spare port number. If you want to push data to Rapid, select the “Client” option.
If you want Rapid to connect to your Wide Orbit PC, select the “Server” option. Usually this value would be set to “Client”.

NOTE
When configuring Rapid, set the Transport to “TCP”, select the “Listen” option checkbox, and set the port to the same one that’s configured in your Wide Orbit system.

HD Radio Importer

To send PSD data to an HD Radio Importer or Exporter, you need to know the IP address of the Exporter for HD1, and the IP address for the Importer for HD2, 3 and 4. If this is a Generation 4 combined Importer/Exporter, you only need the IP address for the combined unit.

The following IP ports need to be entered to send the data to the correct audio service:

• HD1 = 11000
• HD2 = 10010
• HD3 = 10011
• HD4 = 10012

In a Generation 4 system, the user will need to enable a preset that will automatically start the MSAC client. Those presets all end with a “_AE”. If using an older Generation 2 system (version 4.4.7), if not already installed; a separate MSAC client will need to be installed and Importer configured for MSAC. Please contact your Importer manufacturer for this MSAC client and installation instructions.

FM RDS Encoders

Nautel VS Range

When configuring the Nautel encoder to work with Rapid, select the data source as “ASCII over IP”.

Nautel Encoder

Audio IP Streaming Encoders

Icecast

To send metadata to an Icecast server you need to add an HTTP destination to the Iccecast Output and add the following in the URL field:

http://(YourServer):(YourPort)/admin/metadata?mode=updinfo&mount=/(YourMount)

You will need to replace:

• (YourServer) with the IP address of your streaming server
• (YourPort) with the port of your streaming server
• (YourMount) with the name of the mount on your streaming server that you want to send metadata to.
  

e.g. http://192.168.1.1:80/admin/metadata?mode=updinfo&mount=/waim

From "Authorization Type" select "Basic" and enter the username and password for the mount point. These are the same as you use for streaming.

NOTE
If you want to send metadata to multiple mounts on the streaming server you will need to add multiple HTTP destinations to the Icecast Output on Rapid.

Rocket Broadcaster

The encoder must be setup to receive updates in the "Simple Text" format. To configure that value, select "Broadcast" from the main menu, and then select "Metadata Capture".

Metadata Capture in Rocket Broadcaster

Select the transport protocol you want to use, and check that the "Metadata" section for that protocol is set to "Simple Text".

1. Return to the “Metadata” page: select the metadata filter you have just uploaded from the drop-down list and set both encoding types to "UTF-8" and press Save.
2. Ensure your stream metadata credentials are set in the stream configuration page: these are usually "admin" and the same password as your stream.

Telos IP Hardware Encoders

For details on how to configure the software encoders (X/2 & X/20) please read Telos Zipstream X/2 & X20 Software Encoders.
For all hardware encoders, to add a custom metadata filter to your Zipstream or Prostream, follow this sequence:

Navigate to the configuration webpage on your encoder.

Consider port 9000 for the metadata.

Click on the "Metadata" link.

Then click "manage your metadata filters".

This is where you are able to manage your metadata filters.

Scroll to the bottom of the page and click on “Choose File”. Search for the LUA file that you've downloaded from Rapid and upload that to your Telos encoder.

Once the LUA file has been selected, click on the “Upload filter” button.

You should see the following message if the file was uploaded successfully.

The Rapid metadata filter will now appear in the “manage your metadata filters” page.

Select the Rapid filter, set both encoding types to "UTF-8", and press Save.

You can then add HTTP destinations to send metadata from Rapid. The URL should be the IP address of your encoder, with the port set to 9000.

Telos Zipstream X/2 & X20 Software Encoders

Download the LUA file from the Teleos X/2 Output dialog in Rapid (Rapid_TelosZipstreamX2.lua) and copy the file into the C:\ProgramData\Telos Systems\ZIPStream X2\Filters folder.

Configuring the Zipstream

1. On the main Control Panel Web Page, select the Metadata link in the top menu.

2. In the drop-down list indicating "Add Metadata Source", select the connection type that matches the Destination setting in Rapid. For this example, the selection is "TCP on a specific port".

3. Assign a friendly name (My Metadata), select a local TCP port that your Automation System will connect to (4545 in this example), and select a Metadata filter to use.

4. Select Save.

5. The connection method (TCP, UDP, or Serial) and the Local connection port is completely driven by your Automation System or whatever is sending the metadata. You cannot select TCP here if your system can only send UDP data.

Assigning Metadata to Your Stream

When creating or editing a stream instance, you will see a Metadata source as an option in the configuration.

1. Select the drop-down list and select the Metadata source that was created in the previous step.

2. Select Save.

Add TCP Metadata Source

From the main screen, select Metadata. You will be greeted with a drop-down menu named 'Add Metadata Source'. Select 'TCP on specific port' and you will be presented with the following options:

• Friendly name - Give your metadata source an easily identifiable name such as ‘Jazz Stream Metadata’
• Local port to accept TCP connection - Use the up/down arrows to select the correct port on your computer where the metadata connects from your automation system or other source
• Metadata filter - Select Rapid_TelosZipstreamX2

When you are finished making your selections, select the Save button.

Add UDP Metadata Source

In a similar manner, use the menu to add a UDP metadata source.

When you are finished making your selections, select the Save button.

v490/1