Option 1 Backup – Same Streaming Service

Option 1 Uses the new Backup IP settings to send a second copy of the now playing data to a backup streaming computer running the same streaming software and communicating with the same protocol. This a serial process and the Live stream will be updated first followed by the backup stream. Depending on the network, network traffic and communications protocol this may delay the other datacasting services from a few milliseconds to 1-2 seconds. 

To configure CSRDS to send a copy of the metadata to a second computer in CSRDS, select Tools – Properties – HD/IP Output Tab. Enter the IP and Port for the backup stream and click OK to save the configuration settings. 

Sample

When restarted, you will see two “Sent:” entries in the CSRDS Event Log, one for each stream. The timings are incremental and the time shown for the backup stream is the delay between when the first stream and second stream received the data. 

APR-30 10:59:05 Sent:192.168.10.12:31313 (180ms) MUS:MANIC MONDAY by BANGLES On KNAB-FM
APR-30 10:59:06 Sent:192.168.10.19:31313 (73ms) MUS:MANIC MONDAY by BANGLES On KNAB-FM

Option 2 Backup or Alternate Streaming Services 


Option 2 requires running multiple instances of CSRDS where each instance sends the now playing information to a different server. Since each program runs independently, the servers are updated simultaneously with no delays in the RDS or other datacasting services. 

Depending on the automation system, we may need to generate a “file” for each instance of CSRDS to use to link to the now playing information. If you are using an automation system such as iMediaTouch that generates a file for CSRDS this will not be necessary. If the only option is serial or IP, we will use the CSLink module to capture the file from the automation system and create a file that all instances of CSRDS can use.

Configuring a second instance of CSRDS can be done as follows:

  1. In the live instance of CSRDS, select Properties from the Tools Menu
  2. In the General Tab, ensure the Play List History and Send to Multi-Port are NOT checked and if available, the Do Not Send to SM is Checked.
  3. In the Input Sources Tab, if the Music From File option is not selected, set the Serial port to <None>, remove the IP link and use the Browse command to select the file created in CSLink.
  4. In the RDS Encoder Tab, set the Serial Port to <None> and remove the IP link to the encoder.
  5. In the RDS Encoder Tab, change the PS to another name. EG. If the PS is KNAB-FM make it something like KNAB-BK.
    ** Note, anytime after the PS has been changed, you can click the Save command to create the new configuration file. Watch the yellow area at the top of the properties window and you will see the new configuration file name. In the above Example the name would change from CSRDSKNAB-FM.INI to CSRDSKNAB-BK.INI. When creating the shortcut, add the new PS to the target line. (e.g. C:\CenterStage\CSRDS.EXE KNAB-BK)
  6. In the FTP file Output Tab, remove all settings.
  7. In the HD/IP Output Tab, change the Stream settings to the backup or new service and remove any HD Settings.
  8. Click OK and Exit CSRDS.
  9. Create the new shortcut and start both instance of CSRDS.

Create a file with CSLink

Option 3 DAB/Other Output 

For those not doing HD or DAB, Option 3 can be used as a secondary output process sending now playing information via TCP/IP or UDP to another system or service. To use this option, we will need to select DAB as the HD Format and create a DAB.XML file in the format of the data we wish to send.

The first step in this process would be to backup the DAB.XML file and copy or create a DAB.XML file in the necessary format. Details for this process are in the RDS Templates.PDF in the PDF directory or your install set or on the downloads page of our web site at www.arcticpalm.com. 

When used, the now playing information will be a serial send but a little lower in the list. The Live stream is updated first, followed by the Dynamic PS display, then the DAB feed will be sent. 

This option is not recommended as a permanent solution but may be useful for testing or evaluating other systems and services.

External Systems or Services 

In some cases the streaming or other service is on a separate DSL network and requires CSRDS to send the data to a static IP on that network. For sites with a single computer, CSRDS can send directly to that computer. For sites with multiple computers and limited Port Forwarding options, we may need CSLink on that network to forward the CSRDS information to a second computer. 

To do this, we configure CSRDS to send the now playing information to the Static IP network using different ports. On the DSL network, CSLink monitors the ports and forwards the data to the appropriate computer. It may be necessary to run multiple instance of CSLink and like CSRDS, we simply add the CSLink Station name to the Target line in the shortcut.

In this example, CSLink is listening on port 9999 and will forward all information received on this port to 192.168.10.50 on port 31313 using TCP/IP and following the Stream The World authentication.

Did this answer your question?