Under RDLogManager > Edit Events, I select the Timed Start function, then check the box for Action if Previous Event Still Playing > Make Next. This will jettison the over-scheduled music at the end of my hour and jump the log to the hard-timed event, BUT not fire it off until the song is done. As the last 12 minutes of my hour are populated with short songs, the worst I will do is be two minutes late with a legal ID. But I dont think people are setting their watches to my 0.1W signal.
As far as the system handling back-timing, I have not seen that as a feature. It is presumed there is some human interaction at some level and that said human can do a fair job of taking care of "filling the bucket", as it were. Just put in 10 or so more minutes of music than an hour needs, then put in a few "catch-up" markers in so the log evens itself out 3 or 4 times an hour by disposing of music it cant get to throughout the hour. Each hour of the log is then self-correcting. The hour may not end right on the tick of :59:59, but it's close enough for Bluegrass. AP ----- Original Message ----- From: "Andy Brown" <[email protected]> To: [email protected] Sent: Friday, October 25, 2013 10:10:23 AM Subject: Re: [RDD] Best option for playing legal ID at top of hour without unceremoniously cutting into a playing song On 22/10/13 00:57, Alan Peterson wrote: > What I do is overschedule a bunch of *short* songs (typically oldies) > instead of overly long ones inside the last 8 minutes of the hour, > and do a Timed Start-Wait at :58:00 where the subsequent event is the > Legal ID. I save the long tunes for the middle of the hour where > there is not so much of an urgency to hit a critical time, and the > Timed Start at or around :58 drops the overscheduled songs. Works OK > for me & my little clandestine basement station. Hi Alan, A brief question, as this is something I'm currently doing however I'm getting frequently a song starting then say 10-30 seconds later it being cut-off by the scheduled hourly event. Is there something you've come up with to solve that or is that something we have to bear with? Ideally, can the system not back-time? Since the system is in full automation, filling its hours itself, etc, surely the log generator could take that into account and 'accurately' fill the hour with songs that fit? Any thoughts? -- Andy e: andy @ thebmwz3.co.uk e: andy @ broadcast-tech.co.uk w: http://www.thebmwz3.co.uk w: http://www.broadcast-tech.co.uk _______________________________________________ Rivendell-dev mailing list [email protected] http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev _______________________________________________ Rivendell-dev mailing list [email protected] http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
