RDSText CONFIGURATION

Flu-O Radio and Flu-O TV can generate a .txt with information about the currently playing elements.

To have the .txt file automatically generated, you must create the RDSText.dat file within the folder: “..\Shared\Config\CH<n°>\” and enable the “Export item information on play” function in the playout configuration.

The file generated by Flu-O will be called RDStext.txt and by default is saved within the shared folder that you set (..\Shared\Data\CH<n°>\Computer\ComputerName\ ), is useful for<ComputerName>getting information about the songs on the air to pass to the RDS or to add data to the Radio/TV stream.

This guide will show you all the commands that you can use within the RDSText.dat file so that you can customize your RDSText.txt

The commands to be inserted into the .dat file should be placed in square brackets[ ].

[ExcludeInner]
Table_element=_commercials

[Text]
<Artist> - <Title>

A first example of RDSText.dat where items in the commercials table are excluded from writing to the .txt file, and “Artist – Title” information is written to all other reproduced files.

Text

The comman[Text]d indicates what and how it should be written within the RDSText.txt.

The preceding example will write to the RDSText file.txt the Values of the Artist and Title fields separated by ” – ” of the on-air element. When referring to a variable field, it is important to place it within < >

Examples

[Text]
<Artist> - <Title>

Writing: Michael Jackson – Beat It

While without < >

[Text]
Artist - Title

Will write: Artist – Title

You can insert all the fields in the Status file into the data you want to write.dat. The Status.dat file is located in: “..\Shared\Data\CH<n°>\Computer\<ComputerName>\”

Using the command [TextSong] in the same way, you can diversify the text writing of all elements of the songs table from the others. For example:

[Text]
<Title>

[TextSong]
<Artist> – <Title>

In this case the Title will be written for all the elements on the air and Artist – Title for songs only.

Exclusion and Inclusion

Here are the expected exclusion commands:

• ExcludeSame: Excludes items with the same values from writing the .txt file as the previous item
• ExcludeInner: Excludes the entire item indicated
• ExcludeStart: Excludes subsequent items including the one shown from writing
• ExcludeEnd: Ends the exclusion from writing data from the item after the specified item

Then there are the corresponding parameters for Inclusion that work in the opposite way:

• IncludeSame
• Include Inner
• IncludeStart
• IncludeEnd property

You can match them as you like depending on your needs. Here are some examples:

[ExcludeInner]
Table_element=_clips
Table_element=_commercials
Table_element=_programs
Table_element=_shows
Table_element=_automations
Table_element=_voiceover

The parameter without any indication of element “ExcludeEnd” will not be taken into account, instead all elements that will go into play of the tables will be excluded from the writing of the txt: clips, commercials, programs, shows, automations, voiceover

[ExcludeStart]
Note=BREAK
[ExcludeInner]
Table_element=_automations
Table_element=_voiceover
Table_element=_announces

In this case, all elements after all BREAK notes and elements belonging to the tables will be excluded: automation, voiceover and announces.

[IncludeInner]
Table_element=_songs
Table_element=_commercials
[ExcludeInner]
Table_element=_clips
Table_element=_programs

In the latter case, you will include information about the elements in the songs and commercials tables in the write and exclude information from the clips and programs tables.

For all excluded items, the RDSText.txt file will be empty.

Empty

Using the parameter [Empty], you can have Flu-O write custom text.

Example

[Empty]
Text=Radio Bitonlive

This way, every time one of the excluded elements with exclude commands airs, “Radio Bitonlive” will be written to the RDSText.txt file.

You can also create an Empty word schedule to customize the RDS by day and time of the week by using the following format:

text@d_HHmm-HHmm=text to be written on day “d” from “HHmm” hours (included) to “HHmm” hours (excluded)

Where “d” represents the day of the week, from 1 (Monday) to 7 (Sunday), “HH” hours in 24 format and “mm” minutes.

NB: Midnight must be indicated with 2400 in the case of the end time (excluding), in case of departure time MUST be indicated with 0000

Example

[Empty]
Text=Radio Bitonlive
Text@1_090000-120000=Text1
Text@3_130000-150000=Text2

In this case, therefore, the writing of the RDSTxt.txt will show by default, for all excluded elements, the inscription “Radio Bitonlive”, on Monday (1) from 9 to 12 “Text1” and on Wednesday (3) from 1 pm to 3 pm “Text2”.

In this way you have the possibility to plan personalized writings depending on the program broadcast during the various times of the different days of the week.

attention

If rdstext scheduling times overlap, the first one will be written until the end of your time.

example:

[Empty]
Text@1_090000-140000=Text1
Text@3_130000-150000=Text2

The written Text1 will be written until 13:59 and will be replaced by Text2 only at 14:00

NB: If a program is at the turn of midnight, you will have to divide the command into 2 indicating for example:

[Empty]
Text@2_2300-2400=Midnight Schedule
Text@3_0000-0200=Midnight Schedule

Upload

The RDSText.dat can also command the upload of data to an FTP by indicating in the .dat file of the command [Upload].

The Mode tag can be 0 (text-only upload) or 1 (text and cover image upload).

[Upload]
Mode=1
URL=ftp://ftp_address
User=username
Password=******
Passive=
DefaultImage=
DefaultImage-Songs=
DefaultImage-Clips=
DestinationFileTxt=
DestinationFileImage=
SubFolderSaveImageAsTitle-Songs=
SubFolderSaveImageAsTitle-Clips=
Timeout=
MaxFile=
TextEncoding= 

To function it is necessary to indicate

• URL: Address of the ftp server to upload to
• User: User name for ftp access
• Password: to access FTP
• Passive: 0 if the connection is active, 1 if the connection is passive
• Default Image: Path and name of the image on the airing PC to be used in case of lack of cover
• DefaultImage-Songs: Path and name of the image on the airing PC to be used in case of lack of song cover
• DefaultImage-Clips: The path and name of the image on the airing pc to use in case of missing the clip cover
• DestinationFileTxt: Local save location and name (including extension) of the .txt file that is useful for uploading to FTP
• DestinationFileImage: Locally saved path and name (including extension) of the image that is useful for uploading to FTP
• Timeout: The time in milliseconds that the connection times out.

RadioTool

It is possible to configure (for each [Filename<n>]) the updating of data on a remote RadioTool endpoint. The configuration is the following:

[RadioTools<n>]
url=##endpoint address with apikey##

The software automatically manages the data to be sent according to the Text / Empty settings in the scope of [Filename]

Writing to multiple files

Using the command you c[Filename]an save an n number of .txt files and indicate accordingly the different parameters with which to write the information of the songs on the air.

Once you have entered the comm[Filename ]and you will also need to set all the other commands with the indication of the number <n> entered.</n>

Here’s an example:

[Filename2]
file=RDStext2.txt

[Empty2]
Text=*** Radio Bitonlive ***

[IncludeInner2]
Table_element=_songs
Table_element=_compositions

[ExcludeSame2]

[ExcludeStart2]
Note=BREAK

[ExcludeEnd2]

[ExcludeInner2]
Table_element=_clips
Table_element=_commercials
Table_element=_programs
Table_element=_shows
Table_element=_automations
Table_element=_voiceover
Table_element=_announces
Title=_document_

[Text2]
<Title> - <Artist> 
[TextSong2]
<Artist> - <Title> - <Year>

In this case, the new .txt file will be saved in the same folder as the default folder (..\Shared\Data\CH<n°>\Computer\<ComputerName>\) as RDSText2.txt

Send String in TCP and UDP

you can also send the string with song information that is broadcast over tcp and udp

To configure it, you must set a command [Filename] as for multiple file writes and add the Tcp or Udp tag with the address and port indication (IPaddress:port) to send the string to.

Tcp sample:

[Filename2]
file=RDStext2.txt
tcp=127.0.0.1:11111

Udp sample:

[Filename2]
file=RDStext2.txt
udp=127.0.0.1:11111

In both cases, all parameters will be defined as indicated for writing multiple files.

BrandsAreLive

It is possible to configure (for each [Filename<n>]) the updating of data on a remote BrandsAreLive endpoint. The configuration is the following:

[BrandsAreLive<n>]
stream-id=##id of the stream assigned to the radio##
default-image-url=##remoto url of the default cover image that will be displayed. Cannot be empty##
default-title=##Default title. Cannot be empty##
default-artist=##Default artist. Cannot be empty##