[RDD] RDAirplay: Refresh Log over Midnight
Hi, I'm running Rivendell 1.7.2 (packaged Ubuntu version), and have a strange problem: if I edit a log that's currently playing using RDLogEdit (in my tests I inserted one song shortly after the currently playing item) then refresh RDAirplay, any events that would end after midnight are deleted. This includes the Chain To that would conclude the log, which breaks playout at roughly midnight. A quick leaf through the code reveals that QTime rather than QDateTime is being used to represent times, which explains things like why Airplay thinks my roughly 36-hour log is 12 hours long, so the obvious candidate is that somewhere code is comparing the predicted start time with the current time and concluding that the event is in the past, but I can't put my finger on any code actually doing so. Has anyone heard of a similar bug? Is it something that's been fixed in more recent versions? I'll work on getting an installation set up that's viable to run under gdb and see if I can unpick what the refresh process is doing wrong soon... Chris ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
[RDD] Natural Log question solved
Thanks to Tim Camp for the help on this one. I was having problems with some RD clocks not importing traffic. It was fixed by slackening up the start times in the Event used for traffic. Regards Warren Mead Gold MX/Fly FM ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
Re: [RDD] Chain To Woes
On Oct 19, 2011, at 12:55 38, Reid Fletcher wrote: > I can't try it right now, but isn't it possible to specify the log date > in a CHAIN command by using metacharacters instead of a hard > coded date? No, not right now. Cheers! |-| | Frederick F. Gleason, Jr. | Chief Developer | | | Paravel Systems | |-| | A room without books is like a body without a soul.| | -- Cicero | |-| ___ 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 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] Jack in Rivendell Appliance
The talkunafraid blog has alot of useful information referring to JACK and Rivendell. I found that when I am not getting sound output through jack it is because the connections have not been made. You can check this by opening the control (qjackctl) and opening the connections window. I have set the jack control to start at computer startup and and the connections made in the rd.conf file so that connections are made at startup of rivendell should system require restart. Guy Curtis ___ 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 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
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
Greetings, This really sounds like you are trying to re-invent the wheel here. I have six stations chaining everyday some hitting a top of the hour network news and never one problem. You either put in plenlty of extra songs and use a timed event or time out your programing as best you can and put the chain command at the end of the log. If you are going to use a timed event and it really doesn't matter if you are a minute or so off, then I would suggest using "timed next" It's not really complicated. Cheers On Wed, Oct 19, 2011 at 11:55 AM, Reid Fletcher wrote: > > I can't try it right now, but isn't it possible to specify the log date > in a CHAIN command by using metacharacters instead of a hard > coded date? > > I'm proposing that one codes a timed CHAIN set to trigger at, > oh say, 1 minute into the new day. It would be in every log. > At 1 minute into the new day the CHAIN would execute, translating > the metacode to the CURRENT day's date, and as a consequence > load the log for that day's date. When things were running > correctly, it would merely reload itself and in doing so, position > itself at the event following the CHAIN because the clock would > have advanced beyond the time for the CHAIN. In the event a > wrong log was loaded, it would self-correct because the meta > characters would still translate to the current calendar day when > the CHAIN executed. > > Another failsafe might be to permanently load a run log containing > nothing but a CHAIN an AUX deck that at 1 minute after new day, > re-loads the main deck with the current day's run log. That would > be it's sole duty. Running independently of the main run log would > keep Main log sequencing from waylaying the process. How you > chose to specify the log in the CHAIN would remain your choice. > > Of course this depends on my initial question's answer being "yes". > It's a question wanting to be a suggestion. > > __Reid__ > > > On 10/19/2011 8:57 AM, Rob Landry wrote: > > > I wonder what you're doing that I'm doing differently. > > Do you have any timed events in the last hour of the day (i.e. after 11 > P.M.)? I have none. Some of my stations have timed events at 10:56 P.M. and > 12:56 A.M., but none have any timed events after 11 P.M. > > > Rob > > On Wed, 19 Oct 2011, James Gamblin 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><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 > listRivend
[RDD] Jack in Rivendell Appliance
Anyone of you have working Jack on Appliance? I try but I couldn't make it work (snd_pcm_open_conf) Cannot open shared library /usr/lib/alsa-lib/libasound_module_pcm_jack.so -- regards Isaac ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
Re: [RDD] Chain To Woes
I can't try it right now, but isn't it possible to specify the log date in a CHAIN command by using metacharacters instead of a hard coded date? I'm proposing that one codes a timed CHAIN set to trigger at, oh say, 1 minute into the new day. It would be in every log. At 1 minute into the new day the CHAIN would execute, translating the metacode to the CURRENT day's date, and as a consequence load the log for that day's date. When things were running correctly, it would merely reload itself and in doing so, position itself at the event following the CHAIN because the clock would have advanced beyond the time for the CHAIN. In the event a wrong log was loaded, it would self-correct because the meta characters would still translate to the current calendar day when the CHAIN executed. Another failsafe might be to permanently load a run log containing nothing but a CHAIN an AUX deck that at 1 minute after new day, re-loads the main deck with the current day's run log. That would be it's sole duty. Running independently of the main run log would keep Main log sequencing from waylaying the process. How you chose to specify the log in the CHAIN would remain your choice. Of course this depends on my initial question's answer being "yes". It's a question wanting to be a suggestion. __Reid__ On 10/19/2011 8:57 AM, Rob Landry wrote: I wonder what you're doing that I'm doing differently. Do you have any timed events in the last hour of the day (i.e. after 11 P.M.)? I have none. Some of my stations have timed events at 10:56 P.M. and 12:56 A.M., but none have any timed events after 11 P.M. Rob On Wed, 19 Oct 2011, James Gamblin 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
Re: [RDD] Auto Fillers
I have never used that feature in Rivendell, but, in my experience with other software (music schedulers, traffic systems, automation systems) the autofill feature is not really automatic. Even though it is "autofill" you still have to manually initiate the process, I have not yet seen a "system" that will "on the fly" detect that a show will run short and automatically start filling the holes. If you suspect that a show will run short you can overfill the hour. From: Stan Fotinos To: Guy Curtis ; User discussion about the Rivendell Radio Automation System Sent: Tuesday, October 18, 2011 7:51 PM Subject: Re: [RDD] Auto Fillers There is a function in admin/service for allocating fill in carts, but have never used it. Hope that is a start for you. Stan On 19/10/11 5:01 AM, Guy Curtis wrote: Is there a way that i could get rivendell to automatically pick fillers if shows finish before it is supposed to? > > >Guy Curtis > > > >___ 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 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
I wonder what you're doing that I'm doing differently. Do you have any timed events in the last hour of the day (i.e. after 11 P.M.)? I have none. Some of my stations have timed events at 10:56 P.M. and 12:56 A.M., but none have any timed events after 11 P.M. Rob On Wed, 19 Oct 2011, James Gamblin 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
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" 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
Re: [RDD] Natural Log traffic question
Are you using the Rivendell export module in Natural Log? In Rivendell clock you can set a fudge length of time before and after the stopset scheduled time. This sometimes will help if exact time is off a bit. On Oct 18, 2011 7:31 PM, "Warren Mead" wrote: > ** > Recently purchased Natural Log traffic for a RD system I am working on. > > After a small amount of effort (and Wiki reading) I was able to internally > generate music on RD and then merge the traffic log that Natural Log had > created. It worked perfectly. > > The problem is, it only works with one RD clock. When I created another > clock with different hourly spot start times, the spots were missing from > that hour. > > I tried editing the Natural Log template break start times to match the new > clock - still no spots. > > The Natural Log text file looks normal, so I'm thinking it's something I've > overlooked in Rivendell. > > Any suggestions would be very much appeciated! > > Thanks > > Warren > > > > > ___ > 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
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
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
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
Re: [RDD] Chain To Woes
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
Re: [RDD] Chain To Woes
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
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
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
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
[RDD] Chain To Woes
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
