On 03/12/2015 05:50 AM, Chuck wrote:
the scheduler
occasionally puts in a song up to, or more than, 7 minutes long in those
2 minute slots (a 10:13 event appeared there yesterday).
The scheduler does not consider time, especially not the time you
allocate in the clock, for a very good reason. Not all songs are created
equal.
There are a number of ways to distinguish long[ger than(say)3:30] songs.
Stick them in a GROUP of their own that only schedules in the sweep from
:20 to :40
Give them a scheduler code like "Long Song" and either use the EVENT
selector or the CLOCK Scheduler Rules to discriminate them.
You may have to create a dummy event like No Long Song Here which goes
in the clock in the last 10 minutes between other events to make the
scheduler rule workable. Bit of keying but once it's done it's done.
We used RD Library to locate all the long tracks and placed them in an
archive so they can be manually selected as appropriate. If you play a
long song that someone does not like, that someone will tune out, game
over. Same song can be played in a pre announced specialist [Rock Jazz
Disco] programme without losing the listener because they get told the
next hour is going to be stuff they don't like and while they may tune
out, they know they can come back.
We have a presenter in New Zealand on a national network who generates
such a massive switch off the power co can ease off generation and
stockpile water. They are still #1 most other times of day.
Rivendell is a computer program not artificial intelligence. The
thinking needs to be done by whoever is setting it up, who then issues
instructions.
regards
Robert
--
Robert Jeffares
Communication Consultants
Broadcast Engineering and Programming.
Big valley Radio
The Wireless Station
0221693124
+6498176358
_______________________________________________
Rivendell-dev mailing list
[email protected]
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
