2 jingles back to back at random times

[hdradio]

Last night it happened 2 times:
at 21:04 and 21:27 two jingles played back to back.
This is happening at random times. It can happen once a week or once in 15 days or two in a month.
By looking at the current script I don't see anything wrong.
Is there a way to find what causes that ?

[radio42]

You might send me the your Debug log file, even if it is 200MB large to take a look at.
In addition I would need your .pfs script file which was running.
Any overlays scheduled at exactly that time? If yes I need those entries as well.

One typical case is for example if certain script lines could not be executed because they violate a history or script rule and are skipped because of that.

You can check the Source Info column in your playlist from where the 2 jingles originate to find out.

[hdradio]

https://1drv.ms/u/s!Agz248daKO8hg8dKZ9hTFYaLiDN5tA
Keep in mind that later, I recreated that script to be sure that it's ok.
No overlays play at that time (except time announce at 21:00 and 21:30).

Maybe it's what you say about violate history check, but there were enough songs for each script line .

[radio42]

If the song histories are violated it will be recorded in the debug log. I'll take a look later this evening, as I am currently on holiday.

[radio42]

There are really a lot of history 'warnings' and 'errors' in your debug log file, which indicate some scripting issues with your configuration:
(the few socket exceptions contained in the log file didn't really blur these out...)

1) e.g.:
24/08/2016 05:58:34: Script-Line 1 skipped: UseLastTrackOnFinalFail is not set, max history tries reached (Tries=361/180)
or
24/08/2016 05:58:35: Script-Line 4 skipped: UseLastTrackOnFinalFail is not set, max history tries reached (Tries=361/180)
or
24/08/2016 21:42:35: Script-Line 7 skipped: UseLastTrackOnFinalFail is not set, max history tries reached (Tries=721/360)

As your script always schedules exactly one Track and then one Jingle, then one Track and again one Jingle etc., a skipped track script line would immediately result in 2 Jingles playing back to back!
So you might use the 'UseLastTrackOnFinalFail' script option to resolve this issue.

Before the above log entries you will find a lot of these entries, e.g.:
24/08/2016 05:58:35: Script-History: entry directly contain in history (Entry=Πάριος Γιάννης - Πάμε για ύπνο Κατερίνα, MaxHistory=90)
or
24/08/2016 05:58:35: Global-History: entry 'Artist' is contained in history (Entry=Γαλάνη Δήμητρα - Σε πελαγίσιο μνήμα, Artist=Γαλάνη Δήμητρα, MaxHistory=40)

As you can see: these issues are related to your history settings.
Note, that you are using script-line Filters! This limits the number of resulting media library entries. And often your 'Artist' history check rule is violated, so you might need to relax that as well?!


2) e.g.:
24/08/2016 06:02:26: Cancelled Script-Line 2 (LineTries exceeded): 1 LeastRecentlyPlayed : Ελληνικά (Filter=~[RatingValue] > 70 And [Genre] = 'Ακουστικό' And [Year] <= '1990', Options=None)

This log entry indicates, that the Filter conditions AND history checks are so restrictive, that even after trying ALL possible script-lines, none could return a track! Note, that this error happend with a script which did not schedule any Jingles, meaning it was a different script than the one you send me.
However, this is in essence a result of the issue explained under 1) - as here simply all script-lines 'failed'.