Please provide more details. Which players, which stations, where are the players located?

I have this problem all the time with Slacker and Pandora.  It seems to be hit and miss.  One thing I have found, it seems to be the same songs.  On Rhapsody, I cannot play any song from Van Halen Diver Down.  It hangs on buffering.

More details are in this forum thread:

http://forums.slimdevices.com/showthread.php?t=83314

It says:

1. New Rhapsody issues ever since they moved to new datacenter, seen on Sonos and Squeezeboxes.
2. Rhapsody plays fine for awhile and then strange things happen. See posting for log details with error numbers returned from Rhapsody during playback.

Do know what these Rhapsody error numbers are and what we should do when they occur?

Changing bug to focus only on latest Rhapsody issue. Please open new bug if not Rhapsody related.

Rhapsody acknowledges issue and says it will be fixed soon:

http://forums.slimdevices.com/showthread.php?t=83382

Created attachment 7047 [details]
Rhapsody Log

Maybe this might help...

This has been happening for about a month - Rhapsody won't complete a track and throws up an error message "Audio Stream Failed, Skipping to Next track...". Only affects SBRs when synced - unsyncing them solves the issue.

'Code 112' error seems to crop up regularly in the logs.

[10-11-11 16:04:28.9526] Slim::Plugin::RhapsodyDirect::Plugin::rpds_handler (307) 00:04:20:16:31:38 Got RPDS packet: \"p"
[10-11-11 16:04:28.9533] Slim::Plugin::RhapsodyDirect::Plugin::rpds_handler (318) 00:04:20:16:31:38 Rhapsody decoding failure: code 112
[10-11-11 16:04:28.9558] Slim::Plugin::RhapsodyDirect::ProtocolHandler::onStop (751) onStop, logging playback
[10-11-11 16:04:28.9567] Slim::Plugin::RhapsodyDirect::ProtocolHandler::_doLog (809) Logging track playback: 6 seconds, trackId: Tra.2100509, stationId: ps.8647993

Rhapsody support directed me to Logitech.

Please note, as bibbs@hickorytech.net stated, this is also affecting his Slacker and Pandora. Could there be more to this bug than just Rhapsody?

For me, Pandora works fine - it is my go-to service when Rhapsody is flaky. no issues for me there.

This is not just a Rhapsody issue.
I and many other users have been having exactly the same problems with Napster,(I don’t use Rhapsody). 
Please refer to forum thread  http://forums.slimdevices.com/showthread.php?t=82994&highlight=Napster

Created attachment 7051 [details]
server.log excerpt showing Rhapsody decoding failure

(In reply to comment #10)
> Created an attachment (id=7051) [details]
> server.log excerpt showing Rhapsody decoding failure

I'm seeing this error while streaming Rhapsody to an unsynced SB3 (firmware 130) with Squeezeserver 7.5.1 on Mac OSX.

Going back over the logs for 2010, I see the first occurrence of code 112 on 2010-11-17. It's been annoyingly frequent since then.

[10-11-17 12:57:10.0826] Slim::Plugin::RhapsodyDirect::Plugin::rpds_handler (318) 00:04:20:12:8e:fc Rhapsody decoding failure: code 112
[10-11-17 13:24:02.3715] Slim::Plugin::RhapsodyDirect::Plugin::rpds_handler (318) 00:04:20:12:8e:fc Rhapsody decoding failure: code 112
[10-11-17 13:27:18.8685] Slim::Plugin::RhapsodyDirect::Plugin::rpds_handler (318) 00:04:20:12:8e:fc Rhapsody decoding failure: code 112
...

*** Bug 16677 has been marked as a duplicate of this bug. ***

This appears to be a bug in the ip3k firmware HTTP code, somehow triggered by a server-side change at Rhapsody.  This is Rhapsody-specific.

...
> I'm seeing this error while streaming Rhapsody to an unsynced SB3 (firmware
> 130) with Squeezeserver 7.5.1 on Mac OSX.
...

I've seen this on SBR, SBB, and SB3. They are all in a sync group, but the issue also occurs when only one player in the group is running. However, it seems to be worse or more noticeable when multiple players are on.

I had this issue on SBS 7.6 so I downgraded to 7.5 to see if that fixed it. It did not.

I tried opening a ticket with Rhapsody, but they weren't that helpful.

 == Auto-comment from SVN commit #7593 to the player repo by agrundman ==
 == http://svn.slimdevices.com/player?view=revision&revision=7593 ==

Bug 16667, nearly finished fix for Rhapsody split-packet EA bug.  Also improved performance and fixed some other bugs, especially thread sync locking bugs

This is fixed and will be released with the next ip3k firmware update as part of 7.5.

(In reply to comment #16)
> This is fixed and will be released with the next ip3k firmware update as part
> of 7.5.


Thanks Andy.  When will we get this?  Rhapsody continues to be unusable for me, hoping this will fix things.

7.5.2 r31586 has the updated firmware.  I'm not sure when it will be rolled out to SN, for now you can use the nightly for Rhapsody.

I can no longer play Rhapsody through my Squeezebox Duet. Everything else, such as Pandora, and Internet radio stations, works fine. I have upgraded to 7.5.2. 

The UI acts normally when I select Rhapsody - shows buffering, etc. But there is no sound. I have had this problem for 3 days.

Rhapsody w/ Squeezebox worked pretty well for the 2 weeks up until this failure. Prior to that, I had intermittent problems with skipping or stopping. When the skipping problem restarted, I upgraded to 7.5.2 per this thread:
http://forum.rhapsody.com/rhapsody/topics/rhapsody_suddenly_failing_on_squeezebox?utm_content=reply_link&utm_medium=email&utm_source=reply_notification#reply_4209742

That worked for about a day. Then this problem -- no sound -- started. 

Version: 7.5.2 - r31603 @ Thu Dec 9 02:19:30 PST 2010

verified fixed in SB Server 7.5.2

Tim - mine is sometimes a little flaky, and sync'd players sometimes lose each other, but for me, updating SBS fixed the bug identified in this thread. I wonder if your issues are related to something else?

Tim - mine is sometimes a little flaky, and sync'd players sometimes lose each other, but for me, updating SBS fixed the bug identified in this thread. I wonder if your issues are related to something else?

(In reply to comment #22)
> Tim - mine is sometimes a little flaky, and sync'd players sometimes lose each
> other, but for me, updating SBS fixed the bug identified in this thread. I
> wonder if your issues are related to something else?



I am now having the same problems that Tim described above.  I initially had the symptons of the original problem with Rhapsody--songs would skip, errors, etc.  I upgraded to 7.5.2 and that took care of those problems for a couple of weeks.  About three or four days ago, I started experiencing the problems Tim describes:  album art appears, it buffers up to 100% and it appears to be playing a track but no sound comes out.  All other internet based services work fine:  Pandor, Napster, etc.  I experience this both on mysqueezebox and when connected to my home pc.  I have reinstalled 7.5.2 and factory reset by system.  I have also uninstalled and reinstalled the Rhapsody app on mysqueezebox but nothing has worked so far.  Is this still an issue others are seeing?

I also have been having problems similar to the ones described. We use a Logitech squeezebox duet and when running Rhapsody, it just stops playing. The screen on the duet looks as if it is playing. Even the latest update 7.5.2 for this squeezebox server did not fix the problem. I don't experience this problem when using Rhapsody on the squeezebox radio.

Support says issue may still occur after this fix. Not sure what's going on -- need more details. Reopening to further investigate.

Had a customer using Squeezebox Radio v7.5.3 getting error:

"audio stream failed skipping to next track"

Only happening on Pandora.

Player plays internet radio fine without issue.  Router is located about 10 feet from player.

Removing and re-installig app via MySqueezebox.com didn't seem to help.

Only thing that seemed to fix the issue was re-installing v7.5.3 on player.

Not sure if that was what fixed it or not, but seemed to in this case.

Case #110311-004746

Please open distinct bug report for distinct services.