Output Formats and Groups Formats
Users can define the data output streams via that streams configuration screen.
|
|
Administrators should note that
when the HDP PSD data output option has been selected, the Data Output
format will become grayed out and locked. HDP data is 'set' for specific
fields. One can modify the data that 'relates' to these fields via the INI
file. There is also a method of injecting alternative data for these fields. This method is described below. |
| The Default Output Format Template allows one to
set a default string that will be used. One can enter literal text along with
XML Field data fields.One can also specify items such as Station Slogans,
ID's, Comments and other Messages.
|
![]() |
|
|
For details about configuring DAD and the creation of XML files, one should review Setting Up Playback State in DAD. |
|
|
NOTE: When the option: Raw XML has been checked; the Default Output Format along with Group Formats will not be accessible. When this option is checked, PADapult will simply resend any XML data it receives. |
To output data from a XML Data tag field, one must enter that filed encapsulated within square brackets. While the square brackets is a requirement, the XML tag field names are not case sensitive.
For example:
You are listening to [TITLE] by [ARTIST].
The above will display the literal text along with any data from the currently playing audio file. This data will be taken from the XML Title and Artist Tag fields and entered into the Title and Artist field of the Output Format.
In addition to normal XML Tags, users can also use special fields to output specific data. These special fields are as follows:
[SLOGAN] - When Slogan is used, the currently selected SLOGAN will be used. This can be set in the INI file under the [AUTO INFO] section. When using Manual Mode, the currently selected Station Slogan will be used.
[STATIONID] - The STATIONID set in the INI file under the [AUTO INFO] section will be used. When using Manual Mode, the currently selected Station ID will be sent.
[COMMENTS] - Users can enter a string of text into the Comments field on the Main screen.
An administrator could then create a customized string for their station. For example:
Now playing [TITLE] by [ARTIST] on [STATIONID] [SLOGAN]
One can also set a defined length for specific fields. This is done by using a colon ' : ' and the maximum number of characters to output for that field name. In the example below, only the first fifteen characters of the Title field will be sent and displayed.
OUTPUTFORMAT=[SLOGAN]:[TITLE:15]:[STATIONID]
|
|
To send the DAD Cut Number in an Output Format String – use [CUTID] for the DAD data field. |
One can then have each Data stream customized for that steams purpose. One might have the one string for the Web Streaming service while another Output Data format for RDS. The information relating to the database field such as [TITLE] will stay the same with the formatting of database field or literal text being unique.
Additional customization can be achieved by using the Group Formats.
|
Group formats are based upon the GROUP tag in the XML file and the currently playing cut's Group association in the DAD Library database. When the Group Tag matches a Group Filter, the Output string for that Group will be sent. If a Group Tag does not match, then the Default Output string will be sent.
Administrators can create Group Filters for specific Groups such as COMM for Commercial material. When an audio cut in the COMM group is played, one could have PADapult send a string such as:
Keep Listening for more of your favorites coming up next!.
|
![]() |
|
To create a new Group Format, press the NEW button.
Enter the GROUP name and the Output Format desired. The Output Format follows the same structure and rules as described above. Formats can be literal text or can contain XML Field tags such as [TITLE] or [ARTIST].
|
![]() |
One could then create specific Groups for specific purposes such as sponsorships. For example, one might create a Group called SPONSOR and populate it with Advertisers. Then when that sponsor plays on the air, it's data is sent to PADapult. A Group Filter could be created with the Output Format as: This show is being brought to you by [TITLE].
Priority Levels
In addition, users can set a Priority level for the Group Format. Priority Levels allow an administrator to interleave other messages with the normal PAD data about the audio cut playing.
High Priority (listed in RAMA as level 2) messages will be sent to the Destination and will remain as the current message display. A High Priority message can only be cleared by sending a CLEAR message to PADapult. At that time the it will be cleared allowing other messages such as PAD data associated for an audio cut. For example, when an audio cuts PAD data is sent followed by a High Priority message, one would have PAD data, then High Priority message until the High message has been cleared.
Medium Priority messages (listed in RAMA as level 1) will rotate equally with PAD data, PADLive Messages and Scheduled Messages. In this case, one would have PAD data and Scheduled Messages (if scheduled) followed by the Group Format Medium message. All messages would then repeat again until the next song plays.
Low Priority messages (listed in RAMA as level 0) are only sent once. This message would only be displayed briefly between the rotating PAD data and Scheduled Messages.
Additional Group Filters
Within Group Filters one can use PADLIVE or SCHMSG as a Group Name. When one uses PADLIVE as a Group Name, any strings entered via the PADLIVE application will be sent out. Likewise, when using SCHMSG, any of the predefined Scheduled Messages will be sent.
The output of these special filters should be limited to the basic default HD data display fields such as [TITLE] , [ARTIST], [ALBUM] and [GENRE]. When a field such as [TITLE] is used, PADapult will output the PADLIVE or Scheduled Message string into the TITLE display of the HD Receiving unit.
Details about using PADLIVE can be found here.
Details about configuring Scheduled Messages can be found here.
Field Over-rides and Group Output Format Control for HD Outputs
For users who are selecting the HDR HDP/PSD Output option, there is an option for over-riding the information in the 4 major HDP PAD fields.
This can be done for either the Default Output Format Template or can be based upon a Group Output Format.
For example:
Title: {whatever you want} Artist: {whatever you want} Album: {whatever you want} Genre: {whatever you want}

For stations that music is NOT the primary audio source, you can use the above example as the Default Output. You would then create a Group for the groups that your songs would come from and create a Group Output Format with nothing in it at all. This would allow the normal Title/Artist/Album/Genre fields to pass thru to the exciter when a song does play.
Alternatively, if your most common output is a Song you could leave your Default Output Format Template blank and specify the over-ride output using Group Based Outputs.

Syntax rules for these over-ride strings:
Only these four field labels are supported:
Title: { }
Artist: { }
Album: { }
Genre: { }
The syntax must be EXACTLY as shown with the proper case and colon.
The text within the {braces} immediately following the label will be used to replace that HDP field.
Missing braches will cause the over-ride to be ignored.
If you do not want to over-ride a field, just leave it out of your Output Format String.