there are two solutions
1 make sure you overschedule that last hour clock.
2 figure out how an event at the end of the log [chainto] is being
called at midnight. Have you got a time sync just before it?
Put the time sync at 11:55 then schedule close to 5 minutes and let the
chainto event happen
, 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
Eve
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 trigg
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!
|---
001...@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
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 woul
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"
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 p
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 da
__
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 overschedule
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
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 t
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
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
ma
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:
>> T
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 wo
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
> deci
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
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
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:
> Whe
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/
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
22 matches
Mail list logo
