Audiovault Installation Documentation (#engage / Futuri Mobile)

This article is part of a series on Audiovault.

NOTE: Futuri VIP Support will help you to walk through these steps. We are simply providing the steps here so that you can easily reference them later.

To work through this installation process for the first time, please contact Futuri VIP Support. These instructions may look daunting, but a remote session with one of our Support Agents should only take about 30-60 minutes per station.

This process includes the following steps:

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.

Crowd Control Setup

NOTE: If your station has a Futuri Mobile app but does not have a license for #engage, this section is optional.

Crowd Control is an Audiovault feature that BE has discontinued selling, but they have allowed Futuri to re-use its basic infrastructure to deliver winning songs with #engage. It basically works like this:

  • Echo fetches winning songs from Futuri's web servers and writes the winning cut ID to a file.
  • The Crowd Control script reads the cut ID from that file and copies the audio in that cut ID over to a "placeholder" cart called {ccSlot}.
  • Audiovault plays the audio from the winning cut ID when the {ccSlot} is played. It should also copy over artist/title metadata.

Installing Crowd Control is fairly simple. On the on-air machine, navigate to C:\audiovau\Config\Scripts\AVAirEngine. You will need to add an avair.py file to that folder (which you can download here).

On line 16 of avair.py, set the file to equal the folder where you want Echo to write the winning song to. You probably don't need to change it from its default (C:\audiovau\CrowdControl\ccDownload.txt), but you should make sure that folder exists on the computer.

Once this has been done, restart the computer.

Setting up the LDR category in Audiovault

NOTE: If your station has a Futuri Mobile app but does not have a license for #engage, this section is optional.

The commands to trigger #engage voting features will live in an LDR category in Audiovault, and that category will be treated as "music" by TRE.

Once you have created the LDR category, you'll want to add cuts in that category for each of the following:

  • 9999 - UPickStart
  • 9998 - Empty Song Slot
  • 9997 - Begin Song Replacement
  • 9996 - End Song Replacement
  • 9995 - Begin Top Song
  • 9994 - End Top Song
  • 9993 - Begin FaceOff
  • 9992 - End FaceOff Next

As you create each one, you'll want to hit Start to let it record for a couple seconds. You can later replace the content of each of these items with a piece of call-to-action imaging, but these elements must run for at least 1 second before segueing into the next element.

Echo Setup

Futuri's Echo software bridges Audiovault and Futuri's web servers, allowing listener to interact with the station programming via the station website and/or mobile apps.

Echo should generally be downloaded from here and you can obtain a settings file (named station.xml) from Futuri VIP Support. Do not run Echo.exe without first configuring the station.xml file.

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.

Open station.xml in WordPad, NotePad, or another text editor.

The file should look something like this:

Some notes:

  • Futuri VIP Support will provide the , , , and when they set up Echo with you.
  • For music logs, Echo will watch the  folder for music logs that match the  and will then scan those logs for voting sessions and insert {ccSlot} placeholders as needed. The resulting "parsed" logs will be saved in the  folder, and the originals will be moved to the  folder.
    • If your station has a Futuri Mobile app but does not have a license for #engage, you can add an   parameter in the section, set to true, and in that case Echo will only forward the original logs to Futuri's servers, without creating "parsed" copies.
  • In the  section, the  should be set to the Path you specified when configuring TRE. The  should be set to the path you specified on Line 16 of the avair.py during the Crowd Control setup.

When finished configuring, save station.xml and repeat steps as needed for other stations. Each station will need its own copy of Echo.

Microsoft .NET 4.0 or higher is required for Echo. If needed, you can download it 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 Audiovault to be able to play back winning songs, {ccSlot} placeholders for those winning songs must be in the log. Echo will handle this, as follows:

  • Echo will receive the log from your music scheduler when you export it.
  • For "UPick"-style voting sessions, Echo will replace the group of vote options with a single {ccSlot} placeholder.
  • For Top Song and Takeover, Echo will replace each element named "Empty Song Slot" with a {ccSlot} placeholder.
  • Echo will place the modified log in the folder that Audiovault reads logs from, and will place a copy of the original log in a backup folder.

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).

A note on music log formatting - 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 Takeover/Top Song check-in process, you can play the “Begin Song Replacement” command. Within 30 seconds, Echo should ask Futuri for a winning song.

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).

To do a full end-to-end test, schedule a voting session or Takeover in your music scheduler and export the log from there. It should land in Echo's input folder and within a minute or so Echo will move it to the output folder. You can then import that log in Audiovault and make sure the inserted {ccSlot} placeholder audio fills with a song when the time comes.

J
Jasmine is the author of this solution article.

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.