Bugzilla – Bug 3513
Rhapsody sync sometimes fails due to Rhap server 403 error
Last modified: 2009-09-08 09:12:58 UTC
The fix for bug 3336 appears to sort have fixed Rhapsody. It's possible to sync but weird things still happen: Sometimes neither player will start and you need to press play again to get them to start. Sometimes during a track advance, one player will start without receiving the unpause. The second player won't start at all. This seems to be caused by Rhapsody sending back a 403 error to the second player.
Rhapsody sync is working better now, still need to see about syncing Rhap Radio.
I can sync regular Rhap and Rhap Radio. The only issue now seems to be an infrequent 403 error returned by Rhapsody to one of the synced clients when trying to stream a file. I've sent a log to Seth @ Real to see if he knows what the problem could be. Changing the name of this bug to reflect this issue.
SlimServer Version: 6.3.0 - 8002 - Mac OS X 10.4.6 (8I127) - EN - utf8 Synced SB3 and SB2. When I went to settings -> synchronize, it worked fine! Then if I chose a different song all from Rhap server (on either player) it plays fine on the SB3, and shows the song name on the SB2 but no audio from SB2. Thought the obvious and reprogrammed xilinx, that wasn't it. I was able to reproduce this in the other direction. If I change the song to something else from Rhap server on SB2, it will sometimes play fine on both players, sometimes only play on the player the remote is pointing to, and the other player will show the song name, and no progress, and no audio.
Yeah sounds like the same thing I see, and seems to be Rhapsody's fault. Still haven't heard back from Seth about the log file I sent him.
No response from Real. Punting to 6.5.
Andy to ping Rhapsody
Rhapsody UPnP is dead.