If i understand well, your problem is that the Make Next event behaves
like a "Start Immediately" event ?
I seem to remember having encountered this behavior years ago on 2.x but
i can't find a mention of it in my notes. I believe it had to do with
several make next events "accumulating" while waiting for a cart to end.
I might have been something like:
55:00 a 7-minute long cart starts.
58:00 Timed Make Next Event n°1 starts waiting
59:00 Timed Make Next Event n°2 should start waiting but cuts everything
before it and plays the next event immediately.
I'm not sure if the solution was anything else than avoiding this kind
of situation.
I'll try to reproduce this when time allows.
. leo
On 2019-11-23 05:04, Matthew Chambers wrote:
So I am toying around with Rivendell after having not messed with it
for a couple years. I installed v2.19.3 from the Paravel repo onto
CentOS7.
I have a bunch of content ingested and created a pretty plain standard
clock, has music, and breaks and the last event is the TOH ID that is
set to Start Make Next at x:59:50, I use that to "clean up" any extra
songs from the hour and be ready to start the next hour. However when
x:59:50 arrives the currently playing song abruptly stops, the ID
plays and the next hour starts right at the top of the hour, instead
of floating and starting after the current event. Did some behavior
change for Make Next events that I missed, or maybe a bug that I
should upgrade to v3 for?
Matthew Chambers, CBT, NR0Q
Owner/Engineer
M CHAMBERS COMMUNICATIONS ENGINEERING LLC
PO BOX 311, Atlanta, MO 63530
Office (660)239-4911 Mobile (660)415-5620
www.mchambersradio.com [1]
Links:
------
[1] http://www.mchambersradio.com/
_______________________________________________
Rivendell-dev mailing list
[email protected]
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
_______________________________________________
Rivendell-dev mailing list
[email protected]
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
