http://wiki.rivendellaudio.org/index.php?title=Managing_Scheduler_Rules&feed=atom&action=historyManaging Scheduler Rules - Revision history2024-03-29T10:15:53ZRevision history for this page on the wikiMediaWiki 1.26.4http://wiki.rivendellaudio.org/index.php?title=Managing_Scheduler_Rules&diff=101&oldid=prevHiggles: Created page with "The scheduler selects *exactly one* cart per event from the given group. So you are able to set up different categories using different groups like ROT_A, ROT_B, RECURRENT, GO..."2018-03-12T15:51:06Z<p>Created page with "The scheduler selects *exactly one* cart per event from the given group. So you are able to set up different categories using different groups like ROT_A, ROT_B, RECURRENT, GO..."</p>
<p><b>New page</b></p><div>The scheduler selects *exactly one* cart per event from the given<br />
group. So you are able to set up different categories using different<br />
groups like ROT_A, ROT_B, RECURRENT, GOLD and make different events<br />
based on these categories.<br />
<br />
You can control the selection process with these options:<br />
<br />
* Title Separation (in event dialog): Minimum number of Songs to be<br />
scheduled before a Cart can be scheduled again<br />
Please Note: For fast rotating groups with only a few songs you need a<br />
short Title Separation or it will have no effect because the rule will<br />
be broken to often.<br />
<br />
* Artist Separation (in Clocks->Scheduler Rules): Minimum Number of<br />
songs before a artist can be scheduled again.<br />
<br />
* "Scheduler Codes" make things available like tempo control, gender<br />
control, genre separation or daypart restrictions.<br />
<br />
I will try to explain this concept with some screenshots.<br />
<br />
In rdadmin there is a button "Scheduler Codes". Here you can define<br />
Codes like "Tempo-Low", Tempo-Mid", Tempo-High", or "Rock" and<br />
"Country", or whatever you need.<br />
<br />
<br />
Alway remember : <br />
<br />
<br />
for a song, the SCHEDULER CODE depends of the song, <br />
for example, Tempo-Mid will never be Tempo-High<br />
<br />
a GROUP is HOW you PLAY the song,<br />
for example, a ROT-A can be a ROT-B, etc.<br />
<br />
<br />
In rdlibrary you can assign codes to each cart.<br />
<br />
<br />
In rdlogmanager/clocks you can define rules how to handle carts that<br />
have assigned certain codes. For example you can say: Play max. two<br />
carts with "Tempo-Low" in a row or wait at least three songs between two<br />
carts with "Rock". Also, you can say: Do not schedule a song with<br />
"Tempo-High" after one with "Tempo-Low".<br />
<br />
<br />
When you set "Max. in a row" to 0, a cart with that code is not selected.<br />
When "Max. in a row" is at least 1 and "Min. wait" is 0, carts with that<br />
code can be scheduled in a row unlimited times. This makes something<br />
like dayparting possible. Let's say you have a code "no_mornings": Then<br />
you set "Max. in a row" for "no_mornings" to 0 in the clocks you use in<br />
the morning hours and "Max. in a row" to 1 and "Min. wait" to 0 in all other<br />
clocks.<br />
<br />
You can copy rulesets from one clock to another using the import button<br />
in the "Scheduler Rules" dialog.<br />
<br />
In RDLogmanager/Events you can select, from with Group a song should be<br />
taken. Also you can define a code, a cart must have to be selectable.<br />
One example: You have a code called "opener". You create an event for<br />
the "Opener"-positions in your clocks. Only carts with an "opener" code<br />
assigned should be selectable for this event.<br />
<br />
<br />
The scheduler will select a cart when there is at least one in the group<br />
- even if he had to break one or more rules. When he has to break a<br />
rule, the scheduler will print a note to the report displayed after<br />
log generation in rdlogmanager.<br />
<br />
Integration with Rivendells concept or Services: There is a<br />
scheduling history (virtual stack of carts) for each service<br />
<br />
Still on my ToDo-List is a related artist feature and horizontal<br />
separation (to make sure a song is not played at the same time the<br />
next day).<br />
<br />
However, you could use scheduler codes for related artists separation:<br />
Make a code "related" and set them to "max in a row" 1 and "min. wait"<br />
e.g. 5, so all carts with this label will be separated. If you use the<br />
"related" label for Rolling Stones, Mick Jagger, Beatles and Paul<br />
McCartney, Stones and Beatles or Jagger and McCartney will also be<br />
separated. "To avoid this you would have to use different codes<br />
"rel_beatles" and "rel_stones", but could be much work).</div>Higgles