Hi all,
I've been discussing some of the quirks and strangeness with timed
events and log chains with a German member of the mailing list
(thankfully his English is much better than my German).
As you all know with a log chain at the end of the day Rivendell ticks
through the list until there is only the log chain left and then it
loads a new log.
Then the whole days log loads up. On a local machine this is fairly
instant but can still take up to a second on modest hardware. There are
also some further delays with network setups that you can mitigate with
some tweaks to mysql (e.g. skip host name lookup and I'm sure many others).
There are also cases where the log loads exceptionally fast and then you
can get strange (and rare ish) issues whereby the new log also has a
23:59:59 event and seeing as its still 23:59:59 it also executes and
seems to break.
Personally I've always worked around this by using the aux log to shunt
things around, wait for a second and then continue.
We've talked about a couple of options in various levels of complexity:
* Add a date to the timestamp in the database for log.
This would solve the weird twice firing issue (in theory) but I like
being able to load arbitrary logs without concern for the date,
especially for testing purposes. E.g. I made a change for Friday so
lets load that now on Monday to make sure it works as expected.
* A rolling log where log chain is never actually necessary for the
play list to work as intended.
This is more complex in terms of required changes but has some benefits
(and drawbacks). For example airplay always populates with x items to
play. Lets say 20 for now. When event 1 starts playing, event 21 is
appended to the end of the list.
If we get a log chain we append event 1 of the that new log to the end.
In theory this would remove any awkwardness about end of day log
chaining but it also means presenters always know whats happening next.
One minor problem we have here is my final show of the day runs from
22:30 - 01:30, at 23:59 ish, the presenter only really knows that there
is a log chain and not really what is happening next so can't make an
informed link.
Plus you occasionally find out at 23:59 that something broke and now you
have no log. Wouldn't it be nice(r) to always have your next hours
worth to hand? (let me please add that this is normally an operator
error and not Rivendell at fault)
The required changes aside (which aren't trivial changes) the main
drawback to this is you couldn't add a track 10 hours in advance using
airplay. Logedit would still work.
Anyway just thought I'd throw this out there for consideration before
thinking about digging into code.
Regards,
--
Wayne Merricks
The Voice Asia
#######################
Scanned by MailMarshal
#######################
############
Attention:
The information contained in this message is confidential and intended
for the addressee(s) only. If you have received this message in error
or there are any problems, please notify the originator immediately.
The unauthorised use, disclosure, copying or alteration of this message
is strictly forbidden. Christian Vision or any of its subsidiaries will
not be liable for direct, special, indirect or consequential damages
arising from alteration of the contents of this message by a third party
or as a result of any virus being passed on. Please note that we reserve
the right to monitor and read any e-mails sent or received by the
company under the Telecommunications (Lawful Business Practice)
(Interception of Communications) Regulation 2000. Christian Vision is
registered in England as a limited company 2842414 and as a charity
1031031
############
_______________________________________________
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
