v2.1.41 - Fixed time items not taking - 2 issues

Archive mAirList 2.x (English)
1

Hi Torben, et al.

I am actually running an RSL at the moment, called Whitchurch FM, and thought I’d try the development release as a lot of the DJs still use CDs and we don’t rely on mAirList, and I also wanted to use a couple of fixed time events to get us into the news. I know it’s a risk, but someone has to at some point.
I am please to report that I’ve not had a single crash or problem, but we’re only really dragging items into the schedule as needed.

We had only good feedback from the presenters last time we were on air with the stable version and I’m gradually converting them all - thanks Torben - we’re all big fans of your work!

Here’s my scenario:
hh:59:30 - an event turns auto on
hh:59:34 - start news jingle playing from cartwall slot 1,
hh:59:58 - open line in 1 to inject news onto the cartwall output (I have three players and the cartwall asd separate inputs to the mixer)

I wanted these last two to be scheduled events in the playlist, so the DJs can see what’s going on with timings etc, change it if necessary, and it fades out the last track.

ISSUE 1: Initially I tried these as fixed time commands - and they didn’t run at all as far as I could tell - is this a bug?

My solution was to schedule them as silence events with the commands embedded within - this also gives some nice countdowns etc.

Here’s what I have in the playlist:

News CARTWALL News Jingle Start 200000000 15:59:34 #FF8000 CARTWALL 1 START News BREAK #FF8000 News CARTWALL News Inject 100000000 15:59:58 #FF8000 6 0 6 Automation Stop #FFFF00

Most of the time, this has run really well with the slickest news junctions you could hope for, but occasionally (ISSUE 2) one or other or both, of the events just don’t run. I’d say this has only happened 1 time in 14, but it would be great to know if we can rule out the failures.
The playlists are copied from each other with just the time edited for each hour. We’ve been running for a few days and the errors aren’t consistent.

Please let me know if there’s any logging or other useful info that might help resolving things.

2

Hi iain, and welcome.

Thank you for your detailed description of the issues. This is what a bug report is supposed to look like :wink:

I will look into these issues as soon as possible (that is, probably not before Christmas, as I’ll be in India from tommorrow to December 23rd).

On bug/limitation I know about is that stop actions will not be executed when the items happens to fade out in the “background”, for example when you’re only using a single player for automation, and each fading item is detached from the player in order to load and play the next item. But as you’re only using start actions, this shouldn’t be an issue here.

Torben