Hi Scott I had this very problem myself. this is how I solved it. Because the last event in the day is a generic... music in my case there was no hard (or soft) time associated it... it just flowed on from the previous event.... playing 3 or 4 songs after the the hour.... and also the next days clock starts with a hard or soft time... but of course because that clock doesn't load till after the event playing after midnight... it's time attributes are ignored.
What I did is made 2 new clocks. Before Midnight and after midnight. Before Midnight is different from a normal clock in that it's very last event is hard timed event that plays a station ID, 1 second before midnight (23:59:59). Once this Station ID is played .... it loads the next day's log (After Midnight)... which doesn't have a hard timed event at the start. I hope this helps. Many thanks Geoff Barkman On Thu, Sep 29, 2011 at 5:38 AM, <[email protected]> wrote: > > The shortened clock slots fixed our short hours and that seems to be > running great now. But now the last hour of the day is too long so > the chain to the next day doesn't happen until 3 or 4 songs into the > next day. I don't think we have to chain exactly at Midnight but we > can't figure out how to make it chain right after whatever song is > playing at Midnight. Can anyone tell us what we are missing this time? > > Thanks, > -Scott > > > Quoting [email protected]: > >> >> Yes, we were confused about that. Yesterday we changed all the slots >> so there aren't any over 5 minutes and today every hour has been filled. >> >> Thanks, >> -Scott >> >> >> Quoting Robert Orr <[email protected]>: >> >>> Not quite sure you understand how the internal scheduler fills slots. >>> If it sees a slot (pie slice), it puts a song of any length there. The >>> slot could be 10 seconds long. It would put one song of any length >>> there. The slot could be 35 minutes long... it would put one song of >>> any length there. It's merely the number of slots or pie slices that >>> determines how many songs will be placed per hour. If you want six >>> Bronze songs in the hour... put six Bronze pie slices of any length >>> in the hour. >>> >>> Have a great day, >>> Robert >>> >>> On Sat, Sep 24, 2011 at 10:28 PM, <[email protected]> wrote: >>>> >>>> Thanks for all of your replies! We eliminated all of the 5 minutes >>>> and longer slots in the Gold group and it seems to be much better today. >>>> >>>> I have been watching it closely and it has been within a couple of >>>> minutes almost every hour today. I have only seen one that was 5 >>>> minutes early. >>>> >>>> @Alan - we don't have to be exact, we feel that +/- 5 minutes will be >>>> close enough. The problem before was that it was often playing the >>>> top of the hour around 15 minutes early and we had a couple that were >>>> over 20 minutes early. >>>> >>>> Tomorrow we are going to eliminate the slots > 4 minutes in the >>>> OneHitWonder, Bronze, and Silver groups and I'm sure that will >>>> completely eliminate all the problems we had. >>>> >>>> Anyway, thanks again to everyone for all of your help! It sounds >>>> great! Rivendell is pretty amazing, we are planning to go live on Oct >>>> 1st. >>>> >>>> -Scott >>>> >>>> >>>> >>>> Quoting Alan Peterson <[email protected]>: >>>> >>>>> It's a minor note, but one that is not so jarring to the listener's >>>>> ear: Place your shortest tunes into the last 5-8 or so minutes of >>>>> the hour. This way, if your Hard Update event has to cut off a song, >>>>> it won't do so partway through a long-ish tune, which never sounds >>>>> good. >>>>> >>>>> (I've always thought a prime reason the Box Tops' song "The Letter" >>>>> was a hit - other than its catchiness - was because it was 1:50, >>>>> which helped the jock 'cheat' his way to the network news if his >>>>> hour fell short.) >>>>> >>>>> BTW, what is running on your station that calls for a mandatory >>>>> 00:00 hit? If it's hourly news, could you not employ Rivendell's >>>>> slip-time playback? This way a song can make it to the end and the >>>>> news is still intact, although several seconds late. >>>>> >>>>> -AP >>>>> >>>>> >>>>> [email protected] > wrote: >>>>> >>>>> You can have 20 three minute pie slices in the clock (if your songs >>>>> average over 3 minutes, that would mean your hour would have several >>>>> minutes more than it needs... in Matthew's case that works out to >>>>> 63-65 minutes of music per hour) and if you have a hard timed event >>>>> either make next or start immediately at 59:59 it would skip the >>>>> last several songs. >>>>> >>>>> >>>>> [email protected] > wrote: >>>>> >>>>> It is setup in the events to be hard timed to 59:56.6 to start >>>>> immediately even if the previous cart is still playing so that it >>>>> will fade out of the song to be ready for our legal id. It is also >>>>> setup with a Stop transition in case for some odd reason nothing was >>>>> playing that it would wait to the top of the hour to play the legal >>>>> id which is the next cart after this event. >>>>> >>>>> >>>>> _______________________________________________ >>>>> Rivendell-dev mailing list >>>>> [email protected] >>>>> http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev >>>>> >>>> >>>> >>>> _______________________________________________ >>>> Rivendell-dev mailing list >>>> [email protected] >>>> http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev >>>> >>> _______________________________________________ >>> Rivendell-dev mailing list >>> [email protected] >>> http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev >>> >> >> >> _______________________________________________ >> Rivendell-dev mailing list >> [email protected] >> http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev >> > > > _______________________________________________ > Rivendell-dev mailing list > [email protected] > http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev > _______________________________________________ Rivendell-dev mailing list [email protected] http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
