Re: [RDD] Chain To Woes
While it is true that the chain-to event is a timed event, in some way or other all events are, it is not a hard timed event unless you make it so. From: Benjamin D. Fillmore benja...@fillmoretechnical.com To: User discussion about the Rivendell Radio Automation System rivendell-dev@lists.rivendellaudio.org Sent: Friday, October 21, 2011 11:50 PM Subject: Re: [RDD] Chain To Woes Rob, the issue is that when you select the checkbox to add the Chain-To event at the end of your logs, it creates the Chain-To as a Timed Event. So if it fires before midnight, then the next day's log loads (which also has a Timed Event at midnight to load the NEXT day's log) and it gets triggered when midnight actually hits. Effectively skipping a day's log. Adding manually pasting some extra music into the last hour can avoid this. And I imagine it's possible to make a special clock for the 11pm hour that has a chain-to event that is NOT a timed event. I think that's what I'll end up having to do -- because I don't see any way to make the system generated one anything but a timed event. On 10/19/2011 8:40 AM, Tim Camp wrote: It may put your time off a little if you are running early but just chain the next day at the end of your log. No timed event. On Oct 19, 2011 7:01 AM, James Gamblin jgamb...@lwrn.org wrote: Hey Rob, Ours did it last night. We usually add a few songs at the end of the day, for insurance. The fellow that usually takes care of that had a couple of days off. Most were fine, but we got bit last night. Woke up @ 4 am to a silent station. Sure wish the next day would just load. James On Wed, Oct 19, 2011 at 6:52 AM, Rob Landry 41001...@interpring.com wrote: I've never seen this happen. My clients' stations often run out of log before midnight; the next day's log loads a bit early but plays just fine. I usually have a long filler scheduled just before 3 AM with a station ID after it that is set to start at 3AM, so a couple minutes of the filler may play and then the ID starts precisely at 3. Do you have a timed event scheduled for just before midnight? In stations using a Windows-based automation system I've seen people schedule a timed event leading into an 11:56 PM stopset, and if the day's log starts before midnight, the machine would skip to the 11:56 stopset at the end of the log. But if Rivendell did this, I should be seeing my 3AM IDs running at midnight every night. Rob On Wed, 19 Oct 2011, Benjamin D. Fillmore wrote: We are experiencing a random but recurring problem. Sometimes the chain-to event will happen slightly before midnight. The problem is that when this happens, the next log loads, and then at midnight, the log forces the NEXT chain-to event to trigger which either puts us on the wrong day's log, or halts the system (if there isn't a log for the next day in the system yet). It happens multiple times a week. We are having to log in to the system remotely after midnight EVERY day just to make sure the station is still on-air. Obviously, not the ideal situation. I believe there must be a reliable fix, or else this system would not be so widely used. Looking forward to for an answer to this dilemma Thank you! ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
Re: [RDD] Chain To Woes
When have a timed event always at the end of the log to make sure that that does not occur. So make sure the log is full or over and the last event is a timed event and has a Stop transition to it (before the chain) and only start when you want it to change over. Hope this helps Stan On 19/10/11 3:47 PM, Benjamin D. Fillmore wrote: We are experiencing a random but recurring problem. Sometimes the chain-to event will happen slightly before midnight. The problem is that when this happens, the next log loads, and then at midnight, the log forces the NEXT chain-to event to trigger which either puts us on the wrong day's log, or halts the system (if there isn't a log for the next day in the system yet). It happens multiple times a week. We are having to log in to the system remotely after midnight EVERY day just to make sure the station is still on-air. Obviously, not the ideal situation. I believe there must be a reliable fix, or else this system would not be so widely used. Looking forward to for an answer to this dilemma Thank you! ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
Re: [RDD] Chain To Woes
Yes it will, but it's there as a precaution. As log as you have enough events/music before hand then that timed event (can be a music track) will start say at 11:59 even though you have enough music to take you up to say 00:10 the next day. On 19/10/11 4:04 PM, Benjamin D. Fillmore wrote: I'm not sure if I followed that, but I'll take a look tomorrow, when the internet is back up (I can't reach the machine right now). Won't STOP actually stop the automation, preventing the chain event from ever firing, without user intervention? On 10/19/2011 2:56 AM, Stan Fotinos wrote: When have a timed event always at the end of the log to make sure that that does not occur. So make sure the log is full or over and the last event is a timed event and has a Stop transition to it (before the chain) and only start when you want it to change over. Hope this helps Stan On 19/10/11 3:47 PM, Benjamin D. Fillmore wrote: We are experiencing a random but recurring problem. Sometimes the chain-to event will happen slightly before midnight. The problem is that when this happens, the next log loads, and then at midnight, the log forces the NEXT chain-to event to trigger which either puts us on the wrong day's log, or halts the system (if there isn't a log for the next day in the system yet). It happens multiple times a week. We are having to log in to the system remotely after midnight EVERY day just to make sure the station is still on-air. Obviously, not the ideal situation. I believe there must be a reliable fix, or else this system would not be so widely used. Looking forward to for an answer to this dilemma Thank you! ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
Re: [RDD] Chain To Woes
No, just set up extra events using RDlogmanager music scheduler On 19/10/11 4:36 PM, Benjamin D. Fillmore wrote: So it's still coming back to manually inserting music after the merge process dumps the music we already overscheduled. Okay. On 10/19/2011 3:17 AM, Stan Fotinos wrote: Then I would add events into RDlogmanager to prevent that. On 19/10/11 4:13 PM, Benjamin D. Fillmore wrote: Then it would leave the same situation. If there's not an overfill in that hour, then the automation ends. The music IS overscheduled, but the import dumps everything that it decides won't fit in the clock -- which eliminates the overscheduled music. Leaving us back with a log that may or may not end early, and stop automation at midnight. On 10/19/2011 3:09 AM, Stan Fotinos wrote: Yes it will, but it's there as a precaution. As log as you have enough events/music before hand then that timed event (can be a music track) will start say at 11:59 even though you have enough music to take you up to say 00:10 the next day. On 19/10/11 4:04 PM, Benjamin D. Fillmore wrote: I'm not sure if I followed that, but I'll take a look tomorrow, when the internet is back up (I can't reach the machine right now). Won't STOP actually stop the automation, preventing the chain event from ever firing, without user intervention? On 10/19/2011 2:56 AM, Stan Fotinos wrote: When have a timed event always at the end of the log to make sure that that does not occur. So make sure the log is full or over and the last event is a timed event and has a Stop transition to it (before the chain) and only start when you want it to change over. Hope this helps Stan On 19/10/11 3:47 PM, Benjamin D. Fillmore wrote: We are experiencing a random but recurring problem. Sometimes the chain-to event will happen slightly before midnight. The problem is that when this happens, the next log loads, and then at midnight, the log forces the NEXT chain-to event to trigger which either puts us on the wrong day's log, or halts the system (if there isn't a log for the next day in the system yet). It happens multiple times a week. We are having to log in to the system remotely after midnight EVERY day just to make sure the station is still on-air. Obviously, not the ideal situation. I believe there must be a reliable fix, or else this system would not be so widely used. Looking forward to for an answer to this dilemma Thank you! ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
Re: [RDD] Chain To Woes
Hey Rob, Ours did it last night. We usually add a few songs at the end of the day, for insurance. The fellow that usually takes care of that had a couple of days off. Most were fine, but we got bit last night. Woke up @ 4 am to a silent station. Sure wish the next day would just load. James On Wed, Oct 19, 2011 at 6:52 AM, Rob Landry 41001...@interpring.com wrote: I've never seen this happen. My clients' stations often run out of log before midnight; the next day's log loads a bit early but plays just fine. I usually have a long filler scheduled just before 3 AM with a station ID after it that is set to start at 3AM, so a couple minutes of the filler may play and then the ID starts precisely at 3. Do you have a timed event scheduled for just before midnight? In stations using a Windows-based automation system I've seen people schedule a timed event leading into an 11:56 PM stopset, and if the day's log starts before midnight, the machine would skip to the 11:56 stopset at the end of the log. But if Rivendell did this, I should be seeing my 3AM IDs running at midnight every night. Rob On Wed, 19 Oct 2011, Benjamin D. Fillmore wrote: We are experiencing a random but recurring problem. Sometimes the chain-to event will happen slightly before midnight. The problem is that when this happens, the next log loads, and then at midnight, the log forces the NEXT chain-to event to trigger which either puts us on the wrong day's log, or halts the system (if there isn't a log for the next day in the system yet). It happens multiple times a week. We are having to log in to the system remotely after midnight EVERY day just to make sure the station is still on-air. Obviously, not the ideal situation. I believe there must be a reliable fix, or else this system would not be so widely used. Looking forward to for an answer to this dilemma Thank you! ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
Re: [RDD] Chain To Woes
It may put your time off a little if you are running early but just chain the next day at the end of your log. No timed event. On Oct 19, 2011 7:01 AM, James Gamblin jgamb...@lwrn.org wrote: Hey Rob, Ours did it last night. We usually add a few songs at the end of the day, for insurance. The fellow that usually takes care of that had a couple of days off. Most were fine, but we got bit last night. Woke up @ 4 am to a silent station. Sure wish the next day would just load. James On Wed, Oct 19, 2011 at 6:52 AM, Rob Landry 41001...@interpring.comwrote: I've never seen this happen. My clients' stations often run out of log before midnight; the next day's log loads a bit early but plays just fine. I usually have a long filler scheduled just before 3 AM with a station ID after it that is set to start at 3AM, so a couple minutes of the filler may play and then the ID starts precisely at 3. Do you have a timed event scheduled for just before midnight? In stations using a Windows-based automation system I've seen people schedule a timed event leading into an 11:56 PM stopset, and if the day's log starts before midnight, the machine would skip to the 11:56 stopset at the end of the log. But if Rivendell did this, I should be seeing my 3AM IDs running at midnight every night. Rob On Wed, 19 Oct 2011, Benjamin D. Fillmore wrote: We are experiencing a random but recurring problem. Sometimes the chain-to event will happen slightly before midnight. The problem is that when this happens, the next log loads, and then at midnight, the log forces the NEXT chain-to event to trigger which either puts us on the wrong day's log, or halts the system (if there isn't a log for the next day in the system yet). It happens multiple times a week. We are having to log in to the system remotely after midnight EVERY day just to make sure the station is still on-air. Obviously, not the ideal situation. I believe there must be a reliable fix, or else this system would not be so widely used. Looking forward to for an answer to this dilemma Thank you! ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
Re: [RDD] Chain To Woes
When you say the import does that mean you are using an external scheduler instead of Rivendell's own scheduler? If that is the case, then your rivendell clocks should match your external scheduler clocks and nothing will get dumped during the import. From: Benjamin D. Fillmore benja...@fillmoretechnical.com To: rivendell-dev@lists.rivendellaudio.org Sent: Wednesday, October 19, 2011 1:13 AM Subject: Re: [RDD] Chain To Woes The music IS overscheduled, but the import dumps everything that it decides won't fit in the clock -- which eliminates the overscheduled music. Leaving us back with a log that may or may not end early, and stop automation at midnight.___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
Re: [RDD] Chain To Woes
It occurs to me that it would be nice if tomorrow's log were loaded by appending it to today's while today's is still running, the time of each event being adjusted by adding to it the projected end time of today's log. Midnight would become just another time, and not a seam separating today from tomorrow. Would not a seamless log forever banish the specter of confusion between 00:00:00 and 24:00:00? Rob ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
Re: [RDD] Chain To Woes
Although that sounds nice, and I do believe it can be done, I have loaded a new log while the current one is still on the playlist, but have not really checked on it because I have done it in error, so I just deleted the whole thing and started over. but somewhere, somehow, there has to be separation. How would you reconcile your logs if there is no separation? how would you play your hard timed events? From: Rob Landry 41001...@interpring.com To: User discussion about the Rivendell Radio Automation System rivendell-dev@lists.rivendellaudio.org Sent: Wednesday, October 19, 2011 10:37 AM Subject: Re: [RDD] Chain To Woes It occurs to me that it would be nice if tomorrow's log were loaded by appending it to today's while today's is still running, the time of each event being adjusted by adding to it the projected end time of today's log. Midnight would become just another time, and not a seam separating today from tomorrow. Would not a seamless log forever banish the specter of confusion between 00:00:00 and 24:00:00? Rob ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
Re: [RDD] Chain To Woes
Reconciliation would be a matter of reporting all events from 00:00:00 to 23:59:59 on a certain day and comparing them with the schedule from the traffic system. Currently if I load a main log whila another main log is running, the current event continues to play but all subsequent events are wiped out and replaced with those of the newly loaded log, starting at the beginning. The projected start times seem to be calculated from the end of the currently playing event, but those of timed events are not changed. My idea would be to append the newly loaded log to the current one, recalculating the start times from the end of the current log and recalculating the timed events by adding them to 24:00:00. I can see this breaking down, though, if someone wants to create a log for half of today and load it at noon. In that case, a timed event at 13:00:00 would still want to be 13:00:00 and not 1:00:00 the next day. Rob On Wed, 19 Oct 2011, Jorge Soto wrote: Although that sounds nice, and I do believe it can be done, I have loaded a new log while the current one is still on the playlist, but have not really checked on it because I have done it in error, so I just deleted the whole thing and started over. but somewhere, somehow, there has to be separation. How would you reconcile your logs if there is no separation? how would you play your hard timed events? From: Rob Landry 41001...@interpring.com To: User discussion about the Rivendell Radio Automation System rivendell-dev@lists.rivendellaudio.org Sent: Wednesday, October 19, 2011 10:37 AM Subject: Re: [RDD] Chain To Woes It occurs to me that it would be nice if tomorrow's log were loaded by appending it to today's while today's is still running, the time of each event being adjusted by adding to it the projected end time of today's log. Midnight would become just another time, and not a seam separating today from tomorrow. Would not a seamless log forever banish the specter of confusion between 00:00:00 and 24:00:00? Rob ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
