Bugzilla – Bug 16650
No Audio - Not Buffering in Rhapsody
Last modified: 2010-11-08 11:40:50 UTC
We're getting a lot of reports of customers unable to play Rhapsody tracks on both SqueezeOS and older players. They see the track information as if it was playing, the progress bar moves, but there is no audio. We are also getting reports that it shows buffering, but never finishes the buffering stage, and possibly skips to the next song. This has occurred since a recent change with the Rhapsody App, as the icon appears to be different.
I had this problem over the last three days with both a SB Radio and an SB Touch. This morning both were working again.
Created attachment 7024 [details] Log of Radio with audio.* and net.slimproto set to DEBUG Happened this morning on Radio in my house. Happened to have logging enabled -- audio.* and net.slimproto were enabled. I grabbed both messages and messages.0 log and put them into one larger file. Using Squeezebox Server Version: 7.5.1 - r30836 @ Tue Jun 1 06:02:45 PDT 2010. Saw these relevant items in server log: [10-11-06 23:00:51.5226] main::init (323) Starting Squeezebox Server (v7.5.1, r30836, Tue Jun 1 06:02:45 PDT 2010) perl 5.010000 [10-11-07 07:56:58.8641] Slim::Plugin::RhapsodyDirect::Plugin::rpds_handler (318) 00:04:20:07:8a:b9 Rhapsody decoding failure: code 112 [10-11-07 08:03:40.4616] Slim::Plugin::RhapsodyDirect::Plugin::rpds_handler (318) 00:04:20:07:8a:b9 Rhapsody decoding failure: code 109
Should describe incident in comment 3 in more detail: - Radio firmware is r9009 - Able to see Rhapsody menus, and when I press Play track appears to play normally, but zero sound from track - Sound effects from menu navigation, etc. heard OK Other players at my house had issues with Rhapsody playback too.
Also, in my incident the Now Playing percentage indicators visible when audio.* set to DEBUG showed 100%/0% at bottom of screen. I was able to watch the number on left slowly increase from 0 to 100, and it stayed at 100 during the track playback. Given that, I believe the buffer is being filled, albeit slowly. There was no audio playback for local tracks either. I factory reset the Radio. Only then could I play local tracks. Another attempt to play Rhapsody resulted in a crash and reboot. Log enclosed too.
Created attachment 7025 [details] Crash log
On my Touch, after I try to play a Rhapsody track audio output on the Squeezebox is completely disabled until you force a FW update or restore factory settings. Even a power-cycle does not restore audio.
*** This bug has been confirmed by popular vote. ***
I have this problem on my Touch & Radio, but not on the Duet. Sounds like a incompatibility between some upgrade on the Rhapsody servers with the newer architecture Squeezeboxen?
Pretty sure it's a Rhapsody issue: http://forum.rhapsody.com/rhapsody/problems/common
(In reply to comment #9) > Pretty sure it's a Rhapsody issue: > > http://forum.rhapsody.com/rhapsody/problems/common It most likely is. I wasn't implying that the problem is with the Touch/Radio. Sometimes bugs are exposed only under certain conditions. Maybe the Touch/Radio use a certain Rhapsody API with different parameters than the Duet. I was merely providing information that might help debug. As of this morning, I can confirm that Rhapsody streaming works on my Duet but still not on the Touch/Radio.
As of now Rhapsody works on all types of clients including IP3K based Logitech ones, only SqueezeOs players are failing. Furthermore SqueezeOs players are being caused to crash by attempting to play a Rhapsody stream. You can argue that whoever made the change needs to provide a fix, but I fear that will not get us to a solution. Rhapsody may claim that there change uncovered a latent bug in SqueezeOs and that they are still compliant tithe documented API.
I've contacted Rhapsody about this.
Fixed, unfortunately this will require an updated firmware. We hope to get this out as quickly as possible.