The Priorities Definition window is where Priority Lists are created that can be Assigned to Dayparts and Categories. Each list has an Unbreakable, Breakable and Fixed section. All goals, rules and segue bans are now available for use in each list. Previously, the legacy rules and segue bans operated independently and were not integrated with the scoring system in GSelector. Now these rules and segue bans can be prioritized in the same lists with other goals. With User Defined Priority Scoring GSelector offers more precise scheduling control. The program can now calculate a proper score for each goal, rule or segue ban by evaluating each in context with all the others. A priority list can also be used for Reverse Scheduling.
NOTE: Spread goals cannot be set to Unbreakable.
Click the Goals tab, then Priorities, then the Definition tab to access a window similar to this detail illustration. This window is divided into two panes the left pane lists the Priority Lists and the right pane lists the Breakable and Unbreakable priorities in the list selected. When this window is first accessed after installing GSelector or creating a new station, the Default Song Priorities list is created. This list has six Breakable default Goals, recommended for good rotation, and marked with an asterisk, and are permanently added to each Priority List created. In default mode, these are fixed and cannot be deleted; they can be ranked according the user's priorities. Two optional Breakable Spread goals and three Unbreakable Rules are also displayed by default - Vocalist Spread, Category Spread, Hour Restriction Rule, Maximum Per Hour Rule and No Repeat Rule. These can be removed from the Priorities list if not required. If the User Defined Priority Scoring option in the Station | Features | Advanced tab is enabled, the Ranking column is removed and a Weight column is added to the Priorities pane with a graphical representation of the Goal Importance. A Fixed option is also added allowing the user to set the Legacy Rules as fixed and define a score value.
Click any area in this image for help
Click any area in this image for help
GSelector's default install mode is to display eight breakable Goals in the Priorities Pane. To these eight basic Goals, you can add any further Goals, Rules or Segue Bans needed. You can also optionally enable the fixed status.
The default Goals are designed to provide even separation for Songs, irrespective of Category spread or any other Goal, to provide the best possible separation. While these Goals are generally seen as key by most programmers, they do not have to be given a high priority.
The Default Song Priorities are listed here:
The Song Linear Spread Goal spreads consecutive spins of a Song to best effect in the current day, or from one day to the next. Generally, it works on the nearest play of a song. This Goal is ignored from Region to Region when working with more than one Daypart Region.
The Song Radial Spread Goal works across all play history, and ensures that all plays by a song are distributed to best effect across the entire schedule, from day to day and hour to hour. This Goal is ignored from Region to Region when working with more than one Daypart Region.
The Vocalist Spread will spread all songs within the Vocalist to best effect. Double-clicking the Vocalist Spread in the priority list will open the Balance Participants window with Vocalist selected.
The Daypart Goal is a Linear only goal that ensures even rotation for Songs in a daypart. The Daypart goal only looks at where the song played in the current daypart ignoring all other plays.
The score of the Depth priority decreases the further into the virtual stack GSelector has searched to locate the song being tested. The greater the depth searched, the greater the score penalty. Use this priority to equalize the spins of the songs in a category.
The Clock Goal works on Goals set in Clocks. See the Clock Goals notes. Double-clicking the Clock Goal in the priority list will open the Clocks window.
The Packet Spread Goal spreads all songs within Packets to best effect. Double-clicking the Packet Spread in the priority list will open the Balance Attributes window with packet selected.
The Category Spread will spread all songs within the Category to best effect. Double-clicking the Category Spread in the priority list will open the Balance Attributes window with Category selected.
The Newly Added Goal spreads out play of all newly added Songs in a Category from other newly added Songs. This goal only applies to the first play of a Song in a Category. Note that this rule works in Songs that are Newly Added to the Station, or Newly Added to a Category, having been moved from another Category, or Activated back in the same Category.
NOTE: There is a further, fixed Goal, not displayed in the Goals list. This is the Next Day Same Hour Goal, and it automatically works to keep the same song from scheduling in the same hour in two consecutive days. This rule can be overridden for Categories with very short turnovers. See the Next Day Hour Separation notes in the Station Settings: Features topic. This Goal is ignored from Region to Region when working with more than one Daypart Region.
TIP: If you work with very small Categories, this is one of the GSelector tools expressly designed for you. See the Tools for High Rotation Categories notes in GSelector Scheduling.
Attribute Specific Legacy Rule Priorities
Pressing the CTRL+F will open the Find option allowing the user to do a "Smart Filter" find. The Finder will search for results as they are typed. To open the Find option click the pane to search and press the CTRL+F keys on the keyboard.
CTRL+F - Invokes the Find Panel.
ESC - Clears the search box. If the search box is empty, pressing ESC closes the Find Panel.
DOWN ARROW - Moves focus from the Find Panel to the grid's data area.
The Priorities Lists pane holds created priorities lists, these lists can be set flagged for Reverse Scheduling. These Lists are then assigned to Dayparts and Categories in the Priorities Assignment tab.
Click any area in this image for help
Click any area in this image for help
The Priorities List toolbar is used to add, edit, delete or copy Priority Lists. A Priority List can be copied to the current station or to other stations. The toolbar is also used to save or Cancel changes, and apply a Score Threshold. Toolbar buttons may vary in color based on the Appearance Style selected.
Content is a Rule that is primarily used by those stations under governments that require a certain count or percentage of a station’s music to be of local origin. To apply the Content Rule double-click the Priority List to use and select the Apply Content Rule option.
When the Content Rule is applied, it looks at the defined Content Rules, to find songs with a matching Content Attribute, to achieve the desired ratio of local to non-local origin.
When enabled in the Station - Features - Advanced tab a Priorities List can be selected as Reverse Schedule. The Reverse Schedule column shows which Priority Lists are being used for Reverse Scheduling. The default GSelector scheduling setting is to schedule forward from the set start date and time in the Scheduler window. This option gives users the ability to reverse the scheduling order, for any Category Group, Themes or <Twofers> pass, working backwards from the end date and time to the start date and time for the specified scheduling period. Any Category Group, Themes or<Twofers> pass can be set to be scheduled in reverse order. See the Reverse Scheduling notes in the Scheduler window topic.
This pane shows the Goals, Rules and Segue Bans that have been added to the selected Priority List, the order in which they have been ranked by Priority or a user defined weight score, if they are protected against Links, if they are protected Across Regions, and a graphical representation of the Goal Importance. The default install setting is to display seven breakable fixed Goals, and two optional Goals and the rank by priority. For any Goal, Rule or Segue Ban in this list, GSelector spreads Songs by their designated attributes or participants, evenly, for best rotation through the schedule. In the Breakable section of this pane, GSelector prioritizes each goal, rule or segue ban by the order set in this section, from the top down to the bottom, in the numbered order shown. The user can further rank these breakable goals using a weighted score by enabling the User Defined Priority Scoring option in the Station | Features | Advanced tab as seen in the following image. The Unbreakable Rules and Goals are treated Equally. Double-clicking any Legacy Rule in this pane will open the Rotation Rules window properly configured to work with the settings of that rule.
The optimum natural balance of the library is not only affected by the balance set for each attribute, but by the priority assigned in this window. See the notes on Setting a Goals Priority and Setting a Goals Weight Score for how to order the priorities added.
The Priorities pane toolbar is used to add or delete Goals, Rules and Segue Bans, and to reorder the Priority rank (see Setting a Goals Priority in this topic). If User Defined Priority Scoring is enabled, in Setup | Station | Features | Advanced tab, the reorder arrows are hidden.
A Priority is a goal, segue ban or legacy rule that has been added to a Priority List. Click the green Add Priority button to view a menu of Priority Types such as Spread, Segue Ban, Legacy Rule or Goal. Each type will list the Priorities available in that group. Optionally, select All to view a list of all the priorities available. Segue Bans and Legacy Rotation Rules can be set as Breakable or Unbreakable. An Unbreakable priority means GSelector will leave a position unscheduled if all songs available for scheduling violate the Priority. The list order of the Breakable, Priorities is important. Place the more important priorities higher in the list. During scheduling GSelector will compromise a lower breakable priority if doing so will protect one or more higher priorities.
Attribute Specific Legacy Rule Priorities
When scheduling a position, GSelector tests all songs in the category. Depending on how well a given priority is met, the scheduler applies a numeric score ranging from 60 to 100. There are several exceptions in which the lowest score could be less than 60, but these kick in only when you have strayed from default settings in the first two settings in the Setup | Station | Features | Advanced window. The score range is based on the American scholastic grading system in which 60 represents a failure and 100 implies perfection. Those familiar with this score range can instantly recognize that 75 is a “C” or average grade, 85 is a “B” or very good grade and “98” is an “A” or great grade.
The way in which scores are computed varies, depending on the goal. We’ll use Song Linear as an example Natural demand plays a fundamental role in scoring all of the linear spread goals. When testing linear spread for an attribute of a song or link on a particular schedule position, the scheduler will apply a score of 100 if the turnover that would result from scheduling the element in that position is equal to or greater than the natural demand of the attribute being scored. If the turnover that would result from scheduling the element is less than the natural demand, the score will be less than 100. The actual score value will be calculated based on the degree to which the turnover in the tested schedule position deviates from the natural demand of the attribute being scored. Note that each goal is scored separately in a similar way and all priorities are scored for all songs.
Scaling is applied to each score, with the exception of the first priority on the list, according to its location in the prioritized list. The further down the list the greater the score increase. The score of the priority at the very bottom of this list is increased by 15, while scores of the priorities between it and priority at the top of the list are scaled proportionally using 15 as the base. An example will help clarify this. Let’s say that for a given song in a particular schedule position, Song Linear scores at 60, a failure. Now let’s say that Song Linear is at the very bottom of the Priority List. In this case the score will be increased by 15 to 75, to account for the greater importance of the higher priorities on the list. The scores of higher priorities will be scaled proportionally.
After scoring all elements in the category for all priorities and scaling the scores, GSelector determines which attribute has the lowest score for each element. One song’s lowest score might be Song Radial at 65, for example, while another’s could be Vocalist Spread at 85. From this collection of lowest scoring priorities, the scheduler chooses the song with the highest lowest score and places it in the schedule. In other words, GSelector chooses the element whose greatest liability is the highest scoring when compared to the greatest liabilities of all other elements. In the case of a tie, GSelector chooses which element will be scheduled based on the internal IDs of the tied elements.
At the time an element is scheduled an overall score is calculated. It’s an average of all the individual, scaled priority scores. Note, however, that the overall score does not influence which element gets scheduled. It’s merely an additional reference point you might want to use later when editing the schedule.
Spread Goals control rotational patterns of songs, links and/or their attributes. As the name implies, a spread goal attempts to make sure the time between repeat plays of a song, link or attribute is equal to or greater than the turnover implicit in its natural demand. Song Linear, for example, is a spread goal that attempts to impose the turnover time between repeat plays of a song. Song Radial is a spread goal that attempts to impose as much separation as possible, across hours and days, between repeat plays of a song. By default the other Spread Goals combine linear and radial control, but you can separate them for more precise control. See the notes in the Advanced Features section on separating Linear and Radial Spread Elements to reveal the separate Goals. Double-clicking a Spread goal in the priority list will open the corresponding Balance window. The Cutoff columns in the Rotation Rules window can be used with the Spread Goals to cutoff the spread goal to allow a song or link to score 100 sooner.
If Vocalist separation is more important to you than Artist separation and it should be if you have properly coded your songs with Vocalists, remove Artist Spread from your priority list and add Vocalist Spread. This will change tests and displays in the Scheduler and Editor from Artist to Vocalist. Instead of seeing Artist Previous and Artist Next in the Editor’s Test Bar, for example, you will see Vocalist Previous and Vocalist Next after making this highly recommended change.
Bans are created in the Goals | Bans | Segue, Time or BPM windows. Segue Bans control sequences of up to six songs using defined Attribute and Participant code settings. Time Bans, work like a Segue Ban in terms of Twofer, Across Stopset & Hour Restriction, except there's a Time Window separation. A Time Ban can also separate one attribute value from a different attribute value. BPM bans allow the user to setup a range restriction based on the Beats per Minute of the Song or Link. Bans can be set to Breakable or Unbreakable. Bans are simple pass / fail rules and are scored at 100 for a pass and 60 for a fail. By default like bans will be displayed in the Priorities tab as one Ban, but can you can separate them for more precise control. To reveal each Ban, hover the mouse over the location of the ban or check the Separate Ban Priorities checkbox in the Setup | Station | Features | Advanced window. Double-clicking a Ban in the priority list will open the corresponding Segue Bans, Time Bans or BPM Bans window.
Along with the Fixed Goals the following Goals can also be added to the Priority List.
The Airplay Starvation goal provides special scheduling attention to songs in a category that have not played for some time. This goal uses the Maximum Airplay Starvation Turnover Percentage set in the Setup | Station | Features | Advanced tab to determine at what point to schedule the song or link. When the song or link reaches the Maximum Airplay Starvation Turnover Percentage all other goals are ignored and the song or link is scheduled. The Airplay Starvation Goal cannot be added to the same Priority List as the Maximum Separation or Maximum Skip Legacy Rules. Double-clicking this goal in the priority list will take the user to the Setup | Station | Features | Advanced tab.
Use this Goal to activate or deactivate the GSelector Daypart Rotation Goal. When enabled, it works automatically to rotate elements through the different hours in a Daypart. Note that you can apply much more specific settings in the Hour Rotation Rule, and you can use both this Goal and the Rotation Rule if you wish.
Check this box in the Add Goal window to work with the Timing Goal and Exact Time Markers in Clocks. Categories assigned the Timing Goal are used to fill the schedule to meet timing goals between Reset Exact time Markers. Implementing Timing disables Search Depth and Stacking for that Category Group.
NOTE: Implementing Timing for a Category Group disables the ability to implement Kick for the same Category Group, and vice versa. In general, Kick is used for small rapid turnover Categories or Category Groups with high Importance, while Timing is used for larger, slower turnover Category Groups at or near the bottom of the Pass Order.
In addition to the Spread Goals, Segue Bans and Goals accessible from this window, you can also use Legacy Rules. Legacy Rules consist of Rotation Rules and Content Rules, these are detailed in the Rotation Rules and Content Rules topics. Rotation rules work with the Goals implemented in this window. Most Rotation Rules can be set to Breakable or Unbreakable. When you set a Rotation Rule as Unbreakable, GSelector will leave a position unscheduled if all songs available for scheduling violate the Priority. When you set a Rotation Rule as Breakable, GSelector will compromise a lower breakable priority if doing so will protect one or more higher priorities. These Rules can also be separated by attribute using the Allow Attribute Specific Legacy Rule Priorities option in the Setup | Station | Features | Advanced tab.
NOTE: Maximum Separation and Maximum Skip cannot be set to Unbreakable.
Legacy Rules you define in this window are as follows:
Daypart Rotation
This rule controls how many Dayparts a Song, Link, Artist, Song Group, or a Song or Link Attribute or Participant must be scheduled in before that element can be scheduled again in the original Daypart. For more details see the Daypart rule notes in the Rotation Rules topic. Daypart Rotation is a simple pass / fail rule and is scored at 100 for a pass and 60 for a fail. Double-clicking this rule in the priority list will open the Rotation Rules window.
The Days Out of Daypart rule protects against the song or link from being scheduled again in the same Daypart. This rule is covered by “Closest (Daypart)” in the Editor testbar.
The Days Out of Hour rule protects against the song or link from being scheduled again in the same Hour. This rule is covered by “Closest (Hour)” in the Editor testbar.
The DMCA Rule can be added in Goals | Priorities to identify and prevent the scheduling of songs that do not meet the following Digital Millennium Copyright Act (DMCA) performance complement rules:
|
(13) |
The “sound recording performance complement” is the transmission during any 3-hour period, on a particular channel used by a transmitting entity, of no more than— |
||
|
|
(A) |
3 different selections of sound recordings from any one phonorecord lawfully distributed for public performance or sale in the United States, if no more than 2 such selections are transmitted consecutively; or |
|
|
|
(B) |
4 different selections of sound recordings— |
|
|
|
|
(i) |
by the same featured recording artist; or |
|
|
|
(ii) |
from any set or compilation of phonorecords lawfully distributed together as a unit for public performance or sale in the United States, |
|
|
|
|
if no more than three such selections are transmitted consecutively: Provided , That the transmission of selections in excess of the numerical limits provided for in clauses (A) and (B) from multiple phonorecords shall nonetheless qualify as a sound recording performance complement if the programming of the multiple phonorecords was not willfully intended to avoid the numerical limitations prescribed in such clauses. |
|
Reference: 17 U.S. Code § 114 - Scope of exclusive rights in sound recordings; https://www.law.cornell.edu/uscode/text/17/114 |
The DMCA rule will achieve the following:
The DMCA Parameters in the Advanced tab of the Setup | Station | Features window can be used to adjust how the DMCA Rule detects violations.
Important Note |
Slotted songs are not tested in the Scheduler for any rules including DMCA. This also applies to browse list clock requests. All other song clock requests will be tested for DMCA in the Scheduler. However, songs scheduled from slotted categories and browse lists WILL be tested for DMCA in the Editor. So if you retest the position, run Retest Day or the Hotspot Filter, GSelector will catch any DMCA violations. In addition there are two other Scheduling instances that do not get tested:
|
Drive Protection prevents assets from being scheduled in other parts of the same day or in an adjacent day. For example, a person working 9-5 drives to work at 8AM and returns home at 5PM. Drive protection can protect the 5PM hour from playing a song that played during the 8AM hour. Drive Protection can also prevent the person hearing a song at 5PM yesterday from hearing it again at 8AM today. To setup Drive Protection rules use the Drive Protection tab in the Setup | Hours tab. Double-clicking this rule in the priority list will open the Setup | Hours | Drive Protection window.
Prioritizes the enforcement of Hour Restrictions applied to songs or links. Double-clicking this rule in the priority list will open the Setup | Hours | Hours Grids window.
This rule controls how many Hours a Song, Link, Artist, Song Group, or a Song or Link Attribute or Participant, must be scheduled in a Daypart before that element can be scheduled again in the hour of the Daypart in which it was originally scheduled. For more details see the Hour Rule notes in the Rotation Rules topic. Hour Rotation is a simple pass / fail rule and is scored at 100 for a pass and 60 for a fail. Double-clicking this rule in the priority list will open the Rotation Rules window.
Note: You can also implement the automatic Hour Rotation Goal, and the two can work in tandem.
Prioritizes the enforcement of the Maximum per Hour settings defined in the various Goals | Balance windows. Double-clicking this rule in the priority list will open the corresponding Balance window.
This Legacy Rule provides special scheduling attention to songs in a category that have not repeated within a specified time period. Think of Maximum Separation as the opposite of Minimum Separation. How much time can pass before it has been "too long" since a song in a category has played? The time period between repeat plays is set in the Rotation Rules window. Double-clicking this rule in the priority list will open the Rotation Rules window. Maximum Separation is a Breakable rule and cannot be set to Unbreakable.
This rule is similar to the Maximum Separation rule except it looks at the number of times a Song or Link has been skipped instead or the time of separation. The count between repeat plays is set in the Rotation Rules window. Double-clicking this rule in the priority list will open the Rotation Rules window.
This Rule allows the user to set a Minimum Time period to apply before a Song, Link, Artist, Song Group, or a Song or Link Attribute or Participant can be scheduled again. For more details, see the Minimum Separation Rule notes in the Rotation Rules topic. Minimum Separation is a simple pass / fail rule and is scored at 100 for a pass and 60 for a fail. Double-clicking this rule in the priority list will open the Rotation Rules or corresponding Balance window.
Prioritizes the enforcement of settings made in the Setup | Dayparts | No Repeat window. Double-clicking this rule in the priority list will open the Setup | Dayparts | No Repeat window.
This rule, like the Prior Day rule, can be used to apply time protection for up to eight days but it is not tied to a specific day or week. It also can be used to collapse the protection period if needed, working in the Station - Past Day window. The Rule controls how much a Song, Link, Artist, Song Group, or an Attribute or Participant for a Song or Link, must be separated from where that element was scheduled on a Past Prior Day. The rule can be applied in the future as well as in the past. For more details see the Past Day notes in the Rotation Rules topic. Double-clicking this rule in the priority list will open the Rotation Rules window.
This rule controls how much a Song, Link, Artist, Song Group, or a Song or Link Attribute or Participant, must be separated from one or more last play times of that element. The time period defined is the Play Window, and it is designed to work across Dayparts to allow effective protection across Daypart boundaries. For more details see the Play Window Rule notes in the Rotation Rules topic. Double-clicking this rule in the priority list will open the Rotation Rules window.
This rule allows you to apply time protection for up to a week. The Rule controls how much a Song, Link, Artist, Song Group, or a Song or Link Attribute or Participant, must be separated from where that element was scheduled on a defined Prior Day. The rule can be applied in the future as well as in the past. For more details see the Prior Day Rule notes in the Rotation Rules topic. The Prior Day rules are simple pass / fail mechanisms and are scored at 100 for a pass and 60 for a fail. Double-clicking this rule in the priority list will open the Rotation Rules window.
Used to provide protection for Songs, Links, Artists, Song Groups, or Song or Link Attributes or Participants that schedule several times in a Day, this rule controls how much that element must be separated from where it played Yesterday, irrespective of any other plays that day. The rule can be applied in the future as well as in the past. For more details see the Yesterday Rule notes in the Rotation Rules topic. The Yesterday rules are simple pass / fail mechanisms and are scored at 100 for a pass and 60 for a fail. Double-clicking this rule in the priority list will open the Rotation Rules window.
The Allow Attribute Specific Legacy Rule Priorities option will separate the Legacy Rules by Attribute in the Goals | Priorities window. If the primary Rule is used, it enables the rule for all attributes, however if a separate rule is used for a specific attribute then the rule only focuses on songs/links with that attribute. If Minimum Separation is in Goals | Priorities list, it works as before (pre 4.3.2) and enables MinSep for all attributes. If Minimum Separation Artist is in Goals | Priorities and Minimum Separation is not on the list, then songs will only get MinSep for artists. If both are in Goals | Priorities, then Minimum Separation Artist can be at one priority and Minimum Separation (covering all other attributes) can be at another making this a very powerful tool. This option is enabled in the Setup | Station | Features | Advanced tab.
The Link Protection column is used to protect songs against links for Spread Goals, Minimum Separation and BPM Bans. This option will protect against songs and links with like attributes from being scheduled next to each other. When a check box in the column is set, attribute values are spread between the element types. For example, if Link Protection is checked for Sound Code Spread in the song Priority List, when scheduling songs GSelector will spread Sound Code attributes across both songs and links. There are Link Protection and Song Protection check boxes for Minimum Separation. These apply to those attributes which are common between songs and links such as Energy or Genre. There are Link Protection and Song Protection check boxes for BPM Bans. These apply to the BPM Overall and BPM Transition attributes which are common between songs and links. The BPM Ban will be applied against the previous/next scheduled or unscheduled position of either song only or song/link for songs and either link only or song/link for links. If there's a stopset (link, breaknote, spotset or spot block) in between the previous/next protected position, then the Ban Across Stopset setting determines whether GSelector will stop looking when the stopset is hit.
The Across Regions column is used to respect or ignore Daypart Regions. When a checkbox in this column is set, the associated goal or rule will consider plays in any region. When a checkbox in the column is cleared, the associated goal or rule will ignore plays in all regions except the region being scheduled.
This feature provides precise control over the scoring of Legacy Rules failures in GSelector. Previously if a Legacy Rule was declared Unbreakable, all failures of the rule would score 0. When this feature is enabled the priority list will have a new “middle ground” known as ‘Fixed’ where a score can be specified for rule failures. To enable this feature, select the User Defined Priority Scoring option in the Station | Features | Advanced tab. When the User Defined Priority Scoring is enabled a new Value column in the right pane is shown. This column shows the Fixed Failure value when a goal is set as Fixed. Legacy Rules and Segue Bans can be set as Fixed when added or by right-clicking the goal field and selecting Fixed. The selected rule will appear in the Fixed portion of the priority list, between Unbreakable and Breakable. Use the arrow buttons in the Value column to adjust the Failure value. When the Value is adjusted the graphical representation in the Goal Importance column will also change. If current scheduling includes a heavy dose of Legacy Rules set to Unbreakable, this enhancement offers a mechanism to create less unscheduled positions or to widen the pool of available songs when there are multiple Legacy Rule failures.
The default Priority List contributes to scoring in the sense that users specify one priority as being more important than others. However, this accounts for ranking only. The Weight Scoring allows the user to declare, by percentage, the relative importance of the goals. The Weight of the goal can be used to tell the system that Song Linear is much more important than Vocalist Spread. The Weight column is displayed when the User Defined Priority Scoring option in the Station | Features | Advanced tab is enabled. This column replaces the Priority ranking column and allows the user to adjust the rank or the goal using a percentage scoring value. Only Breakable goals can be given a weight score. Use the arrow buttons in the Weight column to adjust the score. When the weight is adjusted the graphical representation in the Goal Importance column will also change.
Copy Priority List to Other Stations
Adding Priorities to a Priority List
Setting Breakable and Unbreakable Priorities
Sharing equal priorities - Tied Goals
Specifying Vocalist instead of Artist Spread
Separate Linear and Radial Goals
Allow Removal of Fixed Priorities
Implementing Timing Goal Scheduling
See also the notes for the Segue Ban window.
To edit the Priority List, click the Edit button or double-click the desired list. Using the following illustrated window the user can change the name, select Reverse Schedule and optionally enable the Content Rule.
Select the Priority List to delete. Click the Delete Priority List button. The deleted Goals in the Priority List are deleted from assigned Dayparts and Categories of that Priority List.
Click the Cancel button to return the window to its last saved state.
To Copy an existing Priority List, select the list to copy and click the Copy button. The following Copy Priority window will open to enter a name, optionally select Reverse Schedule and optionally enable the Content Rule.
Note: If the user specifies an existing name when copying a priority list, the user will be prompt to overwrite the existing list.
The 'Copy Priority to Other Stations' toolbar button will open the Copy Priority Lists window. The Copy Priority Lists window allows the user to copy selected priority lists to others stations in the same database.
The window has three panes. The pane on the left can be used to select one or more existing Priority Lists for the current station. The middle pane is used to select the Station(s) to copy the selected list to. The right pane is used to select the Priority Types from the selected Priority Lists that are to be copied to the selected stations. The Select All check boxes across the top of the window can be used to select all the options in the corresponding pane. Click the Copy button after making the selections. If a priority list already exists on the target station the user will receive a warning that the list will be overwritten.
Note: For Segue Ban priority type, if there's "Hour Restrictions" defined, it will be respected. In addition if a "Category" type segue ban exists in the source station, the category will be cross checked for existence on the target station. If the category does not exist, GSelector will prompt the user with a warning. If the user decides to proceed with the copy, the missing categories (segue bans) will not be copied.
A Priority can be added to a Priority List using the green Add Priority button. Click the button to view a menu of Priority Types such as Spread, Segue Ban, Legacy Rule or Goal. Each type will list the Priorities available in that group. Optionally, select All to view a list of all the priorities available.
Select the Priority to delete from the desired Priority List. Click the Delete Priority button. You cannot delete the fixed Song Linear, Song Radial, and Daypart Goals without first removing the Fixed status. A deleted Goal is deleted from assigned Dayparts and Categories for the Priority List.
The Segue Ban and Legacy Rules can be set as Breakable or Unbreakable. You can set this status by simply dragging the desired goal to the Unbreakable or Breakable section of the Priorities pane, right clicking and selecting the Unbreakable or Breakable or by selecting the Unbreakable checkbox when Adding the Priority.
The Goal List in the Priorities pane displays the Priority rank of the selected goals. Place the most important Goal at the top, and the next most important Goals beneath, sorting all the Goals in order of importance, down to the least important Goal. GSelector works intelligently with the list of Gaols to generate the best scheduling results. If the User Defined Priority Scoring option in the Station | Features | Advanced tab is enabled the rank arrows in the toolbar are hidden and the rank column is replace with a Weight and Goal Importance column.
To rank Goals by priority:
When a Goal is added from the Add Priority window, it is added to the position immediately above the cursor. Use the re-order buttons to move it up or down in the list or click and drag the goal to a new place in the Priority pane. To edit a Priority list, simply select one or more Goals and move them as described above, and continue until the list is in the desired order. The color bands in the pane show the sequence of Goals in the list, but they can also serve to show tied Goals, or Goals of equal priority. To see how color bands work with tied Goals, see the illustration above.
When the User Defined Priority Scoring option in the Station | Features | Advanced tab is enabled the Legacy Rules and Segue Bans can be set as Fixed with a Fixed Failure Value.
When the User Defined Priority Scoring option in the Station | Features | Advanced tab is enabled the rank arrows in the toolbar are hidden and the rank column is replace with a Weight and Goal Importance column.
To rank Goals using a Weight Score:
If the User Defined Priority Scoring option in the Station | Features | Advanced tab is enabled the untie option is not visible.
To tie Goals together:
In this illustration, Daypart and Clock Goal have been tied together. This means they will be treated as having equal importance. All tied Goals share the same color band to indicate that they share equal priority. To untie tied Goals, right-click the goal again and select the untie option.
Click the Threshold toolbar button to access the Scheduling Score Threshold and the Attribute Fallback Score Threshold for Songs.
A Fallback attribute is an attribute that GSelector can fallback to if the normal attribute scores too low to be scheduled.
For Example: A Song is normally genre “Dance” but could be treated as genre “Crossover” in a scheduling pinch because of the fallback attribute. Attribute Fallback Score Threshold is set to 65. The Scheduler will treat the song as “Dance” unless the song scores below 65, then it will treat the song as “Crossover” and test it again.
Fallback Attributes can be defined in the Attributes tab of the Setup | Station | Features window.
This button allows you to access the Rotation Rules window where you can enter settings for any of the Rotation Rules which have been added to a Priority List in the this definition window.
GSelector's default install mode provides for key Goals to be fixed in Song and Link Priority lists, and combines Radial and Linear spread elements into the Artist or Vocalist Spread Goals. These settings can be modified if required.
Separate Linear and Radial Goals
Combine Linear and Radial goals back into Spread Goals
Remove Fixed status from Goals in the Priority list
See also Specifying Vocalist instead of Artist Spread
Spread Goals have two primary components. Linear Spread affects positions in the same day, working across the day. Radial Spread affects positions close to the current position, working across several days. In GSelector's default mode, these two components are combined for all Goals apart from Song Linear and Song Radial. However, these goals can be separated, and then rank them individually to suit programming needs.
To separate Linear and Radial spread Goals:
To recombine all Linear and Radial Spread Goals back into Spread Goals, access the Setup Station Features window, and uncheck the Separate Linear and Radial Spread Goals Checkbox in the Advanced section of the window. This will affect Song and Link Goals
The Priorities window, in default install mode, provides six Fixed Goals. Fixed Goals cannot be removed from the Priorities list, although they can be ordered to suit your requirements. To remove this setting:
To restore Fixed Goal status in the Priority windows, access the Setup Station Features window, and deselect the Remove Fixed Priorities box in the Advanced section of the window. Any Goals that have been deleted from the Priority list are restored according to default settings. This will affect Song and Link Goals.