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
