Bug 12302 - Playback randomly stops at end of track (-00:00), before new track starts - QNAP
: Playback randomly stops at end of track (-00:00), before new track starts - QNAP
Status: CLOSED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: Misc
: 7.3.2
: Other Linux (other)
: -- normal with 1 vote (vote)
: Future
Assigned To: Philippe Kehl
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-06-08 03:46 UTC by Dominique Cote
Modified: 2009-09-25 03:50 UTC (History)
1 user (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dominique Cote 2009-06-08 03:46:31 UTC
first, i apologize if this has been reported in a different context in another bug before. but despite my best efforts i could not find a similar bug in the DB, so here is a new report.

recently i have noticed that playback will randomly stop and the end of a track. the clock shows -00:00. the player will actually say "NOW PLAYING..." but it isn't. sometimes this can happen every two or three tracks, sometimes it will go for days with no stop at all.

pressing the "next"-button will advance to the next track (after a short delay) and playback will continue. when i try to repeat the "offending" track by pressing "back", the transition to the next track works fine. so it is not (easily) reproduceable. :-(

in my case, this will happen under the following circumances (AFAIK):
-> transition from any format to any format (i use vorbis, mp3 and aac)
-> occurs on my SB3s (two of, wireless) and softsqueeze 3.7 (wired)
-> no specific combination of players needed to cause this
-> crossfade is active
-> replay gain is active (smartgain or track gain)
-> analog VU screensaver
-> happens when synched and unsynched
-> i mainly use large, saved playlists with around 400-1000 tracks in them in "shuffle" mode.

my system specs are:
Version: 7.3.2 - 24695 @ Mon Jan 19 18:36:25 PST 2009
Hostname: Turbonas
Server IP Address: 192.168.0.102
Server HTTP Port Number: 9001
Operating system: Linux - EN - iso-8859-1 
Platform Architecture: armv5tejl-linux
Perl Version: 5.8.8 - armv5tejl-linux-thread-multi
MySQL Version: 5.0.27
Total Players Recognized: 3

SC runs on a qnap TS-409 Pro, with firmware 2.1.4 Build 0318T, codepage Western Europe/Latin 1 (850) and using SSOTS 3.15.

Player Model: squeezebox3
Firmware: 123
Player IP Address: 192.168.0.5
Player MAC Address: 00:04:20:07:4e:dc
Wireless Signal Strength: 44%
 
KitchenPlayer Model: squeezebox3
Firmware: 123
Player IP Address: 192.168.0.4
Player MAC Address: 00:04:20:07:a8:c6
Wireless Signal Strength: 64%
 
SoftSqueezePlayer Model: softsqueeze
Firmware: 2
Player IP Address: 192.168.0.11
Player MAC Address: 1b:e5:d9:ba:3d:9a

please note that there is an active thread on this topic in the forum at:

http://forums.slimdevices.com/showthread.php?p=430230

there seem to be a number of other people experiencing the same problem, but not necessarily under the same circumstances... the only commonality i could see so far, is that we all use SC - which is why i posted this bug in the "squeezecenter" section.

please let me/us know what we can reasonably do to help nail this bug
Comment 1 James Richardson 2009-06-08 09:07:45 UTC
Does the same error happen with SC 7.3.3 (beta)

Please download from http://downloads.slimdevices.com/nightly/?ver=7.3 if you haven't already.
Comment 2 Dominique Cote 2009-06-08 15:06:10 UTC
it is not a linux-only problem. ppb (as he states in the thread) is running his SC on win XP. which is why i purposely left the "platform" empty. ;-)
Comment 3 Dominique Cote 2009-06-17 07:54:21 UTC
finally - after a long wait, i got a stop which i could capture. the player's buffer (in this case softsqueeze) drops to 0% and does not refill. i have left it in this state for over 20 minutes now just in case it recovers itself - which it didn't.

short of upgrading to 7.3.3., are there any logging settings i can activate which will help us to identify the problem?
Comment 4 James Richardson 2009-06-17 08:08:43 UTC
(In reply to comment #3)
> finally - after a long wait, i got a stop which i could capture. the player's
> buffer (in this case softsqueeze) drops to 0% and does not refill

Does the same error happen with your Hardware Players, SB3?  if so, then you could capture a log file from that.

Softsqueeze is no longer a supported application/software player so I really can't accept it's failure as a failure of SqueezeCenter

My suggestion would be to wait for FlipFlip to release a 7.3.3 version of SqueezeCenter for your QNAP, then load that version and test the hardware players again.
Comment 5 James Richardson 2009-06-17 09:37:38 UTC
This bug has been fixed in the 7.3.3 release version of SqueezeCenter!

If you haven't already. please download the new version from http://www.logitechsqueezebox.com/support/download-squeezecenter.html 

If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.
Comment 6 Dominique Cote 2009-09-24 03:30:45 UTC
guys, i was hoping this bug is indeed fixed - it is not.

i am running:
Version: 7.3.3 - 27044 @ Mon Jun 15 15:03:29 PDT 2009 (upgraded)
Hostname: Turbonas
Server IP Address: 192.168.0.102
Server HTTP Port Number: 9001
Operating system: Linux - EN - utf8 
Platform Architecture: armv5tejl-linux
Perl Version: 5.8.8 - armv5tejl-linux-thread-multi
MySQL Version: 5.0.27
Total Players Recognized: 3
SSOTS: 3.18 (upgraded)

i am still getting random stops with exactly the same symptoms.

sometimes playback will go for hours or even days, other times it will stop every couple of tracks.

all players are always synced, but usually not all of them are on/playing: 2x SB classic, 1x boom (recently purchased).

my qnap is not running any other programs in the background and the last time it happened i know there weren't even other clients accessing it either. effectively the qnap was idle.
Comment 7 James Richardson 2009-09-24 05:31:36 UTC
Dominique: sorry, but I am out of ideas at this time.  Please try the official QNAP forums http://forum.qnap.com/

There may be people there with the same issue, or more knowledgeable on the QNAP product that can help you.
Comment 8 Dominique Cote 2009-09-25 03:50:07 UTC
i did. but the forum for SC over at qnap is not exactly one of the most active - in contrast to here. so i found no specific answer, nor a thread describing the problem.

james, perhaps i can provide a snapshot/log of the situation. can you please instruct me as to which logging settings i need to activate to maybe help you look into this?