Ran into this problem a few months ago as well: if there's a song playing at
midnight and you have an event to set itself to NEXT at 00.00 or somewhere
there, it will do that, because no date is specified.
We solved this by creating a macro-cart with commandline RN
/home/rd/loadlog-nextday!
Just happened upon (a) possible bug(s) this morning while monitoring my test
stream live...
For whatever reason, in the 5AM hour this morning, the main log (rdreportLOG)
played just three elements: a 1/2 hour program that started early; a 2m feature
(scheduled at 5:28); and a 4m feature
