Bugzilla – Bug 10613
SqueezePlay audio output lost while still "playing"
Last modified: 2009-09-08 09:29:39 UTC
SqueezPlay sometimes "looses" the audio playback, especially when system load is high (high CPU load or swapping). The song is still shown playing in both SP and SC but the audio stops. Can usually be remedied by pressing SPACE BAR twice (i.e. Pause and Continue Play). I’ve seen this with all SP versions since, currently using the 2009-01-07 nightly build with SC 7.3.2 - 24541 on Windows XP Home+SP2, 1.8GHz Intel, 768 MB RAM. (On a system like this, MusicIP + SC + SP use up ALL resources, especially memory between 780 and 930 MB according to task manager, CPU load between 13% while streaming the middle of a song, going up tp 100% when SP requests info from SP, like lists or song change. Using Firefox for SC makes SP stutter or loose audio sometimes.)
Btw, when streaming to another audio client like Winamp on the same setup, audio never stutters or is lost, even though Winamp roughly eats double the memory SP requires (i.e. between 130 and 170 MB) and *really* makes the system swap a lot.
SC 7.3.3-24684/Win, SP 2009-01-16/Win: Stops audio output after between 5 and 10 songs, jumps back to 0:00 in the current track, counts till between 0:28 and 0:38, jumps back to 0:00, repeats this endlessly.
please include a log with the following set to debug: formats.audio player.source player.streaming
Sorry will take another few days until I can come back with serious test results, had a harddisc crash here, currently restoring backups ...
I believe I'm having the exact same problem. When I view the Debug Playback screen while playing, my Decode and Output Buffers hover between 99-100%. My decode state is 11. All my files are FLAC. When the music stops, my Decode State goes from 11 to 12, and my Output Buffer goes to 0%. I have plenty of PC processing power, and I've never experienced a dropout from my Squeezebox.
Unable to replicate with 7.4 r27942 and SP 7.4 r5936 Please retest with the above version or higher. If you are still able to replicate the issue, please provide logs as requested and reopen the bug.