On 19/08/2020 4:35 am, Bj Mora wrote:
Hi Mark,
The answer to your last question is “Yes,” it would be a problem if
the Friday night log ended early, so the Saturday 0000 LEGAL ID (your
next timed event) would run before scheduled, and then the LOG chain
would soon start your Sunday log (assuming you had a Sunday log ready
to go). If you didn’t have a Sunday log, then RDAirplay would stop.
One suggestion is to schedule that Saturday 0000 LEGAL ID timed event
before 0000 (ours is at 2359:56). (Our log chain is still scheduled
for 0000.01.) And make sure that last hour (2300) is over scheduled as
you have done.
in His service,
BJ Mora for GraceRadio at graceradio.net <http://graceradio.net>
KGCE-LP/Modesto NOW at FM 107.9!
Good point, I pad out with PSA's, the first one is make next, and the
last one is a make next to drop any un-needed prior ones if a song is
very close to ending on the hour. At the 11PM hour, the last one is a
macro that puts the mainlog to sleep and wakes it up just before the
sound panel finishes a cart to avoid log roll over delays . I generally
run 1 song overscheduled each hour, but sometimes all songs play out.
I'll have to schedule another to be safe in the 11pm hour after reading
this. This is also why I use a logchain as a segue after timed events,
to try and avoid timed events as the roll over event.
Message: 1
Date: Mon, 17 Aug 2020 17:11:57 +0000
From: Mark Murdock <[email protected]
<mailto:[email protected]>>
To: "[email protected]
<mailto:[email protected]>"
<[email protected]
<mailto:[email protected]>>
Subject: [RDD] RDAirPlay Crash
Message-ID:
<dm6pr12mb38652675e2ddebfd426989a2b3...@dm6pr12mb3865.namprd12.prod.outlook.com
<mailto:dm6pr12mb38652675e2ddebfd426989a2b3...@dm6pr12mb3865.namprd12.prod.outlook.com>>
Content-Type: text/plain; charset="us-ascii"
We started using Rivendell on-air in February, and for the most part
it has worked very well for us. Twice however, we have had RDAirPlay
crash at midnight. The latest was Friday night. We are running
version 3.4.0. We have our IDs scheduled as a timed start, hard start
time, make next for 59:30 for each hour, including 23:59:30. We
overschedule our hours a bit so that the ID will usually play near
the top of the hour. I looked at the log for Friday, and everything
looked normal. There was a correct "Log Chain" command at the end of
the log scheduled for T00:00:00.0 that pointed to the log for 0815.
Does anyone have an idea why RDAirPlay might quit under these
circumstances?
Crash/quit as in locked up or gone, or just stopped as Mark has suggested?
Gavin.
Would there be a problem if the last song of the day ended before the
ID was scheduled for 23:59:59 and then the log chain command came in
before 00:00:00? If you have any ideas, I would appreciate it!
Thanks much!
Mark Murdock
KAMB
90 E. 16th St.
Merced, CA 95340
(209) 723-1015
[email protected]
<mailto:[email protected]><mailto:[email protected]>
Website<https://celebrationradio.com/>
<snip>
_______________________________________________
Rivendell-dev mailing list
[email protected]
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
_______________________________________________
Rivendell-dev mailing list
[email protected]
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
