Bugzilla – Bug 17579
No Audio from Rhapsody on IP3K
Last modified: 2011-10-10 08:36:19 UTC
No audio when streaming Rhapsody to IP3K from SBS 7.6.X.
Bridging is enabled?
Latest ip3k firmware installed?
This is an excerpt of my description of the problem to the Stage II tech support: "I have an SB3 Classic that connects wirelessly to the same Network. That one works fine with Rhapsody, using the server or mysqueezebox.com, so I don't think it is the firewall issue. In the transporter I can see all my rhapsody information (Playlist, Artist, Albums, tracks, etc) but when I hit play on a track, the transporter shuts down and reboots, reconnect to the network, goes back to the rhapsody and into the track it was trying to play, says connecting, buffering and when it should be ready to play, shut down/reboot again to start the cycle once more. Sometimes after a couple of those cycles, it loads up again, goes into Rhapsody, display the track info and it would say music stopped."
Today I was tinkering with the Transporter and I got it to work with Rhapsody, believe it or not using mysqueezebox.com not even the SB Server. I did a factory reset (Power+ADD), then did the setup as always but with the Ethernet BRIDGE on NO. It worked perfectly. Then I did set up again with the Bridge set to YES and it when back to give me the same problem. Had to repeat the factory reset and setup to get it to work again. So, that's where the problem seems to lie. My directv gets connected to my home network using the transporter as an internet access point. The way things are right now I either get rhapsody or directv (OD and whole house access to the DVR). Everything was working fine until the last firmware update before I submitted the first report of the issue
OK, Rhapsody is broken with bridging and this won't be fixed, unfortunately.
(In reply to comment #5) > OK, Rhapsody is broken with bridging and this won't be fixed, unfortunately. Why? Why if it was working perfectly before? I The transporter is an expensive piece of equipment, I paid almost 2k for it, I really don't think this is the way to address issues like this. How can I escalate this?
Because Rhapsody changed their SSL certificate, and it now requires twice the memory it did previously.
Workarounds: switch to another service, or buy a $50 standalone wifi bridge.