I've been banging my head against the wall on an issue which prevents me
from enjoying Spotty.  First I thought something was wrong with my
SqueezeAmp and started looking in the logs to see if I could get some
insights.  Eventually, I realized something was wrong on the server
side.

Fast forward:  I ended up running the squeezebox server from the command
line to get the output from the socket wrapper, as it seemed that it was
somehow terminating abruptly.  What seems to happen is:
    
- Socket wrapper opens up spotty 
- socket wrapper transfers several data chunks, so far so good
- After some time, the socket wrapper stalls and watchdog kills the
  process
  

Here is the extracted socket wrapper log:

Code:
--------------------
    SW: 2019-10-25 12:21:35.282 Socketwrapper 1.11beta
  SW: 2019-10-25 12:21:35.283 -i 0 -o 51681 -c 
"C:\ProgramData\Squeezebox\Cache\InstalledPlugins\Plugins\Spotty\Bin\MSWin32-x86-multi-thread\spotty.exe"
 -n Squeezebox -c "C:\ProgramData\Squeezebox\Cache\spotty\8ba0b816" --verbose 
--single-track "spotify://track:6lhDKRxI7fjL1Jao6erY1n" --bitrate 320 
--disable-discovery --disable-audio-cache --pass-through 2> 
C:\ProgramData\Squeezebox\Cache\spotty\spotty.log
  SW: 2019-10-25 12:21:35.294 Init complete.
  SW: 2019-10-25 12:21:35.295 # =input== =output= ==type== ===details===
  SW: 2019-10-25 12:21:35.295 0 00000008 00000114  PROCESS 
"C:\ProgramData\Squeezebox\Cache\InstalledPlugins\Plugins\Spotty\Bin\MSWin32-x86-multi-thread\spotty.exe"
 -n Squeezebox -c "C:\ProgramData\Squeezebox\Cache\spotty\8ba0b816" --verbose 
--single-track "spotify://track:6lhDKRxI7fjL1Jao6erY1n" --bitrate 320 
--disable-discovery --disable-audio-cache --pass-through 2> 
C:\ProgramData\Squeezebox\Cache\spotty\spotty.log
  SW: 2019-10-25 12:21:35.295 1 00000110 00000120  THREAD  Output Socket
  SW: 2019-10-25 12:21:35.296 MoveDataThreadProc for step 1 started.
  SW: 2019-10-25 12:21:35.297 MoveDataThreadProc for step 1 about to call 
ReadFile.
  SW: 2019-10-25 12:21:36.142 MoveDataThreadProc for step 1 got 7986 bytes, 
about to write data.
  SW: 2019-10-25 12:21:36.299 MoveDataThreadProc for step 1 about to call 
ReadFile.
  SW: 2019-10-25 12:21:36.299 MoveDataThreadProc for step 1 got 8192 bytes, 
about to write data.
  [... repeat 2 lines above, many times ... ]
  SW: 2019-10-25 12:21:41.286 MoveDataThreadProc for step 1 about to call 
ReadFile.
  SW: 2019-10-25 12:21:41.286 MoveDataThreadProc for step 1 got 8192 bytes, 
about to write data.
  SW: 2019-10-25 12:21:41.286 MoveDataThreadProc for step 1 about to call 
ReadFile.
  SW: 2019-10-25 12:21:41.286 MoveDataThreadProc for step 1 got 8192 bytes, 
about to write data.
  SW: 2019-10-25 12:21:55.305 Watchdog expired - Thread for step 1 stalled.
  SW: 2019-10-25 12:21:55.305 Tidying up
  SW: 2019-10-25 12:21:55.307 Watchdog expired
  SW: 2019-10-25 12:21:55.307 Waiting for process step 0 to terminate
  SW: 2019-10-25 12:21:57.308 Tidying up - process for step 0 hasn't died or 
wait failed. wr=258 :0
  SW: 2019-10-25 12:21:59.323 Tidying up - Thread for step 1 hasn't died.
  SW: 2019-10-25 12:21:59.323 Thread for step 1 streamed    603 blocks 
totalling 0046DE64 (4644452) bytes
  SW: 2019-10-25 12:21:59.323 Exitcode for Thread 1 Code=259
  SW: 2019-10-25 12:21:59.338 Socketwrapper has terminated.
  
--------------------


This results in a cascading effect which causes
Slim::Player::Source::_readNextChunk to detect the end of the stream and
report "end of file or error on socket", with a position that represents
the number of bytes read.  At this point, the streaming controller
changes to a new streaming state : STREAMOUT. The player will keep going
until its internal buffer is empty, and the next track will start.

Unfortunately, and with a variety of players (duet, boom, etc), this
most of the time result in a song that gets cut out.

Is there any way to get some logging out of spotty or its underlying
librespot?  This might help me unearth the actual root cause, as for now
I'm in the dark.



LMS 7.9 - 1xRadio, 1xBoom, 5xDuet,3xTouch, 1 SB2. Sony PlayStation,
Emby, Chromecast v1 and v2 and... 
*SQUEEZEAMP*!
------------------------------------------------------------------------
sle118's Profile: http://forums.slimdevices.com/member.php?userid=35009
View this thread: http://forums.slimdevices.com/showthread.php?t=110455

_______________________________________________
plugins mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/plugins

Reply via email to