Grid Editor US
Grid Editor US
USER GUIDE
Introduction
This documentation is designed to help you everyday to work with RadioAssist.
Each topic represents one tool of the Radio-Assist range of products and all
functions are explained in detail.
However, following the different radio configurations, some tools or functions are not
available on your work station.
NETIA
Contents
Chapter I GridEditor 1
1 Workflow
................................................................................................................................... 1
2 GridEditor
...................................................................................................................................
definition 3
3 Time slot
................................................................................................................................... 3
4 Creating
...................................................................................................................................
a time slot 3
5 Modifying
...................................................................................................................................
a time slot 5
6 Program
...................................................................................................................................
Metadata 7
URL Files .......................................................................................................................................................... 9
Im ports .......................................................................................................................................................... 9
Start and End ..........................................................................................................................................................
events 10
Presentation/Guests/Team
..........................................................................................................................................................
/Channels 10
Description .......................................................................................................................................................... 11
7 Copying
...................................................................................................................................
a time slot 11
8 Deleting
...................................................................................................................................
a time slot 13
9 Filling...................................................................................................................................
in a time slot 14
10 Create...................................................................................................................................
a screen (Break) 15
11 Broadcast
...................................................................................................................................
modes 17
12 Events...................................................................................................................................
On Screen 18
13 Copy and
...................................................................................................................................
paste a screen 22
14 Metadata
...................................................................................................................................
items 22
Create and add
..........................................................................................................................................................
a Metadata item 23
Modify a Metadata
..........................................................................................................................................................
item 24
Delete a Metadata
..........................................................................................................................................................
item 26
15 Create...................................................................................................................................
a run (Step) 26
16 Locked
...................................................................................................................................
duration 29
17 Copy and
...................................................................................................................................
paste a run 29
18 Template
................................................................................................................................... 30
Creating a tem..........................................................................................................................................................
plate 30
Deleting a tem..........................................................................................................................................................
plate 31
19 Validity
...................................................................................................................................
period 32
20 Exception
...................................................................................................................................
Grid Days 32
Choosing exception
..........................................................................................................................................................
grid days 33
Multiple Grids.......................................................................................................................................................... 35
21 Imports
................................................................................................................................... 35
A - SETTINGS .......................................................................................................................................................... 36
File Settings
......................................................................................................................................................... 37
Item Selection
.........................................................................................................................................................
Settings 39
Import Settings
......................................................................................................................................................... 40
Specific Actions
......................................................................................................................................................... 41
Link Betw een
.........................................................................................................................................................
Numref and DB 42
Copyright 2016 by NETIA - All rights reserved. AMA/APO – 06/2016 – v1.2 Contents I
B - LINES .......................................................................................................................................................... 42
22 Music ...................................................................................................................................
scheduling 46
23 Create...................................................................................................................................
a playlist 46
1.1 Workflow
GridEditor 1
Radio-Assist 8 - Grid Editor
Copyright 2016 by NETIA - All rights reserved. AMA/APO – 06/2016 – v1.2 2
1.2 GridEditor definition
"GridEditor" is a planning tool which is used to create the program grid.
· Template creation.
· Time slot creation.
· Assignment of templates to timeslots.
E.g.: A time slot called "Morning " is reserved in the program grid from 06h00 to 09h00
and is broadcast every day of the week except weekends from 11/6/05 to 31/8/06.
The slot contains a number of events represented by templates and their program steps
which are broadcast one after the other at a set or variable time.
GridEditor 3
· Enter the parameters of the time slot (time slot name, validity period, begin time, end
time, valid day(s)).
· In the grid, right click on the slot you wish to modify and then select "Modify program
parameters".
GridEditor 5
· Modify the parameters of the time slot (time slot name, validity period, begin time, end
time, valid day(s).
GridEditor 7
The following window is displayed.
The name as well as the hours for the beginning and the end of the program are
automatically displayed.
The box allows you to change the settings for the start time
and the end time of the show, should these settings be changed.
URL files : It is possible to attach URL links or any other kind of file to a program.
As regards URL files, click on , populate the URL field, then click on .
As regards files, click on , WIndows explorer will open. Select teh file you wish to
To open the link or the file, select it from the list and then click on .
To delete the link or the file, select it from the list and then click on .
You will be able to reach the file by clicking on the following icon .
1.6.2 Imports
Add the imports related to the specified program.
· Click on then select from the list the import that is related to that program.
· Click on
GridEditor 9
1.6.3 Start and End events
Start and end events :
It is possible to attach different kinds of events to the beginning or to the end of each
program (Gpi, switch to auto mode, recording start, and so on...)
All these elements are set by the administrator and will be added to GridEditor.
1.6.4 Presentation/Guests/Team/Channels
This zone allows you to give three levels of description for the program (quick description,
normal and complete)
Write the text in the fields you wish to use.
Valdation will be done once you'll click on at the bottom of the window.
· In the grid, right click on the slot you wish to modify and then select "Copy program".
GridEditor 11
· Enter the parameters of the time slot (time slot name, validity period, begin time, end
time, valid day(s).
GridEditor 13
· Click on « Delete program » .
Click on .
· Drag and drop from the Browser to the time slot and build the frame of your time slot.
· Right-Click on the Screen and then choose "Modify" or "Create empty screen" from the
menu.
You can modify or type the screen name (break name), the category and the broadcast
mode.
GridEditor 15
The "Duration wanted" box can be ticked in order to specify a wanted duration for this
screen.
Type the durantion wanted (HH:MM:SS)
If the reel duration of the screen is superior to the typed duration, the difference will be
shown in red.
If the reel duration of the screen is inferior to the typed duration, the difference will be
shown in green.
· Floating Time : The screen is broadcasted automatically after the previous screen
· Off time : Screen with an automatic start time which is automatically calculated
according to the end of the broadcast time set by the user. End time: time set for
screen broadcast to end.
· Time limit : Screen with automatic broadcast at a set time + start screen. If broadcast
of the previous screen ends during window countdown, this screen will be broadcasted.
If it is not over, the Auto window screen will not be broadcasted and the broadcast
· Time limit forced : Screen with an automatic broadcast time. Same procedure as "Time
Limit" except that the screen is automatically broadcasted at the end of the defined
window.
· Near on time : The screen is broadcasted at a set time. Nonetheless, Air-DDO will wait
for the song (which is on air in the previous screen) to be over before starting the new
screen :
· Sync OnTime : Same procedure as "Time Limit". The difference is that the screen is
IMPORTANT : These broadcast modes are defined in "GridEditor" and "Feder-All" but they
are used in Air-DDO (playout system belonging to the Radio-Assist range of products).
GridEditor 17
1.12 Events On Screen
Input Events allow you to trigger an action when the screen starts going On-Air.
A) INPUT EVENTS
Air-DDO awaits an event to start broadcasting the screen. At the beginning of the screen,
Air-DDO receives an event. This starting mode can only be used with TIME LIMIT and
TIME LIMIT FORCED modes (indeed, ON TIME mode will be triggered based on the exact
hour).
To create a new Input Event, complete the popup with the name and the parameters of
the events, then click on . Your event now appears in the drop-down menu and you
can use it on any screen.
GPI
This type of event allows you to start the screen on reception of a GPI command.
COM
This type of event allows you to trigger the broadcasting of a screen on reception of the
COM command.
The fields "Data", "Parity", "Num Com", "Baud Rate", "WordLenght" and "Stopbits"
correspond to the configuration of your COM port.
IP
This type of event allows you to trigger the broadcasting of a screen on reception of the
IP command.
B) OUTPUT EVENTS:
To create a new output event, complete the popup with the name and the parameters of
the events, then click on . Your event now appears in the drop-down list and it can be
used on any other screen.
GPI
An output GPI event means Air-DDO sends a GPI command when the screen starts (for
example, the ON-AIR light is on when broadcasting starts).
COM
An output COM event means Air-DDO sends a command which triggers a COM command.
The fields "Data", "Parity", "Num Com", "Baud Rate", "Wordlenght", Stopbits" correspond to
your port COM settings
· Offset : the Offset defines the position from which the COM command is sent.
IP
An output IP event means Air-DDO sends an IP command.
RECORD COMMAND
· Name : name given to the event
· Duration : N/A
· Address : listening address
· Ident : command identifier
· Data : IP command sent
GridEditor 19
· Port : Listening port
· TTl : Time To live (value fixed at 255 by default)
· Type : UDP or TCP
· Action : Start or Pause or Stop
· Offset : the offset position defines defines the position from which the command is sent
FADE AUTO
The FADE AUTO event only works with the ON TIME and OFF TIME modes. When the FADE
AUTO option is activated, it means the screen will start on time, operating a fade out on
the previous item (instead of cutting it abruptly).
- If the value is fixed to 0 = the fade out will start at the beginning of the ON
TIME/OFFTIME screen,
- If the offset is negative = the fade out will start BEFORE the starting time of the
ON TIME/OFFTIME screen,
- If the offset is positive = the fade out will start AFTER the starting time of the
ON TIME/OFFTIME screen,
MODE AUTO
The AUTO command allows you to switch from manual to automatic mode in AIR-DDO, and
conversely.
In other words, if the START AUTO parameter is set to ON, the screen will start from the
position to which the screen should be playing.
SHELL COMMAND
· Nom : name given to the event
· Duration : N/A
· Cmd : name of the command you wish to trigger (command executed by the
workstation's OS)
· Offset : the offset position defines the position from which the command is executed
GridEditor 21
- If the offset is set to "0" = command is executed when the screen
starts
- If the offset is negative = command is executed before the screen
starts
-If the offset is positive = command is executed after the screen
starts
VLSU
This type of event is used in correlation with localization players, in order to send a PLAY
order to the different PLAYERS in use (Digitrack or LocPlayer)
Then place the cursor where you want to paste the screen, right-click and select "Paste"
in the meu.
The configuration will be made upstream to create the tab and all the criteria that can be
added to the screen.
To create a Metadata item, in the Browser click on on the right of the screen
GridEditor 23
IMPORTANT: These items created in the database will be used as "ORGINAL".
That is, whenever an original item is added in a playlist or a playlist is generated
using an original, a copy will be created in the database but without an icon in the
browser.
To do so, open the show, then drag and drop the item on a screen.
From now on, all palylists generated from this template will have the item linked to this
screen.
To modify a Metadata item, right clic on the icon and right click.
GridEditor 25
Metadatas are saved.
To delete a Metadata item, right clic on the icon and right click.
Click on YES.
Example : a template named "News" contains steps for each type of news :
"International news", "National news", "local news" etc.
Simple Run : It's the most commun type of run. No setting needed in advance or later
GridEditor 27
Event Run : Run used to apply events (GPI activation, record command, fade auto, etc...)
These events are crated by system administrators.
Target Run : Run used when using the Radio-Assist music scheduling integrated solution.
Example : if the step (event) is 5 seconds long, and you insert inside an audio file which is
10 seconds long, it will be possible to play 10 secondes but the duration in the playlist will
remain 5 secondes.
GridEditor 29
Then place the cursor where you want to paste the run, right-click and select "Paste" in
the meu.
Select them using the CTRL or SHIFT key, depending on the selection mode wanted (one
by one or a group of runs).
Then place the cursor where you want to paste these runs, right-click and select "Paste"
in the meu.
1.18 Template
A template describes the content of a program of part of a program. A template is
composed by screen (Break) (example : program name) and steps (events) - (program
detail).
· Click on the "Template" icon to create and then on the following button (circled in red).
GridEditor 31
A message to confirm the deletion is displayed. Click on « Yes» to confirm the deletion or
« no » to cancel the action.
(Example : The « News » time slot from 0h to 2h will be valid during 1 year, from
November 1st 2009 to November 2nd 2010, everyday except the week-end).
To specify to Radio Assist the exeption grid days, position your cursor on the grid and
then, right click on it.
GridEditor 33
To select one day, just click on it. It becomes yellow.
From now on, the selected days will appear as "exceptional" days in GridEditor.
Here, every day of the month of july except the tuesdays will appear as exceptional days.
allows you to mark every given day of the week as an exception grid day.
If you choose a starting date and an ending date and untick some days, you'll have two
possibilities:
· By clicking on , Radio Assist will convert only the days between these two dates, the
untick day(s), to exception grid days.
Therefore, you can choose to modify a full programming schedule or only apply a few
changes on your grid.
Depending if the playlists are created automatically ou manually.
1.21 Imports
The Imports window will allow to parameter the settings for files coming from third party
softwares such as Ads Traffic or Music Scheduling.
GridEditor 35
1.21.1 A - SETTINGS
You can choose from the drop-down list the type of configuration you wish to use in order
to import the sounds into the playlists. By default, the list is empty.
To create a new configuration profile, you just have to select NEW. Once you're through
with the setup, save your profile (via the icon) and it will appear in the drop-down
list.
The settings are saved in an XML file present on the record path of Radio Assist in the
FEDERALL directory.
The path must therefore be UNC.
The icon allows you to delete from the list the profile that has just been selected.
The two other icons are used to import or export configuration files.
when Radio-Assist users click on the dedicated button , in the FEDERALL module (in
the automatic mode, it is Federall Service which does the import of sounds). The 2
import modes (manual and automatic) can not coexist. 2 simultaneous imports on the
same playlist would cause scheduling problems.
· Loc Import : This box is used only if the "Localization" option is used. An import file is
sent by "LocScheduler" and a cartstack will be created with the items in the import. This
option is only available for automated import (via FederallService).
· Cartstack : The option allows you to create cartstacks instead of playlists.
o This option is only available for auto import (via FederallService).
o The values recovered to qualify the cartstack are limited:
§ PLAYLIST_NAME is used for the title of the cartouchier
§ TIME_BEGIN_ST for the startdate and boradcastdate
§ For carts, the RUN_NAME is used to fill the textHead
§ We update the items durations and NumRef for the recheck cartouches
· File name : .txt or .xml file's name format used for the import (for example : %02D%02M
%04Y.TXT).
The dates are filled with wild cards % : 04Y% 02D% 02M (Y = year, M = month D = day).
% 04Y means one year out of 4 digits.
GridEditor 37
e.g : ImportFile% 02D% 02M% 04YourChannel1.XML (for example:% 02D% 02M%
04Y.TXT).
· File path : UNC Path. Path to the file generated by the scheduling software
(MusicMaster, Selector…) used for the import of sounds into RadioAssist.
· Xsl path : UNC Path. Complete file's path to the .xsl sheet used to convert the xml file
(generated by the third-party application) into the format supported by RadioAssist.
· Skip X Lines : possibility not to take into account the first lines of the import file. You
can leave this box empty.
· Field type : defines the type of formating for the import file. Fields can have a FIXED
size or they can be separated by DELIMITERS.
· Format : the file can contain 1 (single) or 2 (multiline) types of lines.
· First line delimiter: Character or string of characters located in first position of each line
of the import file allowing to define the main type of the element to be created (screen
for a playlist or cartstack item in Cartstack mode).
· Other lines delimiter : Character or string of characters (located in the first position of
each line of the import file) to define the secondary type of the element to be created
(not for a playlist or cartstack in the T_RTF table in Cartstack mode).
· After import : action performed by Federall Service on the file used to import the sounds
(Delete file/Do nothing/Move file to [done] directory/Rename file [.done]…)
· Do recheck if file not found : here you choose whether Federall Service must rescan the
database later in case some sound files were not found the first time (the re-check
frequency is defined in the "Playlist Import" section, in the Federall Service Setup
window).
· Create Log File : Create a log file generated in the folder whose location is noted in "Log
File path"
· Keep run infos on recheck : Keeps run information when associating a run created by
the import with a sound from the database.
The informations kept are:
o RUN_NAME
o SPECIAL_RUN_DURATION
o LIST_FADE
o X_INLINK
o X_OUTLINK
o INTROMS
o OUTTROMS
This option makes it possible to keep the work done on a third-party application in terms
of mixes, fade points and cutting of the sound during an import (when associating a sound
with a run, one normally takes the default information of the sound).
· Match on whole playlist : Allow imports with unordered items (screens or not) in the
import file.
When importing, we treat each line of the import file one by one. Traditionally, for each
new line, one looks for the corresponding element in the associated playlist and this, from
the last element found. With this option enabled, we go from the first element of the
playlist to each new line of the import file.
· Import items : In this section, you can choose the status of all the items that must be
inserted into the playlist.
Does Federall Service have to deal with :
GridEditor 39
- All types of items?
- RTB items?
- RTB and broadcastable items?
· Prefer alternate item prefix : An alternative item import can be set. These items must be
stored in the database with the same identifier as in the file but preceded by a prefix.
Example ::
File Ref = 1234
Prefix = ALT
The import will look for priority if there is an identifier ALT1234 in ABC8. Otherwise he will
look for the identifier 1234.
· Prefered choice : here you choose which item must be used for import :
o FIRST FIND
o PROD item (virtual file)
o MASTER item (physical file)
Import on playlist : Choice if the import is done in all playlists, or only RTB or not RTB.
- The first one (INSERT ITEMS IN SCREEN) creates the playlist's structure (the structure
must first be defined in the txt or xml files that are ingested by Federall Service)
- The second one (USE TARGET RUN) does not imply any structure creation : Federall
Service only inserts the sounds in the empty runs with a specific name (ex : $MM)
In the first case, fields are configured by default (ie. screenshot here above) but it is
completely possible to change the parameters. Federall Service creates the playlists
without using any pre-existing structure. The service will use these parameters if no
information is found in the import file.
· Screen start mode : here you choose the default start mode of all the screens (Float,
On time, Time limit…)
· Screen Type1_Item : Radio-Assist's reference tab, in which the sounds to be imported
are.
· Use run target : when this box is ticked, the playlist's structure is not created. Federall
Service fills the playlists, basing itself on a pre-exisiting structure (which has been
defined before by Radio-Assist users in GridEditor)
· Target Run Name : name of the 'runs' in which the sounds must be inserted (ex : $MM)
· Delete empty target step after import : this option allows you to delete runs which
remain empty after the import. (For instance, if the scheduling application has prepared
5 sounds in the 4PM-5PM time slot while there are 8 'runs' called $MM in the Radio-
Assist's playlist, Federall Service will delete the 3 remaining empty runs for which there
is no associated sound to import.
· Start Importing after current time : when this box is ticked, Federall Service starts
importing sounds in the playlists that are scheduled for after the current time.
· Insert empty run if item not found : when Federall Service scans the ABC8 database in
search of a sound to insert into the playlist, if the corresponding sound file is not found,
the run that is left empty will be marked as candidate to a re-scan.
It is possible to trigger a specific action depending on the code that is found in the file
used for the import.
· The first column is used to enter the code that must be found in the text.
· The second column is used to specify the type of action you want to trigger when
Federall comes across the above-mentioned code.
Examples of actions : Do nothing, create empty run, create screen, Use screen [NAME] if
not Create it, Use screen [TIME] if not create it, Set chain = NO to prev run, Grid
Screen…
GridEditor 41
In rare cases, a customer-specific feature may be required. The setting results in a
specific code and 2 parameters.
These codes are used today at RTL and Radio France.
In this section, it is possible to enter the references that must be used to find an item in
the ABC8 database. Usally, one reference is enough.
Nevertheless, if Federall does not manage to find an item based on the first reference, it
can use another reference in order to locate the desired item: you can use up to 6
references.
1.21.2 B - LINES
This section is used to describe the structure of the txt or xml file generated by the third-
party application:
The 'field boxes' correspond to the different columns that appear in the txt or xml file:
- The first section (here in the example : '6' ) means that the field's text starts on the
fourth character position
- The third section : 'TYPE_ACTION' means that the action noted in the "Specific action"
field will be done. Here, creating a screen.
GridEditor 43
INTROMS introMS du pas.
ITEM_NAME Item's name.
ITEM_REMARKS Remarks associated with the item.
LOCPLAYER Loc player name as part of a location import.
NUM_CD Num_CD ref.
NUM_SELECTOR Num_Selector ref.
NUMREF#1 Dynamic reference number (see NUMREF)
Make the link between the external identifier and a Netia
DBD field for matching.
NUMREF#2 Dynamic reference number (see NUMREF)
Make the link between the external identifier and a Netia
DBD field for matching.
NUMREF#3 Dynamic reference number (see NUMREF)
Make the link between the external identifier and a Netia
DBD field for matching.
NUMREF#4 Dynamic reference number (see NUMREF)
Make the link between the external identifier and a Netia
DBD field for matching.
NUMREF#5 Dynamic reference number (see NUMREF)
Make the link between the external identifier and a Netia
DBD field for matching.
NUMREF#6 Dynamic reference number (see NUMREF)
Make the link between the external identifier and a Netia
DBD field for matching.
PATH Item's path.
PLAYLIST DATE Playlist date. Used in playlist creation mode.
PLAYLIST NAME Playlist name. Used in playlist creation mode.
PLAYLIST START Playlist start time. Used in playlist creation mode.
PLAYLIST END Playlist finish time. Used in playlist creation mode.
POSITION RTL specific. Sets the position of the add step in the
screen (informative)
REGIE RTL Specific. Define the add agency (informative)
RUN_NAME Run name. This one will be used in case the sound matter
is not yet present in Radio Assist. An empty step is then
created with this name. Otherwise the filled name is the
Netia item name.
SCREEN_DURATION Screen duration
SCREEN_NAME Screen name
SCREEN_REMARKS Remarks linked to the screen
GridEditor 45
1.22 Music scheduling
The music scheduling tool integrated in Radio-Assist allows you to perform the following
operations:
The setting of the music scheduling is explained in the "Music Scheduling" documentation.
GridEditor 47
Fill in a time slot 14
Index Floating 17
-G-
-A- GPI input event 18
Add a Metadata item 23 GPI output event 18
Automatic broadcast modes 17 Grid Editor definition 3
Guest 10
-C- -I-
Channel 10
COM input event 18 Import Settings 40
COM output event 18 Imports 9, 35
Copy 11 IP input event 18
Copy a run 29 IP output event 18
Copy a screen 22 Item Selection Settings 39
Copying a time slot 11
Create 3
Create a Metadata item 23
-L-
Create a playlist 46 Lines 42
Create a run 26 Locked duration 29
Create a screen 15
Create a template 30
Creating a time slot 3 -M-
Metadata Items 22
-D- Mode Auto event 18
Modify 5
Delete 13 Modify a Metadata item 24
Delete a Metadata item 26 Modifying a time slot 5
Delete a template 31 Multiple Grids 35
Deleting a time slot 13
Description 11
-N-
-E- Near on time 17
End events 10
Event Run 26 -O-
Events 18
Exception grid days 33 Off time 17
On time 17
-F- -P-
Fade Auto event 18
File Settings 37 Paste a run 29
Files/URL 9 Paste a screen 22
-R-
Record Command event 18
Record to Live event 18
Run 26
-S-
Screen (Break) 15
Shell Command event 18
Specific Actions 41
Start events 10
Step 26
Sync on time 17
-T-
Target Run 26
Team 10
Template 30
Time Limit 17
Time Limit Forced 17
Time slot 3
-U-
URL 9
-V-
Validity period 32
VLSU event 18
-W-
Window 17
Copyright 2016 by NETIA - All rights reserved. AMA/APO – 06/2016 – v1.2 Index 49
GridEditor
The information given in this document is subject to alteration without prior warning
and is not binding upon Netia SA. The software described in this document is supplied
under licence agreement and may only be used or copied within the terms of this
agreement. It is illegal to copy software onto any information support, unless
specifically authorised in the agreement. The licence authorises you to make one
copy for backup.