Client reported that Sequencer played in silence from 02:17:56 to 02:18:08 in Sep 11. This is the second time that the same problem happened, the latest issue happened at 02:15:49 in Sep 10.

I checked the log, here is what I found: 1.LINK#410544 began to play at 02:17:34, along with the segue mark of SONG#410543, ended at 02:17:36, but the stop time in log showed 2:18:08. 2.SONG#410543 didn’t fade out in its segue mark at 02:17:34, it continued to play and ended at 02:17:56, but the stop time in log showed 2:18:08. 3.Sequencer stopped at 02:17:56 and began to play at 02:18:08. 4.Our client enabled “Auto Fade Songs at Segue”, “Fade-Out Duration” and “Hard ETM Fade Start Offset” were all set as 0.8s. 5.Their SR backup machine has same log structure, same station settings, sequencer played correctly at above time. 6.There are also some same log structures in this main site log, but this problem only happened at 02:17:56.

I also see these in debug at the time of problem happened, but have no ideas for them.

1
2

9-11 02:18:07.994 | Seq    | SEQUENCER       | CQ881-FM        | CheckForIsAliveSend took 81574!  Step1: 0, Step2: 81574, Used ThreadedPingMessage=False, Used BroadcastMessage=True
9-11 02:18:08.057 | Seq    | SEQUENCER       | LockWithTimers  | Long lock statement - Name: ProcessNormalQ Diff: 81.6469999999972

Our client wants to why this happened.

I have uploaded all debug cue and backup files to this site folder in NY ftp.