Thanks. I'll check into this. Chris Howard also lent some advice which seems to make sense. He requested screenshots and came back with the following:
"I am not an expert by any means. But I think I understand what happened. When "Between The Devil And Me" started at 11:56:28.6 and it lasted 4:20. By the time it finished the time would have been 12:00:40.6 The first hard event was at 12:00:00 and the second hard event was at 12:00:30 When "Between The Devil And Me" finished, it was already time for the 2nd hard event and the thing just jumped right to it. The general rule, at least as much as I can tell, is that the hard events pass by and the most recent one to have passed becomes the next thing to happen." He went on to suggest that a fix could be to place small events in front as a buffer such as PSA's. What he's saying seems to make sense but I'm with him in the "I'm no expert" department. So, that leads to a question of are Hard Timed Events set up as Make Next limited to a certain amount of time before they too are skipped like regular (music) events? Additionally, in the Use Hard Time menu, there is a "Wait" option. Is that wait time a time you can specify for that particular event to wait before it expires and is skipped over or is that a delay time for that event to wait before it fires off? I know in Zara Studio you can set a max wait time on an event and if a song runs over that amount of time, the event expires and the log continues on. One thing to note that I sorta touched on in my original email, these events are currently set up as 2 individual events containing multiple carts. For example; TOH contains a Weather cart and Legal ID cart. BOH contains Weather Intro, Weather Sponsor & Weather carts. The skipping is not the TOH or BOH event itself. It's actually skipping various carts within the events that looks to be a time purge. In other words, BOH will have Weather Intro and Weather sponsor skip but not the Weather cart. I had an instance yesterday where it played the Weather Intro & Weather Sponsor but skipped the Weather. I'll look into Jim's notes and see if I can come up with anything there. ---brandon > Date: Tue, 18 Mar 2014 16:59:57 +0000 > From: Jim Stewart <[email protected]> > Subject: [RDD] Log Skipping Hard Start Time Events > > I also have never had this problem and we use "hard" time events all the time. > > I have had (and still do) problems with, at least macro events, that are too > short (time wise) that things can be skipped over, but that doesn't seem to > be your case either. > > Other places to look for hints to what is going on is: > > > 1) Generate an "as played" log, as in setup a log that records all > events, (in rdadmin), then go and generate one of them (in rdlogmanager) for > a day you had problems. It will produce a simple text file somewhere that > you can easily share with us. > > 2) Logs of Rivendell events show up in system logs anyway. Depending on > your Linux Distribution, it should show up a few places so try these commands > and see what you find: > > a. sudo less -S /var/log/syslog > > b. sudo less -S /var/log/messages > > and look for various "caed" events so to see what and when things are > happening. ("less" is a simple pager, you can use Pg-up/dn to navigate > around or "/<searchtext>" to search for things, "//" does a "search next". > Do "man less" for more info.) _______________________________________________ Rivendell-dev mailing list [email protected] http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
