RDJ pauses after event even when in autodj/automation mode

[Rob Ashcroft]

See the following video description of the issue
https://youtu.be/PYkzSlbWyi0

An event used at the top of the hour successfully loads and begins, but pauses playout after a 2 second wait manual event.  The exact same event worked in v1.8.3  but seems to have this glitch in v2

Any suggestions on fixes?  Thanks

[Richard - Radio Rubery]

Sounds to me like the rotation hasn't been edited for V2 (an issue I came across as well).  All you need to do is open each rotation and click the edit icon at the end of each line then Ok and save the rotation once all lines are done.  You will then find it works.

[Rob Ashcroft]

Sounds to me like the rotation hasn't been edited for V2 (an issue I came across as well).  All you need to do is open each rotation and click the edit icon at the end of each line then Ok and save the rotation once all lines are done.  You will then find it works.

Except this is not in regard to a rotation at all, it's an event; so that particular fix is not applicable here.

In the meantime I have removed the 2-second wait manual event from the one-item playlist that is part of the TOH news event (basically the event loads and empty playlist between news tracks for the moment).  That works fine, so I have isolated the manual wait event as the issue.

Next I will recreate a 2-second wait manual event to include in the loaded playlist to see if that resets things.  I'll post back the results when done.

[Rob Ashcroft]

Here's a clip of the rebuild process: https://youtu.be/Jj3b_WIChHE
The result is the same: https://youtu.be/SKdjtsCIURY

Next will try two different things.
1. delete the playlist and save a new one with a different name (but do everything else the same)
if that doesn't work...
2. add a 'play' instruction following the manual event containing the 2 second wait

[Rob Ashcroft]

Next will try two different things.
1. delete the playlist and save a new one with a different name (but do everything else the same)
if that doesn't work...
2. add a 'play' instruction following the manual event containing the 2 second wait

So the first step resulted in no fix/change BUT the second step did.  The gap feels a bit looser so I will reduce the wait time though (maybe to 0.5 seconds).

Long screen recording of that latest process trialling changes: https://youtu.be/Q-OqShDKHZ8

[neutralhills]

I can confirm the same behaviour on my system. An event that works on 1.8.2 and keeps playing after the pause won't play on 2.0.0 unless I add PLAY to the sequence. I wish I had seen this a couple of days ago.

[Rob Ashcroft]

I can confirm the same behaviour on my system. An event that works on 1.8.2 and keeps playing after the pause won't play on 2.0.0 unless I add PLAY to the sequence. I wish I had seen this a couple of days ago.

I noticed yesterday [on one occasion] it seemed to continue playing after the 'wait' [like it used to in 1.8.2], meaning that having the added 'play' in the event then skipped past the next track straight after playing it.  All a bit strange, and trying to figure out if that's what actually happened or not. 

The first variable length track (news) seems to usually time out correctly, the second one (sport) times out way too early.

Has there been any software programming changes to the way these actions work?

[Rob Ashcroft]

Hi Neutralhills,

I've just tried organising my top of the hour news event in a different way, and it seems to work better now without the extra play command.

Instead of stacking everything into the one event, I have created a playlist for the news [intro track - news track - wait event - sports track - wait event - news outro]

That playlist is then loaded into the top of the hour event that includes the extra things like disable/enable RDJ, clear playlist, load news playlist, load a variety of stings/promos/ads after the news.

Not sure why it works, it just does :-)  Though I may need to extend my 2 second wait to three seconds, as that seems a bit too tight now, cutting off the very end of the variable length tracks.

Hope that makes sense.  Not sure if it will work in your scenario for however you use the wait command?