ralphy wrote: > Have you had a chance to 'try this' > (https://forums.slimdevices.com/showthread.php?113554-SqueezeLite-on-Windows-pausing-interruption-dropout-of-audio-every-5-minutes&p=1002509&viewfull=1#post1002509)?
Ok so I got the new build, and tested again today. The outages happened, as before. But I did NOT see any socket errors, after several outages over 45 minutes. Yesterday, I did see the socket errors a couple of times, but as I've pointed out, the socket errors happened AFTER the audio dropout, and seems to be a symptom, but doesn't point towards the cause. But yesterday, I did notice the socket error happen when the console was blocked, so I was able to force the error as follows: 1. In the console, with debug output running, use the mouse to select text in the console. This causes console output to be blocked, until you right-click the console. 2. While the console is blocked, use the squeezebox controller to seek ahead on the track. This forces activity in SqueezeLite, but the application is blocked, due to the console. 3. Now the socket error starts to appear. [14:57:11.357] stream_thread:404 end of stream [14:57:11.358] sendDSCO:214 DSCO: 0 [14:57:12.368] sendSTAT:195 STAT: STMt [14:57:14.380] sendSTAT:195 STAT: STMt [14:57:14.859] process:527 strm [14:58:10.318] process_strm:280 strm command t [14:58:10.328] sendSTAT:195 STAT: STMt [14:58:10.328] mad_decode:207 end of stream [14:58:10.338] mad_decode:292 gapless: early end - trimming padding from end [14:58:10.338] decode_thread:100 decode complete [14:58:10.338] slimproto_run:715 output underrun [14:58:10.348] sendSTAT:195 STAT: STMd [14:58:10.358] send_packet:114 failed writing to socket: 2745 [14:58:10.358] sendSTAT:195 STAT: STMu [14:58:10.378] send_packet:114 failed writing to socket: 2745 [14:58:10.378] slimproto_run:578 error reading from socket: Unknown error [14:58:10.518] slimproto:932 connected [14:58:10.518] sendHELO:148 mac: 70:85:c2:a8:ce:68 [14:58:10.525] sendHELO:150 cap: CanHTTPS=1,Model=squeezelite,AccuratePlayPoints=1,HasDigitalOut=1,HasPolarityInversion=1,Firmware=v1.9.8-1318-test2,ModelName=SqueezeLite,MaxSampleRate=384000,dsf,dff,alc,aac,ogg,ops,ogf,flc,aif,pcm,mp3 Note that this is NOT the error we're talking about, this is some other issue. I would not expect the console to be blocked, in normal operation, so this does not indicate any issue by itself, I was just forcing it to misbehave. Also, looking at the code yesterday, I did notice that the "retry" code exists in 2 places: send_packet() and slimproto_run(). It seems that the change you made was only to send_packet(), and the handle 2745 was found there. The other one still shows "unknown error". Ralphy can you tell me how to find the details of your most recent commit? Last time you provided a link to it, but I don't see a way to get it through github. I'm logged in to github, but I don't see how to find the commits. Please help me navigate to the commits. Thanks ------------------------------------------------------------------------ foopydog's Profile: http://forums.slimdevices.com/member.php?userid=71156 View this thread: http://forums.slimdevices.com/showthread.php?t=113554 _______________________________________________ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
