Bugzilla – Bug 17320
Rhapsody does not work if using WiFi bridging
Last modified: 2012-03-05 07:09:27 UTC
I upgraded my SBS to 7.5.5 and found Rhapsody will no longer play on my SB3. The display denotes buffering of the song, then appears to stop (no progress shown on the music advancing). I've tried playing Rhapsody through Squeezebox Server and while the server shows the music time advancing (and even goes on to the next song when finished), the SB3 simply shows the song name and no time advance. Rhapsody is working fine with my Boom, so I know my setup is fine. I've also made sure I didn't have any synchronization between the Boom or SB3 as well. I originally tried running server version 7.5.5 and firmware version 134 on my SB3, then also tried server 7.6.0 - r32741 with firmware version 137. Both exhibit the same problem.
Are you by any chance using using wifi bridging with your SB3?
Yes, I do use wifi bridging.
Andy, Looks like the problem is tied to wifi bridging. When I disable bridging, Rhapsody plays correctly. Please confirm if you can duplicate the problem on your end.
OK, we may not be able to support Rhapsody and bridging at the same time. I would suggest finding an alternate solution for your ethernet device, perhaps a standalone wifi bridge.
Does this impact Duet as well? My Duet controller is connected to the receiver in bridge mode and I am seeing the same issue with Rhapsody.
Hi, I am having the same problem (Boom & Radio work) but my Classic is not easily accessible and it is a pain to go connect an ethernet cable. Can I check / disable bridging wirelessly?
I can confirm that the bug is somehow related to the wireless bridge settings. Even though I was NOT and never have used the wireless bridging option, when I connected an ethernet cable and explicitly disabled wifi bridging, it solved the problem. I had the same symptoms that others have reported. I have a Squeezebox Classic, and when the problem started, I was running Squeezebox Server 7.4. (Not sure what firmware version I had.) A couple weeks ago, Rhapsody stopped working. All other apps worked fine. In Rhapsody, I could browse/search for albums/tracks, make a selection, it would say it was buffering, then act like it was playing, but no sound. I tried switching from Squeezebox Server to mysqueezebox.com, but it didn't help. I upgraded to the latest version of Squeezebox Server - v 7.6 - r32854. Reading the release notes from 7.5, and seeing there was fix for Rhapsody, I was hopeful that this would fix the problem. After the server upgrade, my Squeezebox automatically updated to firmware version 137. I tried Rhapsody - no dice. Same exact symptoms: I could connect and browse, but no music! After reading about this bug, I decided to try plugging in an ethernet cable and disabling wireless bridging. Now here's the thing: I have never used wireless bridging. I have only connected my Squeezebox to my LAN wirelessly. I did not have an ethernet cable plugged in. By definition, wireless bridging is all about bridging a wireless connection with a wired one. To use it, you have to have a wired ethernet connection to some other device! Not having an ethernet cable plugged in, I did not think the comments about wireless bridging would be relevant to my setup. But I didn't know what else to try, so... I plugged in the ethernet cable, connected it to my router, held down the left arrow to re-do the network setup, chose "No" on the wireless bridge option, and after going through the rest of the setup, Rhapsody worked! I immediately disconnected the ethernet cable, and Rhapsody continues to work with no problems.
Well, it worked fine bridging for over 3 years. Why is Logitech removing this valuable feature?
Rhapsody requested us to implement new certificates in the player firmware. This larger data unfortunately breaks bridging, lack of memory. There's no way to have them both work, we're sorry.