Bugzilla – Bug 573
SoftSqueeze navigation causes track playing to jump back to the beginning
Last modified: 2008-12-18 11:55:18 UTC
I'm using SoftSqueeze 1.4 and I'm finding that about 20% of the time I navigate left or right in the menu system this results in the track currently playing stopping and then starting to play again from the beginning
Sounds a bit like a combination of things. The official 5.3.0 release had a bug that would restart a track when the player resumed after power-off or disconnect. This also means that softsqueeze is somehow disconnecting in order to trigger this bug. Can you try the Sept 23 nightly build to see if you still have restarts?
I tried the 23rd nightly build and the same thing happens. I also noticed this in the Win2k Event Log. Attempting to use the BBCNews.pm module resulted in the windows service stopping. I guess that is another bug?
Forgot to attach the Event log and BBCNews.pm version Event Type: Error Event Source: Application Event Category: None Event ID: 0 Date: 24/09/2004 Time: 20:02:45 User: N/A Computer: DELL Description: The description for Event ID ( 0 ) in Source ( Application ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: Undefined subroutine &Slim::Web::RemoteStream::openRemoteStream called at C:/Program Files/SlimServer/server/Plugins/BBCNews.pm line 254. . # # $Id: BBCNews.pm,v 1.29 2003/12/08 12:30:08 kevin Exp $ # # Author: Kevin Walsh <kevin@cursor.biz> # # This is a complete rewrite of a similar module by Gordon Johnston # <gordonj@newswall.org.uk>. Gordon's BbcNews.pm version 0.2.1 was # dated October 2002 (http://newswall.org.uk/~slimp3/news-ticker.html). #
openRemoteStream crash is fixed in today's build.
Richard, any thoughts on this one?
I'm still seeing the same issue with the new server 5.3.1 and softsqueeze 1.5. I now notice what I possibly missed before which is that when the audio restarts this is always at the same time as the screen goes black momentarily when doing the LEFT<->RIGHT menu navigation in softsqueeze. It never happens with UP/DOWN menu navigation. Seems like this is associated with a disconnect happening between softsqueeze and the server as sometimes I do momentarily see the 'Problem: lost connection with the server message' in the softsqueeze display. Further investigation seems to show that I get the issue when using a wireless connection between the laptop running softsqueeze and the server but not when using a crossover ethernet cable. FYI in my setup both server and client are on a wirelessB network but speed is always 11Mbits/s as my house is very small. However, I've been using softsqueeze and the server in the wireless configuration for a long time and I've not had an issue prior to server release 5.3.0
This sounds like it is a problem caused by Softsqueeze disconnecting from the slimserver, but the question is what's causing the disconnect. It sounds like a few people on the discuss list are seeing this problem as well. To help debug this could you start Softsqueeze from the command prompt in windows (instructions are at http://softsqueeze.sourceforge.net/download.html). An errors will then be displayed in the window while it's running. If you could append the output to this bug then I'll see if I can work out what's happening.
I started from the command line and I do see debug messages saying that there is a disconnect. I now have my laptop where the client is running connected to the Slim Server via a crossover ethernet cable running at 100Mbits/s I have no issue with the Slimp3 itself, it works just fine. It's just SoftSqueeze that has the problem 5969 [AWT-EventQueue-0] WARN com.slim.softsqueeze.Config - Calling Config Listeners for key=excession.y_excession.egg val=567 old=641 24245 [SlimTCP] WARN com.slim.softsqueeze.SoftSqueeze - Lost contact with Slim Server 33599 [SlimTCP] WARN com.slim.softsqueeze.SoftSqueeze - Lost contact with Slim Server This is my environment: E:\Software\PC\SlimP3\5.3.1\softsqueeze>java -version java version "1.5.0" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0-b64) Java HotSpot(TM) Client VM (build 1.5.0-b64, mixed mode, sharing) Running under Windows 2000 Pro with a 700MHz IBM Thinkpad with 512MB of RAM
Sorry for the slow reply, but I have been away recently. I was hoping for some more useful information in the debug. So far this just proves that Softsqueeze is disconnecting from the slimserver, but does not indicate why. Could you please run Softsqueeze from the command line, as follows: 'java -Dlog=com.slim.softsqueeze.Protocol -jar SoftSqueeze.jar'. This will be very verbose but will hopefully give me the information I need to fix this. Thanks.
Thanks for sending me the debug output earlier. I have now had chance to look at this in detail, and still don't completely understand what is causing the disconnect. Could you please enable the 'slimproto' debugging in the slimserver and then send the slimserver log to me.
I have had some useful debug output from another effected user this evening. It looks like the slimproto connection is being disconnected when reading the body of a slimproto command (the header containing the command size has been received ok). Alice, are you running a firewall on your Windows 2000. If so does it log any events during the disconnects? Could you also confirm that the slimserver and softsqueeze are running on the same PC. Thanks.
Looking at the debug it does not appear that either the slimserver or Softsqueeze are dropping the connection, but this is a network or OS issue. Dean just committed a fix to the slimserver and squeezebox firmware to prevent the music restarting following a disconnect. I have updated Softsqueeze (now version 1.9) to work with this fix. Could you please the next nightly slimserver build (2004-10-19). The music should not restart, but you might still get lost connection with slimserver messages occassionally.
Richard, if you can't reproduce this still, please close.
This has been fixed for a while now.
Routine bug db maintenance; removing old versions which cause confusion. I apologize for the inconvenience.