There are several steps involved in capturing and posting metadata to the various devices and services. As the middleware application CSRDS must capture, filter and cleanse the data then reformat it in a number of different ways as required by the receiving device and actually get it to that device. This requires a reliable communication link to the device, converting to the correct data and a reliable 24×7 communication link to the device or service.
The most common issue is the communication link. We need to capture and send data every few minutes 24×7. As such it is important to work with your network administrator to ensure the the computer running CSRDS has a reliable connection and can access all of the input and output sources. While Arctic Palm support cannot be your network administrator here are some tips to correct common issues.
A TCP/IP connection is a network connection where one PC is the “server” and all other PC’s are the “Client”. As a server that PC opens a port and listens for other computers to request a connection. Once the server accepts the connection both computers can send and receive data. The Client PC will need the IP of the Server PC but the Server does not require an IP as it just listens to the port. Most automation systems, devices and services use TCP/IP and are the server so CSRDS defaults as the client. However, some automation systems are the client. (most RCS systems are the client). If this is the case in CSRDS Select Tools–Properties–Other and set the Input Source is the Client option.
For Automation System connections CSRDS opens and keeps the port and monitors the status. Some network issues may cause the connection to be closed without changing the status so CSRDS is in a constant Waiting for Next Event… state. If this continues to be an issue check your network configurations to ensure nothing is dropping the connection but as a workaround: In CSRDS — Tools–Properties–Other Tab and set the Persistent Connection option. When selected CSRDS will force a reconnection should no data be received for several minutes.
For Output Devices, CSRDS is “port aware”. That is, it opens the port, sends the data and closes the port allowing other applications or other instance of CSRDS to update the same devices and services.
Trouble Shooting IP
When CSRDS makes a TCP connection and gets an error like a timeout or Forcefully Rejected error we know the connection request was blocked. This can be an IP issue where the IP is incorrect or on a different network but more often the error is due to the port. The security settings may block the port. This could be on the CSRDS computer, the computer/device CSRDS is trying to connect to, a router/switch setting or network group policy blocking ports. If blocked contact your network Administrator to open the port. It could also be the selected port is already in use by another application which may be running as a system service. Simply using a different port may resolve the issue. (never use a reserved ports like 80, 21,22,23, etc)
Tip: Ping the IP from the CSRDS computer and if it Pings properly it is a Port issue.
Note: CSRDS uses the Windows O/S API to handle all communications. When CSRDS requests the connection, sends data or closes the port control is passed to the O/S and CSRDS is locked until control is returned. Normally this is too fast to see but if CSRDS goes into a “Not Responding” state for more than a few minutes, it is a network issue as control was never returned to CSRDS.
Like the IP connections, CSRDS calls the Windows O/S for serial connections and control is passed to the O/S and CSRDS is locked until control is returned. CSRDS appears to be hung and in a Not Responding state. This is a serial issue especially with USB to Serial connectors and while you may use Putty or other TelNet applications that work fine, they are not connecting and sending data every few minutes 24×7.
The file method is the most reliable method for capturing metadata. If used, you should create a special directory on the on-air computer specifically for metadata and set the security to the CSRDS users with read only rights. CSRDS does not send data back to the automation system.
The only issues we see with the File Method are security related with the user on the CSRDS computer does not have access or rights to the directory on the on-air PC. Rights are at the user level NOT the PC. Multiple staff may use a single PC and while one users has rights the others do not.
It’s Not Working
Click Here for step by step Trouble Shooting tips
We tune the radio to our station and we do not see any now playing information in the display. Since there are a number of processes in the chain we need to step back and follow the metadata from the beginning through each step and CSRDS has a number of troubleshooting tools to assist. The best place to start is with the Event log. This is the blue event log area on the main controller window that will shows each post every step of the way. Depending on the devices and services we will see entries such as these in the event
Metadata captured from Automation (Se View– Event Viewer — Captured Tab to see what was actually received)
AUG-12 13:43:01 Captured:\\192.168.10.20\CSWRITE\MUSICFROM\PALM_FM.XML Posted:12-AUG-19 13:43:01
(note: If we captured and no processing or posting commands the format is wrong or the category is missing)
Now Playing metadata posted to DTS Connected Radio (See View — Event Viewer — CONRAD Tab to see what was sent and received from DTS)
Aug-12 13:43:02 Posted Current Event to CONRAD:AGE OF AQUARIUS BY FIFTH DIMENSION On KTST
Artist Image Captured from DTS Connected Radio (See View — Event Viewer — CONRAD Tab to see what was sent and received from DTS)
AUG-12 13:43:04 Captured Artwork from Conrad:S:\CSWrite\GraphicFiles\b13919e7f7d765bd34d90a585ef290a9.jpg
Artwork send to HD Radio (See View — Event Viewer — JMSAC Tab to see what was sent and received from the JMSAC application)
AUG-12 13:43:05 File Copied to JMSAC LotID:1064 b13919e7f7d765bd34d90a585ef290a9.jpg
Artwork Staged for HD Radio (See View — Event Viewer — JMSAC Tab to see what was sent and received from the JMSAC application)
AUG-12 13:43:06 Posted Artwork to JMSAC:1064
Now Playing Data sent to Stream (See Templates — Stream Temaplte to see the template and the formatted data sent to the stream)
AUG-12 13:43:08 Sent:localhost:8500 (920ms) MUS:AGE OF AQUARIUS BY FIFTH DIMENSION On KTST
Now Playing sent as Dynamic PS event to RDS Encoder
AUG-12 13:43:08 DPS=AGE OF AQUARIUS BY FIFTH DIMENSION On KTST
PAD and Image Trigger to HD Radio See View — Event Viewer — JMSAC Tab to see what was sent and received from the JMSAC application)
AUG-12 13:43:10 JMSAC=FIFTH DIMENSION/AGE OF AQUARIUS
Now Playing sent to RDS Encoder Radio Text
AUG-12 13:43:10 TEXT=AGE OF AQUARIUS BY FIFTH DIMENSION On KTST
Now Playing and Playlist uploaded to web site (See Templates — Now Playing/Playlist Template to see the template and the formatted data sent to the web)
AUG-12 13:43:11 FTP:AGE OF AQUARIUS BY FIFTH DIMENSION On KTST–> Web Updates –>History Update
Of course you will only see entries from the devices you have selected but if you see the Captured and now playing data being posted we know the data is getting through the system and the issue lies elsewhere.
If CSRDS did capture data but is not sending anything either the Format is incorrect or the categories are missing or incorrect.
Resolution: Select Event Viewer from the View Menu and click the Captured tab. Verify the data is in the right format and complete.
If using a Wide Orbit system and the captured data is coming in bursts the data sets are incomplete Click Here for Details.
The more likely cause will be missing or incorrect categories. Categories are used to filter out unwanted content and events in categories not in the list will be ignored. Select Properties from the Tools Menu, click Input Sources Tab and click the Green Categories command to add missing categories. Save the Settings and put CSRDS back on-line and these songs will now be displayed.
If unsure of the format use the copy to clipboard command and paste the data into an e-mail to firstname.lastname@example.org to confirm the format for the selected system.
A single computer can be used to run multiple instances of CSRDS. The configurations are saved in a configuration file named for the PS as defined in the RDS\RBDS Tab and saved in the root of the windows directory for Example C:\Windows\CSRDSPALM-FM.ini where PAL-FM is the PS.
Resolution: To tell CSRDS which configuration to use we add the PS to the shortcut for that instance. This will be displayed in green box in the bottom left of the properties window. To configure the shortcut, right click on the shortcut, select properties and add the PS to the target line in the shortcut. For Example c:\centerstage\csrds.exe PALM-FM To save the configuration file you may need to run CSRDS as an administrator even if you are logged in as an Administrator and depending on the settings in Windows Vista, 7, 8 and 10 windows may actually save the file in a virtual windows directory in one of the C:\users\username directories. If this is the case, you will need to move the CSRDS*.ini files to the c:\windows directory and delete them from the users directory.
Missing all Songs
This may be a communications, format or category. To find which one, in CSRDS select Event Viewer from the View Menu and click the Captured tab. This will display the raw text from the automation system. If there is nothing in the display (no Captured Events in the Log) there is a problem with the communications and CSRDS is not getting anything to send.
If the data is in the captured tab check the format to ensure the correct Music Format is selected. If not, select the correct system. Check the category to ensure they are all in the categories settings. (see above). We may have taken the defaults of MUS and COM while the metadata has a different setting.
Some Missing Songs
As long as data is captured, the most common cause for missing songs is the category. Most systems send a lot of data we do not want to use and CSRDS uses the category to filter out unwanted material and if a song is received for an undefined category it is ignored.
Resolution: In CSRDS Tools-Properties–Input Sources Tab– Click the Green Categories Tab to open the Categories window and enter the missing Category. Click Continue then save the settings.
Songs Do Not Stay in display
If CSRDS displays a song for a few seconds then the static message is displayed. This is an option usually used by news talk stations to rotate information and is controlled by the “Do Not Send Promos” option.
Resolution 1: To set this option in CSRDS–Tools–Properties–Input Sources Tab– Select the “Do Not Send Promos During Songs” option. Save the Settings and put CSRDS back on-line.
Another issue could be the duration defined in the metadata. When CSRDS captures the event, you will see the duration in the bottom right of the CSRDS window and a countdown in the top of the status line. When this reaches zero and another song has not been received the static or scheduled message will be displayed. CSRDS will add a couple of seconds to the duration to prevent the static message from posting only to get a song a few seconds later. If there is “jock talk” or other delays you can extend that time using the the Music Event Buffer in the “Other tab”. This will keep the song in the display a few seconds longer waiting for the next song. As soon as the next song is received it will replace the existing song regardless of the time left.
Resolution 2: This will not be an issue for systems with a fixed format, but systems with user definable option may have multiple formats for the duration and you will need to modify the format to match the format required for CSRDS. If you do not know the format, e-mail email@example.com with the automation system you are using and we will send you the formats for that system.
Commercials not going to Stream
If CSRDS needs to send commercial events to the stream for substitution you will need to ensure the commercial categories are in the configuration settings and the Send Sponsor option is selected. This is Tool-Properties-Input Sources Tab. Green Categories command to add the commercial categories and Send Sponsor option left middle option list. To block commercial from the RDS, Web, HD or other displays go to each tab and set the Do Not Send Sponsors options, In the top portion of the HD/IP Output DO NOT set the do not send sponsor option. Once set CSRDS will send the COM event to the stream and the static message to everything else.
Not showing on all radios (Dynamic PS)
Older and even some newer RDS receiver do not automatically display Radio Text and require the listener to press an “i” info or “d” display button to see the radio text. This may look like the RDS is not working but it is. Newer receivers show both so Dynamic PS is not required but to ensure all listeners see you metadata in Properties–RDS\RBDS Tab select Use Dynamic PS. You will get a message when you update the configuration so click Yes to activate Dynamic PS
Delays Displaying data
If the now playing information is late or even one event behind we may have an issue with the communications or receiving device. The event log will show when the data was captured as well as when the data was posted. The Posting event is shown after the data was sent so you can check the time of the post to the time it takes to get to the display. The difference is caused by the network communications or the time it takes the device/service to display the data.
Resolution: If it’s the RDS\RBDS display you may need to reboot the encoder, especially if songs are behind. For Web Sites, Streams, or other services you may need to check their logs to see when they go the info and when they posted it. As we increase the processes such as calling services are artwork there will be additional delays. These actions will be in the event log but should only take less than a second to process. If this is longer, check your network to see if there are delays from security or load. If it continues, check with the service to see if they are having issues with their servers.
Logos Not Showing
To post logos to your HD System you will need to assign the logo file to the station (See How To Section) and you will need to run the JMSAC module from your hardware vendor. In CSRDS you will see the a Posted Logo to JMSAC command in the event log and you can check the JMSAC response in the View Menu–Event Viewer–JMSAC Tab. This will show you the commands CSRDS sent to the JMSAC and the JMSAC response. Note: if you see an error on the JMSAC event make sure the JMSAC module is configured and running.
The Event viewer as well as the simulators will display the logo sent to the JMSAC. If these are correct but the logo is not showing, you will need to check the HD configuration to ensure the data service names are correct and that the JMSAC processed the file correctly.
Hint: While logos can be up to 24kb in size, smaller is better as they can be transmitted faster with fewer errors.
Not Showing on Stream
Streaming services have all defined their own method for capturing metadata using different formats as well as different communications protocols. The Sent event n the CSRDS log is the post to the stream and using the Stream Template option from the Templates Menu you can verify the format posted to the stream. The format is defined by a template and we have worked with several streaming companies on their formats and have the template in the installation directory. Others have a number of Arctic Palm stations and use our default RDS.XML template but for other you can create your own template based on their needs.Communications is another issue and you will need to work with the streaming company to establish the link especially if it’s an HTTP, HTTPS or WEB/URL post.