Futuri Mobile integrates with several automation systems, including Audiovault v9.20 and higher. This series of articles is generally geared toward your station's IT/engineering staff, but it's a good idea for program directors to be familiar with this information at a higher level, too.
There are two basic pieces to integrating Audiovault with Futuri:
- Now Playing information - Song elements and some song cart "commands" will be configured to export from Audiovault to Futuri.
- Music Logs- Echo will also be configured to watch the folder where your station's music logs are saved. These music logs are used for two primary purposes:
- Seong Alerts - Users can sign up to receive alerts when their requests are about to play on your station. Futuri's system compares what your station is playing now with what's scheduled in the near future, so that we can send these alerts ahead of when the request actually plays (so there's time for the user to turn on the radio).
Insallation
To work through this installation process for the first time, please contact Futuri VIP Support. A remote session with one of our Support Agents should take about 30-60 minutes per station.
This process includes the following steps:
- Now Playing Setup
- Echo Setup
- Configuring Your Music Scheduler to Export Logs to Echo's Import Folder
- Testing
Now Playing Setup
Now Playing data from Audiovault to Futuri's Echo software is handled through TRE. These instructions assume that your station already uses TRE for other Now Playing exports (such as RDS or your stream), but if you don't already have TRE, Futuri VIP Support can help you to obtain a license for it (and initial TRE installation instructions) from BE.
To pass data from TRE to Echo, you will need either the Listener Driven Radio or XML Primary output enabled from TRE. If you do not already have this output enabled (or if your existing XML outputs are already in use), Futuri VIP Support can help you to put in a purchase order with BE for the Listener Driven Radio output, which is available at a discounted rate from the normal XML output. Once BE licenses the output, they will send back a new tre.bin file and you can replace the existing tre.bin with the new one, and then restart TRE.
To enable the Listener Driven Radio (or XML) output, open TRECfg.exe and navigate to that output's tab. Check the Enable box, and enter a folder path in the Path box. This could be something like C:\np, or you could put it in the station's Echo folder (likely C:\Echo), especially if Echo is the only utility that's going to use this file. Finally, type a filename into the File box. It doesn't matter what the filename is, as long as its extension is .xml
You'll also want to navigate to the Event Mapping tab and enter "LDR" under the Music list of categories. You'll create the LDR category in Audiovault further down in these instructions.
You may need to save TRECfg.exe and then re-start TRE to implement these changes.
Echo Setup
Futuri's Echo software bridges Audiovault and Futuri's web servers, allowing listeners to interact with the station programming via the station website and/or mobile apps.
You can submit your station information here, and our VIP Support Team will pre-configure your Echo application for you.
To install Echo (typically on the same PC as Audiovault), create the folder C:\Echo\XXXX (where XXXX is the station’s call letters) and extract the contents of the downloaded Echo.zip (link above) to the same folder.
In the newly extracted folder, place the station.xml file from Futuri VIP Support. It must be saved in the same folder as Echo.exe.
When finished configuring, save station.xml and repeat steps as needed for other stations. Each station will need its own copy of Echo.
Note: Microsoft .NET 4.0 or higher is required for Echo. If you're running Windows 7 or higher, you should be all set, but If needed, you can download .NET 4.0 by clicking here and following the instructions. When .NET 4.0 is confirmed to be installed, run Echo.exe and navigate to File > Boot on Startup so that Echo will start up with the PC.
Configuring Your Music Scheduler to Export Logs to Echo's Import Folder
Note: If you configured Echo's value to be TRUE, this step is not necessary.
In order for Song Alerts to work properly, we will need a copy of your station's music logs.
In order to make this work, your music scheduler should be configured to export logs to Echo's new "input" folder. To do this, open your music scheduler to its log export settings and add /input to the export path (i.e. M:\WXYZ\Music\input).
Next, in the original export folder (i.e. M:\WXYZ\Music) add folders called "input" and "backup".
Because Echo is configured to export its parsed copy of the log to the original export folder (i.e. M:\WXYZ\Music), it is not necessary to change the log import settings for Audiovault (since it will continue to pull logs from the same place it always has).
Note: Make sure the log export from your music scheduler is using the correct format (should have > signs down the left side (for all audio), and should have X's down the right side). If your log doesn't look like that, you will need to get in touch with BE Support and your music scheduler support to re-configure your exports to use that layout.
Testing
Once the steps above have been completed and Echo is running, make sure that there are no noticeable errors on Echo’s screen.
Make sure that the next song played in Audiovault is received by Futuri. Now Playing entries should also be displayed in Echo's GUI.
To test the music log parsing process, you can move the logs around to simulate a new log:
- Go to Echo’s output folder (found in the output field in station.xml, i.e. M:\WXYZ\Music)
- Cut today’s log and all future logs and paste them in Echo's input folder (found in the input field in station.xml, i.e. M:\WXYZ\Music\input).
- Within about 60 seconds, Echo should detect a change and put the parsed copy in the output folder (and a backup in the backup folder).