Bugzilla – Bug 7661
Rhapsody Direct hangs when starting a new track
Last modified: 2009-07-31 10:18:46 UTC
When playing a Rhapsody playlist, SB3 will randomly stop when it moves on to a new track within the playlist. When this happens, the left-side data buffer indicator starts increasing from 0 to the full number of seconds that correspond to the track's length. The right-side audio buffer remains stuck at a low number such as 0.0 or 0.3, and no sound comes out. While the left-side data buffer increases, the router's bandwidth meter shows a normal fast and consecutive download rate from Rhapsody. The SB will just hang like that indefinitely, until a forward, back or play button is pressed on the remote, at which point the relevant track is restarted and all proceeds normally again. The attached log was taken with SqueezeCenter Version: 7.0 - 17759 - Windows XP - EN - cp1255 This has been occurring for a very long time now.
Created attachment 3150 [details] Log of hang when starting a new track I skipped a track at 20:33:50 The SB3 hangs as described in comment and nothing further is printed in log after 20:34:04.4551 (until pressing play, ff or rewind)
For a photo of the SB3 and the buffers counts when it hangs, see http://forums.slimdevices.com/showthread.php?t=44427
Created attachment 3151 [details] Sb3 hanged while it proceeded to next track in playlist SB3 hanged at 15:41:50.6591 while it proceeded to next track with a Rhapsody playlist (no involvement on my part here) It continued normally after I pressed "next" at 16:51:55.8853
Maybe similar to bug 6508
Might also be a firmware bug.
QA to reproduce, then assign to felix to investigate.
I had the following log settings at DEBUG: plugin.rhapsodydirect, player.source, player.streaming.direct I had "show buffer fullness" in the player's display settings Play a large Rhapsody playlist. A good candidate is Top Tracks of Willie Nelson which includes over 1000 tracks. Then there are 2 possible methods to reproduce: 1. Passive approach: Just leave it alone playing. Take a look a the SB3 display from time to time, at some point it will hang with no sound. 2. Proactive approach: Skip to next track. If it starts playing (with sound) skip to next track. Do so until SB3 hangs with no sound. It might occur on track #3 or #30 or #300...
Assigned to Ross for reproduction & logging
I just experienced the same exact behavior as described while playing Rhapsody through SqueezeNetwork. Andy, let us know if you need anything else.
Based on y360's log, I fixed a bug in change 18623 related to handling of the case where an rpds 3 call does not come back in time and the player underruns. I don't think this is the cause of this bug though. Will keep investigating.
More SC logs would be helpful.
Is there anything else needed to be placed under debug in addition to plugin.rhapsodydirect, player.source, player.streaming.direct
No, those options should be enough. I take it you didn't see any improvement from my fix in 18623?
I will attempt to reproduce under debug with latest 7.0.1 nightly
Andy, I think the bug is fixed. SqueezeCenter Version: 7.0.1 - 18702 played 240 Rhapsody tracks without hanging. It still happens in SN but that's probably because SN hasn't been updated yet. I also encountered tracks being skipped but that's a different bug.
Well that's good news!
Marking fixed, please reopen if you see it again.
Andy, could you please update this bug when the fix is released to SN, thanks
The next SN release is currently scheduled for April 29. You can test the latest SN code by connecting a player to www.test.squeezenetwork.com (or add "use_sn_test: 1" to your server.prefs file).
I'm sorry to report the problem is still happening with the upgraded SN I managed to reproduce with latest 7.0.1 SqueezeCenter Version: 7.0.1 - 19242 @ Tue Apr 29 08:35:16 PDT 2008 - Windows XP - EN - cp1255 I will attach a log shortly
Created attachment 3311 [details] first incident at 08-04-30 23:21:43.4605, second incident at 08-05-01 00:01:08.6269 First incident at 08-04-30 23:21:43.4605 Second incident at 08-05-01 00:01:08.6269
Bummer, it seems to be the same situation, the track right before the hang failed with a decoder underrun before it started, and this puts the player into a bad state or something.
I rewrote a bit of the Rhapsody code today to fix a bug with synced channels, please retest this bug with tonight's nightly.
Created attachment 3384 [details] 7.0.2 - 20236 reproduced at [08-05-28 21:40:27.2345] Reproduced with SqueezeCenter Version: 7.0.2 - 20236 See at [08-05-28 21:40:27.2345]
OK, thanks. Nothing helpful in the log though, it just seems to stop for no reason. What did the player UI do during this time?
Andy, under "show buffer fullness" it was the same as described in the initial comment of this bug.
We're having trouble reproducing this, but we believe that it is happening. If anyone can help with comments or logs please leave additional comments!
Please test firmware 101 in tonight's 7.1 nightly. I fixed a memory bug in Rhapsody that may have contributed to this bug.
Anybody seen this with 7.1 yet?
I'm on SqueezeCenter Version: 7.1 - 22103 @ Fri Jul 25 01:03:09 PDT 2008 - Windows XP - EN - cp1252, And It seems that the issue is mostly fixed. I only have the problem when synced with two players. (Currently I have two, one wired, one wireless). Recently the issue seems fixed, however, during a rhapsody channel, the controller will show towards the end of a track time remaining 59:59 and nothing will happen for a while. And then suddenly the next track will start, and the screen eventually refreshes. At this point, this is more functional than before, and still works for most uses, but I thought I'd point this out. I will try to replicate the problem tonight when I get home and detail here precisely what happens..
Going to mark this one fixed.
Verified fixed in SqueezeCenter 7.2.1-23472 Controller 7.2 r3070 Receiver r48 SB2/3 r113 Transporter r63 Boom r33
This bug has been fixed in the 7.3.0 release version of SqueezeCenter! Please download the new version from http://www.slimdevices.com/su_downloads.html if you haven't already. If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.
Reduce number of active targets for SC