Bugzilla – Bug 4795
Streaming reconnect fails after forget player
Last modified: 2008-12-18 11:12:53 UTC
Brief Description ============= When attempting to reconnect to Slimserver from a remote Windows Media Player, connection succeeds but no sound is heard. If browser is refreshed Windows Media Player looses connection. Detailed Description ================ Slimserver running on a Windows 2000 box behind a hardware firewall. Port 9000 open on firewall allowing remote connections and Slimserver password-access only selected for security. Connection is from a Windows Media Player instance executing on a Windows 2003 box and via the Internet. See repro steps for details of the bug. Repro Steps =========== 1. Browse to slimserver from remote IE6.0 and ensure only local Squeezebox instances are listed in 'Settings'. 2. Open Windows Media Player on remote W2K3 box and open URL http://<URL to slimserver>:9000/stream.mp3 entering correct username/password. 3. Refresh browser to see player instance in 'Settings' and select in right-pane drop-down. 4. Select a few songs and start playing. Verify stream by listening to WMP. 5. Close Windows Media Player. 6. On Slimserver select 'Forget Player'. 7. Reopen Windows Media Player and open URL http://<URL to slimserver>:9000/stream.mp3 entering correct username/password. 8. In WMP, note display states 'Buffering....' but no music heard. 9. In browser showing slimserver site, click 'refresh'. 10. When slimserver page refreshed WMP states 'stream' length (the time shown is the time from the initial connection to when the browser was refreshed) and 'plays' (no sound heard) out. Remote IP address is not listed in 'Settings'. Steps 7 - 10 can be repeated with the same results. Notes ===== I connect to the slimserver from a corporate network and the player IP address can change between connection instances. Due to this i have to 'forget player' between connections to ensure i 'play' to the correct player instance (otherwise i would have a number of IP addresses listed in the slimserver dropdown and not know which one to stream to).
Mat thanks for the very clear details. I'm going to have a look at this shortly, I will report back with what I find.
Thanks again Mat. With your clear and detailed instructions I was easily able to verify this issue. If it helps, this is not reproducible with username and password not enabled. To recap: SlimServer 6.5.1 running on XP (must be password protected), Windows Media Player running on windows 2k3 server. From WMP open URL, enter user/pass and stream music. Then close WMP, 'forget player' for the 2k3/wmp computer, then open wmp and open url once, it will connect and appear to stream, but only silence.
Created attachment 1826 [details] TCP Traffic for first connection to slim server This is the TCP traffic for the initial connection of the WMP to the remote slimserver.
Created attachment 1827 [details] Second connection to slim after selecting forget player After the first, good, connection the WMP was closed and 'forget player' selected in slimserver. The WMP was then reopened and a connection made to the same instance of slimserver. The TCP traffic was caught in this 'SecondDuffConnection' file. The second connection behaved as described in the bug.
(In reply to comment #2) > Thanks again Mat. With your clear and detailed instructions I was easily able > to verify this issue. If it helps, this is not reproducible with username and > password not enabled. > To recap: > SlimServer 6.5.1 running on XP (must be password protected), Windows Media > Player running on windows 2k3 server. From WMP open URL, enter user/pass and > stream music. Then close WMP, 'forget player' for the 2k3/wmp computer, then > open wmp and open url once, it will connect and appear to stream, but only > silence. SlimServer 6.5.1 running on Windows 2000 (not XP), otherwise recap is correct. In addition, if the browser to slim is refreshed WMP indicates stream has stopped and plays the silence out.
Assigning to Dan. Let me know if you need anything else from QA.
Ross, Dean suspects you did not hit 'play'. Could you try again?
Now I'm seeing the bug before even forgetting the player. I tried streaming from XP running 6.5.5 nightly from 10/23 to a win2k3 server WMP and winamp, both show tag information for the track playing in SlimServer, but do not play any audio. Yes, I clicked play in WMP / winamp.
Password protection works once again, however this bug still exists. After establishing the connection I close the software playing via stream.mp3, forget the player, re-open the stream.mp3 software and click play it says Squeeze Center and shows the stream that was playing before, but there is no audio.
Ross I will come look at this bug when you get a chance. If this is a real bug, I would at least like to find a workaround before shipping 7.0.
I should go talk to Ross
Cannot reproduce, I tested with Foobar2000 and WMP11. It did take a lot longer (~50 seconds) for WMP to begin playing after I played something from the web interface though, I guess it uses a bigger buffer. One thing I wonder if we should do with web clients is auto-forget them when they disconnect...
I've made 3 changes related to this bug. 1. The player name for web clients is now more helpful, i.e. "foobar2000 from 192.168.1.10" 2. When a streaming client disconnects it is automatically removed from the list of players. 3. When a streaming client reconnects and there is an existing playlist, auto-start playing it without requiring you to hit 'play' in the web UI. This is basically a forced 'power on resume' since we can assume if you connect to a stream you'd like to hear music. Playback will begin at the beginning of the last track you were listening to. Marking this bug as fixed, please reopen if you still have problems.
This bug is being closed since it was resolved for a version which is now released! Please download the new version of SqueezeCenter (formerly SlimServer) at http://www.slimdevices.com/su_downloads.html If you are still seeing this bug, please re-open it and we will consider it for a future release.