Windows KB4512941 update and PF, AssignNextTrackToPlayer (TrackCueOut) failed

You found a bug or have any issues? Please post them here!
Post Reply
jsonio
Posts: 51
Joined: 10 Dec 2018 11:39
Windows KB4512941 update and PF, AssignNextTrackToPlayer (TrackCueOut) failed

Post by jsonio »

Hello Bernd,

Since the windows update 1903 / KB4512941 the 5th of september and the PF update to 4.1.3.1, everything goes wrong with PF. The scheduler does no more load the next programs and stay forever on same one, there is many cuts and (very) long silences... Because everything started with the W10 update, we are going to try to remove the KB4512941 today because Microsoft reported a "CPU overusage" bug.

I enabled the debug log to see if PF detect something during the silence and it gives many sequences like this :

09-09-19 08:08:10: AssignNextTrackToPlayer (TrackCueOut) failed: Player=B already assigned2 (Loading, True)
09-09-19 08:08:10: DJ-StartDone B: loading track (-2147482449, Artarpop 73 & le Collectif le Temps des Cerises - Attention... l'armée !, 00:09:58.6000000)
09-09-19 08:10:22: DispatchCommand: EXEC_SEND_EMAIL PROPPFREXX SILENCE|PROPPFREXX HAS JUST DETECTED A SILENCE @ 2019-09-09 08:10:22
09-09-19 08:10:22: DispatchCommand Reply: OK
09-09-19 08:37:15: DJPlayerReport: Player=B, Event=TrackPause: Artarpop 73 & le Collectif le Temps des Cerises - Attention... l'armée !

As you can see ie here nothing happened during 27 minutes... the only fail message seem to be : AssignNextTrackToPlayer (TrackCueOut) failed: Player=B already assigned2 (Loading, True)

What does it mean? Could it be the reason of the silence? Could it be related to W10 update bug?

Thank you a lot for your opinion about it,

jsonio
User avatar
radio42
Site Admin
Posts: 8295
Joined: 05 Apr 2012 16:26
Location: Hamburg, Germany
Contact:
Re: Windows KB4512941 update and PF, AssignNextTrackToPlayer (TrackCueOut) failed

Post by radio42 »

I haven't heard anything related from any other user yet.
But there seems to be indeed something wrong with your machine/windows10 update.
The debug log showed, that it took 20 minutes to load a single track, which is of course insane and not normal.
So yes, rolling back to the last save point might be a good idea.
Hope you can resolve the system issue!
jsonio
Posts: 51
Joined: 10 Dec 2018 11:39
Re: Windows KB4512941 update and PF, AssignNextTrackToPlayer (TrackCueOut) failed

Post by jsonio »

Hello Bernd,

In fact, it is not possible to roll back this W10 update :( So I tried to monitor carefully PF running to see if it could be related to a CPU overusage. PF was like just using 2% of the CPU... not exactly an overrun...

I think I finally found the source of the problem : we are using RDP to access to the PF computer and it seems that, since the KB4512941 update + the PF 4.1.3.1 update, exiting RDP, locks the W10 session in a way that PF dislikes. Of course the session isn't totally closed but just "locked" until the next connection.

On the previous log the 20 minutes between loading the track and playing the track were in fact the period between having closed the session and having opening it again.

Is there some "keep alive" settings I should know about PF?

If someone needs it, I solved the problem by using this workaround : tscon.exe RDP-Tcp#NNN /dest:console to close the RDP session makes everything working fine again.
User avatar
radio42
Site Admin
Posts: 8295
Joined: 05 Apr 2012 16:26
Location: Hamburg, Germany
Contact:
Re: Windows KB4512941 update and PF, AssignNextTrackToPlayer (TrackCueOut) failed

Post by radio42 »

This is good to know! Especially the workaround.

The Win10 update in fact comes with a known issue about RDP. It effectively ‘steals’ the audio session of any running app. Resp. it leaves it in a situation, so so that the app (in this case ProppFrexx) would require to reset its audio session.

Currently there is no way for PF to detect this or issue a keep alive.
Another option is maybe to switch from RDP to E.g. VNC or another demoting tool.

Post Reply