PDA

View Full Version : softsqueeze stutters at the beginning of songs



mkosma
2005-09-05, 11:57
I'm still having odd problems with my setup. Most bothersome, I am experiencing a stutter / dropout / glitch at the beginning of tracks.

First, here's my config:

PC: Athlon64 3400+, 1GB ram, WinXP. NForce3 chipset/audio.
Java ver: 1.5.0_04 (as reported by softsqueeze)
Softsqueeze: 2.0b11 (runs on the same machine as slimserver)
Slimserver: 6.0.3 (reported by softsqueeze)
However, slimserver web interface reports as follows:
SlimServer Version 6.1.2 - 4157 - Windows XP - EN - cp1252
Audio buffer size: 128000
MP3 decoder: Java MP3 Plugin.
Screen saver: blank screen.
Network: wired 100Mbit ethernet, connected to Netgear wireless router for other PCs and the bridge to SB2.

My library consists of FLAC and MP3 tracks, about half and half.

I also have a wired SB2 connected to a Netgear wireless bridge.
Unfortunately someone else is always using the "real" sound system (connected to TV, DVD, xbox, etc.) so I am most often relegated to listening through my PC speakers.

Periodically, there is a (jarring) pause in the initial second or so of a track.

I can get this to happen pretty repeatably with MP3 files. I believe it has also happened with FLACs, but I am not sure and have not been able to reproduce it. So it could be an MP3-only problem.

It seems to happen at particular song transitions, and seems somewhat repeatable. For example, I'm listening to The Hold Steady, Separation Sunday (downloaded from eMusic - a fabulous album by the way). If I listen to track 2 and let it continue to track 3, I get a glitch (stutter) right at the begnning of track 3. However, if I hit next or prev track to advance to the beginning of track 3, it plays fine.

Not sure it's related, butafter playing a while the softsqueeze app seems to lock up and must be closed and restarted. Usually after I've been away from the computer.

I'm ready to devote whatever time and attention is required to get this fixed. Thanks (Richard presumably) in advance for the help!

mkosma
2005-09-07, 09:02
bump ... any help out there?

JJZolx
2005-09-07, 09:58
I'm still having odd problems with my setup. Most bothersome, I am experiencing a stutter / dropout / glitch at the beginning of tracks.
I noticed this happening a lot just yesterday while running SoftSqueeze connected across the Internet and a VPN connection from work to home. I was running the Random Play plugin and playing FLAC files converted to 160bps MP3. It also occasionally ceased playback completely - viewing the web server in a browser with Fishbone shows the progress bar moving, so SlimServer is still streaming when it happens. Usually just restarting the track or forwarding to the next one resumes the playback.

On a local network why not just run some other music manager/playback program connected to your library?

mkosma
2005-09-07, 18:20
1. I have seen the same pausing / freezing behavior running SoftSqueeze from work over a SSH link.

2. Given that I use the SB2, and softsqueeze at work, I prefer simply to use the same interface while at home, too. Also, I sometimes will be using softsqueeze synchronized with my SB2. I suppose I could use winamp for casual listening, but really, this should work, shouldn't it? Otherwise what's the point of softsqueeze?

mkosma
2005-09-09, 06:54
further info. I turned on Audio Buffer logging in Softsqueeze. A couple seconds before the end of a song that was playing, I had a pause/dropout. I immediately opened up the softsqueeze console window. The log is below. Three things of note:

1. the strm IO error / ConnectionException / connection refused error
2. the buffer underrun towards the end of the log
3. at the end of the track, softsqueeze's playback freezes. The display shows "now playing", but there's no audio, the audio output meters are frozen, and the next track never appears.

When I try to skip to forward/next track, I notice a similar strm IO error / ConnectionException at the end of the log. See below for details.


...
1063491 [AudioDecoder-5] DEBUG audiobuffer.verbose - avil R=6381568 W=6389181 A=7613
1063491 [AudioDecoder-5] DEBUG audiobuffer.verbose - buf R=6389181 W=6389181 #=7613
1063501 [AudioDecoder-5] DEBUG audiobuffer.verbose - avil R=6389181 W=6389181 A=0
1063501 [AudioDecoder-5] DEBUG audiobuffer.verbose - avil R=6389181 W=6389181 A=0
1063501 [AudioDecoder-5] DEBUG audiobuffer.verbose - audio buffer underrun
1063501 [AudioDecoder-5] DEBUG audiobuffer.verbose - avil R=6389181 W=6389181 A=0
1063501 [AudioDecoder-5] DEBUG audiobuffer.verbose - avil R=131840000 W=135343616 A=3503616
1063501 [AudioDecoder-5] DEBUG audiobuffer.verbose - free R=131840000 W=135343616 F=24384
1063501 [AudioDecoder-5] DEBUG audiobuffer.verbose - buf R=131840000 W=135343616 Buffer full, waiting ...
1064212 [AudioMixer-0] DEBUG audiobuffer.verbose - avil R=131840000 W=135343616 A=3503616
1064212 [AudioMixer-0] DEBUG audiobuffer.verbose - avil R=131840000 W=135343616 A=3503616
1064212 [AudioMixer-0] DEBUG audiobuffer.verbose - buf R=131968000 W=135343616 #=128000
1064222 [AudioDecoder-5] DEBUG audiobuffer.verbose - free R=131968000 W=135343616 F=152384
1064222 [AudioDecoder-5] DEBUG audiobuffer.verbose - free R=131968000 W=135471616 F=24384
1064222 [AudioDecoder-5] DEBUG audiobuffer.verbose - buf R=131968000 W=135471616 Buffer full, waiting ...
1064633 [SlimTCP-1] ERROR player - strm IO error
java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(Unknown Source)
at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at java.net.Socket.<init>(Unknown Source)
at java.net.Socket.<init>(Unknown Source)
at com.slim.softsqueeze.audio.Player.connect(Player.j ava:305)
at com.slim.softsqueeze.audio.Player.slimprotoCmd(Pla yer.java:198)
at com.slim.softsqueeze.Protocol.socketCommand(Protoc ol.java:369)
at com.slim.softsqueeze.Protocol.access$300(Protocol. java:34)
at com.slim.softsqueeze.Protocol$TcpSocket.run(Protoc ol.java:465)
1064633 [Player Status] DEBUG audiobuffer.verbose - avil R=6389181 W=6389181 A=0
1064633 [Player Status] DEBUG audiobuffer.verbose - avil R=131968000 W=135471616 A=3503616
1064763 [AudioMixer-0] DEBUG audiobuffer.verbose - avil R=131968000 W=135471616 A=3503616
1064763 [AudioMixer-0] DEBUG audiobuffer.verbose - avil R=131968000 W=135471616 A=3503616
1064763 [AudioMixer-0] DEBUG audiobuffer.verbose - buf R=132096000 W=135471616 #=128000
1064763 [AudioDecoder-5] DEBUG audiobuffer.verbose - free R=132096000 W=135471616 F=152384

...

1087857 [SlimTCP-1] DEBUG audiobuffer.verbose - avil R=135530496 W=135530496 A=0
1087857 [Player Status] DEBUG audiobuffer.verbose - avil R=6389181 W=6389181 A=0
1087857 [Player Status] DEBUG audiobuffer.verbose - avil R=135530496 W=135530496 A=0

...

1880387 [Player Status] DEBUG audiobuffer.verbose - avil R=135530496 W=135530496 A=0
1881388 [Player Status] DEBUG audiobuffer.verbose - avil R=6389181 W=6389181 A=0
1881388 [Player Status] DEBUG audiobuffer.verbose - avil R=135530496 W=135530496 A=0
1882390 [Player Status] DEBUG audiobuffer.verbose - avil R=6389181 W=6389181 A=0
1882390 [Player Status] DEBUG audiobuffer.verbose - avil R=135530496 W=135530496 A=0
1883391 [Player Status] DEBUG audiobuffer.verbose - avil R=6389181 W=6389181 A=0
1883391 [Player Status] DEBUG audiobuffer.verbose - avil R=135530496 W=135530496 A=0
1884393 [Player Status] DEBUG audiobuffer.verbose - avil R=6389181 W=6389181 A=0


...

2072292 [SlimTCP-1] ERROR player - strm IO error
java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(Unknown Source)
at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at java.net.Socket.<init>(Unknown Source)
at java.net.Socket.<init>(Unknown Source)
at com.slim.softsqueeze.audio.Player.connect(Player.j ava:305)
at com.slim.softsqueeze.audio.Player.slimprotoCmd(Pla yer.java:198)
at com.slim.softsqueeze.Protocol.socketCommand(Protoc ol.java:369)
at com.slim.softsqueeze.Protocol.access$300(Protocol. java:34)
at com.slim.softsqueeze.Protocol$TcpSocket.run(Protoc ol.java:465)

mkosma
2005-09-09, 06:57
oops, forgot to add this clarification: the above error occurred when playing a FLAC file, bitrate-limited/converted to mp3, over SSH tunneling from work. Softsqueeze version 2.0b11, Java 1.5.0_02, Primary Sound Driver / 128000 buffer / Java MP3 Plugin.

mkosma
2005-09-09, 07:12
Closed squeezebox, reopened, and went and replayed the same track (Angry Chair by Alice in Chains) and the same problem occurred. This time, here's the verbose player debug. Interestingly, it shows the freeze (repeating elapsedseconds=288) at the track end.

349510 [Player Status] DEBUG player.verbose - status=STMt fullness=35757 bytesRx=6389181 elapsedSeconds=264
350521 [Player Status] DEBUG player - decode: 1.0663032531738281 avail=11181 size=1048576
350521 [Player Status] DEBUG player - output: 96.62403464317322 avail=3408896 size=3528000
350521 [Player Status] DEBUG player.verbose - status=STMt fullness=11181 bytesRx=6389181 elapsedSeconds=265
351252 [AudioDecoder-6] DEBUG player.verbose - buffer underrun; audioStream=com.slim.softsqueeze.audio.AudioStream @1d98a isOpen=closed
351272 [AudioDecoder-6] DEBUG player - decode: 0.0 avail=0 size=1048576
351282 [AudioDecoder-6] DEBUG player - output: 96.62403464317322 avail=3408896 size=3528000
351282 [AudioDecoder-6] DEBUG player.verbose - status=STMd fullness=0 bytesRx=6389181 elapsedSeconds=266
351392 [SlimTCP-1] DEBUG player - audg leftLvl=99 rightLvl=99
351392 [SlimTCP-1] DEBUG player - httpRequest=GET /stream.mp3?player=98:86:a5:0e:be:6a HTTP/1.0



351392 [SlimTCP-1] DEBUG player - parsed strm: command=s format=109 crossfade=0 ipaddr=127.0.0.1 port=9000 autostart=true autostartThreshold=261120
351392 [SlimTCP-1] DEBUG player - connect: state 3
351392 [SlimTCP-1] DEBUG player - http connect: ipaddr=127.0.0.1 port=9000
352324 [Player Status] DEBUG player - decode: 0.0 avail=0 size=1048576
352324 [Player Status] DEBUG player - output: 98.29297065734863 avail=3467776 size=3528000
352324 [Player Status] DEBUG player.verbose - status=STMt fullness=0 bytesRx=6389181 elapsedSeconds=267
352334 [SlimTCP-1] ERROR player - strm IO error
java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(Unknown Source)
at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at java.net.Socket.<init>(Unknown Source)
at java.net.Socket.<init>(Unknown Source)
at com.slim.softsqueeze.audio.Player.connect(Player.j ava:305)
at com.slim.softsqueeze.audio.Player.slimprotoCmd(Pla yer.java:198)
at com.slim.softsqueeze.Protocol.socketCommand(Protoc ol.java:369)
at com.slim.softsqueeze.Protocol.access$300(Protocol. java:34)
at com.slim.softsqueeze.Protocol$TcpSocket.run(Protoc ol.java:465)
352334 [SlimTCP-1] DEBUG player - audg leftLvl=99 rightLvl=99
353325 [Player Status] DEBUG player - decode: 0.0 avail=0 size=1048576
353325 [Player Status] DEBUG player - output: 94.66485381126404 avail=3339776 size=3528000
353325 [Player Status] DEBUG player.verbose - status=STMt fullness=0 bytesRx=6389181 elapsedSeconds=268
354327 [Player Status] DEBUG player - decode: 0.0 avail=0 size=1048576
354327 [Player Status] DEBUG player - output: 87.40861415863037 avail=3083776 size=3528000
354327 [Player Status] DEBUG player.verbose - status=STMt fullness=0 bytesRx=6389181 elapsedSeconds=269
355328 [Player Status] DEBUG player - decode: 0.0 avail=0 size=1048576
355328 [Player Status] DEBUG player - output: 83.78049731254578 avail=2955776 size=3528000
355328 [Player Status] DEBUG player.verbose - status=STMt fullness=0 bytesRx=6389181 elapsedSeconds=270
356330 [Player Status] DEBUG player - decode: 0.0 avail=0 size=1048576
356330 [Player Status] DEBUG player - output: 80.15238046646118 avail=2827776 size=3528000
356330 [Player Status] DEBUG player.verbose - status=STMt fullness=0 bytesRx=6389181 elapsedSeconds=271
357331 [Player Status] DEBUG player - decode: 0.0 avail=0 size=1048576
357331 [Player Status] DEBUG player - output: 72.89614677429199 avail=2571776 size=3528000
357331 [Player Status] DEBUG player.verbose - status=STMt fullness=0 bytesRx=6389181 elapsedSeconds=272
358333 [Player Status] DEBUG player - decode: 0.0 avail=0 size=1048576
358333 [Player Status] DEBUG player - output: 69.2680299282074 avail=2443776 size=3528000
358333 [Player Status] DEBUG player.verbose - status=STMt fullness=0 bytesRx=6389181 elapsedSeconds=273
359334 [Player Status] DEBUG player - decode: 0.0 avail=0 size=1048576
359334 [Player Status] DEBUG player - output: 62.01179027557373 avail=2187776 size=3528000
359334 [Player Status] DEBUG player.verbose - status=STMt fullness=0 bytesRx=6389181 elapsedSeconds=274
360336 [Player Status] DEBUG player - decode: 0.0 avail=0 size=1048576
360336 [Player Status] DEBUG player - output: 58.383673429489136 avail=2059776 size=3528000
360336 [Player Status] DEBUG player.verbose - status=STMt fullness=0 bytesRx=6389181 elapsedSeconds=275
361337 [Player Status] DEBUG player - decode: 0.0 avail=0 size=1048576
361337 [Player Status] DEBUG player - output: 54.75555658340454 avail=1931776 size=3528000
361337 [Player Status] DEBUG player.verbose - status=STMt fullness=0 bytesRx=6389181 elapsedSeconds=276
362339 [Player Status] DEBUG player - decode: 0.0 avail=0 size=1048576
362339 [Player Status] DEBUG player - output: 47.49931991100311 avail=1675776 size=3528000
362339 [Player Status] DEBUG player.verbose - status=STMt fullness=0 bytesRx=6389181 elapsedSeconds=277
363340 [Player Status] DEBUG player - decode: 0.0 avail=0 size=1048576
363340 [Player Status] DEBUG player - output: 43.87120306491852 avail=1547776 size=3528000
363340 [Player Status] DEBUG player.verbose - status=STMt fullness=0 bytesRx=6389181 elapsedSeconds=278
364342 [Player Status] DEBUG player - decode: 0.0 avail=0 size=1048576
364342 [Player Status] DEBUG player - output: 40.243083238601685 avail=1419776 size=3528000
364342 [Player Status] DEBUG player.verbose - status=STMt fullness=0 bytesRx=6389181 elapsedSeconds=279
365343 [Player Status] DEBUG player - decode: 0.0 avail=0 size=1048576
365343 [Player Status] DEBUG player - output: 32.986849546432495 avail=1163776 size=3528000
365343 [Player Status] DEBUG player.verbose - status=STMt fullness=0 bytesRx=6389181 elapsedSeconds=280
366345 [Player Status] DEBUG player - decode: 0.0 avail=0 size=1048576
366345 [Player Status] DEBUG player - output: 29.35872972011566 avail=1035776 size=3528000
366345 [Player Status] DEBUG player.verbose - status=STMt fullness=0 bytesRx=6389181 elapsedSeconds=281
367346 [Player Status] DEBUG player - decode: 0.0 avail=0 size=1048576
367346 [Player Status] DEBUG player - output: 22.102494537830353 avail=779776 size=3528000
367346 [Player Status] DEBUG player.verbose - status=STMt fullness=0 bytesRx=6389181 elapsedSeconds=282
368348 [Player Status] DEBUG player - decode: 0.0 avail=0 size=1048576
368348 [Player Status] DEBUG player - output: 18.47437620162964 avail=651776 size=3528000
368348 [Player Status] DEBUG player.verbose - status=STMt fullness=0 bytesRx=6389181 elapsedSeconds=283
369349 [Player Status] DEBUG player - decode: 0.0 avail=0 size=1048576
369349 [Player Status] DEBUG player - output: 14.846257865428925 avail=523776 size=3528000
369349 [Player Status] DEBUG player.verbose - status=STMt fullness=0 bytesRx=6389181 elapsedSeconds=284
370351 [Player Status] DEBUG player - decode: 0.0 avail=0 size=1048576
370351 [Player Status] DEBUG player - output: 7.590022683143616 avail=267776 size=3528000
370351 [Player Status] DEBUG player.verbose - status=STMt fullness=0 bytesRx=6389181 elapsedSeconds=285
371352 [Player Status] DEBUG player - decode: 0.0 avail=0 size=1048576
371352 [Player Status] DEBUG player - output: 3.9619047194719315 avail=139776 size=3528000
371352 [Player Status] DEBUG player.verbose - status=STMt fullness=0 bytesRx=6389181 elapsedSeconds=286
372354 [Player Status] DEBUG player - decode: 0.0 avail=0 size=1048576
372354 [Player Status] DEBUG player - output: 0.33378684893250465 avail=11776 size=3528000
372354 [Player Status] DEBUG player.verbose - status=STMt fullness=0 bytesRx=6389181 elapsedSeconds=287
372364 [AudioMixer-0] DEBUG player.verbose - buffer underrun; audioStream=com.slim.softsqueeze.audio.AudioStream @1d98a isOpen=closed
373075 [AudioMixer-0] DEBUG player - decode: 0.0 avail=0 size=1048576
373075 [AudioMixer-0] DEBUG player - output: 0.0 avail=0 size=3528000
373075 [AudioMixer-0] DEBUG player.verbose - status=STMu fullness=0 bytesRx=6389181 elapsedSeconds=288
374076 [Player Status] DEBUG player - decode: 0.0 avail=0 size=1048576
374076 [Player Status] DEBUG player - output: 0.0 avail=0 size=3528000
374076 [Player Status] DEBUG player.verbose - status=STMt fullness=0 bytesRx=6389181 elapsedSeconds=288
375078 [Player Status] DEBUG player - decode: 0.0 avail=0 size=1048576
375078 [Player Status] DEBUG player - output: 0.0 avail=0 size=3528000
375078 [Player Status] DEBUG player.verbose - status=STMt fullness=0 bytesRx=6389181 elapsedSeconds=288
376079 [Player Status] DEBUG player - decode: 0.0 avail=0 size=1048576
376079 [Player Status] DEBUG player - output: 0.0 avail=0 size=3528000
376079 [Player Status] DEBUG player.verbose - status=STMt fullness=0 bytesRx=6389181 elapsedSeconds=288
377081 [Player Status] DEBUG player - decode: 0.0 avail=0 size=1048576
377081 [Player Status] DEBUG player - output: 0.0 avail=0 size=3528000
377081 [Player Status] DEBUG player.verbose - status=STMt fullness=0 bytesRx=6389181 elapsedSeconds=288
378082 [Player Status] DEBUG player - decode: 0.0 avail=0 size=1048576
378082 [Player Status] DEBUG player - output: 0.0 avail=0 size=3528000
378082 [Player Status] DEBUG player.verbose - status=STMt fullness=0 bytesRx=6389181 elapsedSeconds=288

MrC
2005-09-09, 10:21
There are too many variables here to reliably deduce the cause of the problem (home play, work play, synchronization). Lets try reducing these to fix one at a time.

What's your upload speed from your home network connection, and what bitrate is your player expecting at work?

I'm suspecting your work <-> home connection is not fat or reliable enough in both directions to handle the amount of data being pushed through. Test this by lowering the players bit rate as much as possible via the web interface.

For you home situation, it does seem like you are experiencing network troubles in general. Have you looked at any of your network stats to see what your packet loss is?

Finally, turn off synchronization during your tests until you get everything working properly. Synchronization over the wireless network does have trouble occasionally, and will cause exactly the behavior you describe. I've commented on this in a previous post some time ago.

mkosma
2005-09-09, 12:54
I understand what you're saying, but I think most of those variables are not in play.

1. sync is OFF for all devices. I have not used sync since I started trying to debug these problems. I only offered that as a good reason why I'd like softsqueeze to work, as opposed to abandoning it for winamp or some such on the local pc.

2. network problems seem unlikely. The problems occurring at the office seem identical to the problems occuring when softsqueeze is running on the same PC as slimserver. However ...

3. I admit, that there could be different things going on, and the logs I generated today in the office. I will try to generate a similar set of logs on the home PC, now that I know how to do it. That should rule out network problems altogether, I would think.

4. how do I check packet loss? could that be an issue even in the situation under #2 above?

5. the logs I attached for Angry Chair, which is shown in the squeezebox web interface as a 178kbps VBR MP3 file. It's not high enough to be bitrate limited (now set at 320kbps).

6. I'm not sure if this is the best way to test the bandwidth, but I used filezilla over sftp to download a few files. Download speed from home->work seems fine -- e.g., I can download a FLAC file of size 34,882,445 bytes in 14:42 minutes (about 40 KB/sec).

MrC
2005-09-09, 14:13
I understand what you're saying, but I think most of those variables are not in play.

1. sync is OFF for all devices. I have not used sync since I started trying to debug these problems. I only offered that as a good reason why I'd like softsqueeze to work, as opposed to abandoning it for winamp or some such on the local pc.Ok, good.


2. network problems seem unlikely. The problems occurring at the office seem identical to the problems occuring when softsqueeze is running on the same PC as slimserver. However ...Oh, really?
352334 [SlimTCP-1] ERROR player - strm IO error
java.net.ConnectException: Connection refused: connect


3. I admit, that there could be different things going on, and the logs I generated today in the office. I will try to generate a similar set of logs on the home PC, now that I know how to do it. That should rule out network problems altogether, I would think.
I think you also have a different version of Java as well. Too many variables.


4. how do I check packet loss? could that be an issue even in the situation under #2 above?Abolutely! A noisy cable, ethernet jabber, excessive retransmits all will affect your playback. On Windows, netstat -se in a command window will give you ethernet stats.


5. the logs I attached for Angry Chair, which is shown in the squeezebox web interface as a 178kbps VBR MP3 file. It's not high enough to be bitrate limited (now set at 320kbps).

6. I'm not sure if this is the best way to test the bandwidth, but I used filezilla over sftp to download a few files. Download speed from home->work seems fine -- e.g., I can download a FLAC file of size 34,882,445 bytes in 14:42 minutes (about 40 KB/sec).
Your 40KB/sec is 320kbps. That would be an average over 14 minutes. You are likely not getting 320kbps sustained, but rather are bursting higher at times, and getting starved at others. There are likely to be stalls where you get far less than your stated average. And timeouts with ftp are much less significant than with streaming, high-priority data for audio or video.

But again, we're bringing in too many variables. Bottom line is that you have trouble with connections early on in your home network. Try simplifying everything. Configure just your server PC and your SB2 wired, without anything in the mix including ssh. When you start your playback, monitor process time with task manager. See what's kicking in. Perhaps a firewall is taking time to allow the connection and stuttering.

If that all works fine, then start adding items one by one.

mkosma
2005-09-09, 19:53
cool. thanks for the help. I will continue working on this over the weekend and report back. Dialing down the bitrate a bunch for internet softsqueeze sounds like a necessary step to fixing the office connection, at least.

mkosma
2005-09-09, 19:56
by the way, netstat -se says this. Anything jump out at you?

Interface Statistics

Received Sent

Bytes 568788398 1225607002
Unicast packets 1167277 1300623
Non-unicast packets 6870 680
Discards 0 0
Errors 0 0
Unknown protocols 46

IPv4 Statistics

Packets Received = 1168773
Received Header Errors = 0
Received Address Errors = 7
Datagrams Forwarded = 0
Unknown Protocols Received = 0
Received Packets Discarded = 24
Received Packets Delivered = 1168749
Output Requests = 1298949
Routing Discards = 0
Discarded Output Packets = 0
Output Packet No Route = 0
Reassembly Required = 0
Reassembly Successful = 0
Reassembly Failures = 0
Datagrams Successfully Fragmented = 0
Datagrams Failing Fragmentation = 0
Fragments Created = 0

ICMPv4 Statistics

Received Sent
Messages 1 1
Errors 0 0
Destination Unreachable 1 1
Time Exceeded 0 0
Parameter Problems 0 0
Source Quenches 0 0
Redirects 0 0
Echos 0 0
Echo Replies 0 0
Timestamps 0 0
Timestamp Replies 0 0
Address Masks 0 0
Address Mask Replies 0 0

TCP Statistics for IPv4

Active Opens = 671
Passive Opens = 321
Failed Connection Attempts = 2
Reset Connections = 194
Current Connections = 23
Segments Received = 968795
Segments Sent = 1092142
Segments Retransmitted = 8584

UDP Statistics for IPv4

Datagrams Received = 199903
No Ports = 82
Receive Errors = 13
Datagrams Sent = 198305

MrC
2005-09-09, 20:51
Your discards and errors are 0, so your cable and physical connectections seem fine. That's good.

I don't like these:

IPv4 Statistics
Unknown protocols 46

TCP Statistics for IPv4
Segments Retransmitted = 8584

You have about just under 1% of your TCP segments requiring restransmission. What we can't tell is if this is happening evenly distributed over time, or all at once (eg. during your SB2 play). This basically means a segment of data had to be retransmitted because TCP did not receive an acknowledgement within a certain time frame - hence TCP retransmits. This leads some credibility to packet loss and/or occasionally high latency. If it is evenly distributed over time, its less troublesome.

What you could do is reboot, run netstat -se 1, start your SB and watch the values change.

mkosma
2005-09-09, 21:30
I'll try a fresh boot and netstat.

In the process tonight, I noticed a ton of packets in my firewall log, some being blocked, from ip addr 0.0.0.0. Turns out the mac address is that of my xerox printer. It's connected over tcp but spewing netware, netbeui, and appletalk, and a bunch of other types of junk. So I turned off all that in the printer. Unfortunately, that made no difference - the problem is still occurring.

So I was able to generate an error log when the problem occurs at home, running local sofsqueeze as originally described. I have attached the log as a text file. I turned on all debug options except graphics and skin.

The error occurred right at the beginning of track 2. I'm not seeing much in the log at that point. Conceivably the problem could have occurred earlier, so I've attached a few seconds prior. When track 2 started, after 00:01 showed up on the timer and before 00:02, the playback paused or stuttered briefly.

Note I've truncated a bunch of very long "tcp recv: grfe 0 0 ..." lines before attaching this log. The log file is attached, rather than pasting since it's so long. Also, had to truncate ".verbose" to ".v" and all audiobuffer.verbose "avil" lines to "... avil ...". Not sure what if anything is important here.

MrC
2005-09-09, 21:46
A Src IP of 0.0.0.0 would likely be a DHCP request. A device that does not yet have an IP address will send this out, with a destination of the 255.255.255.255 address. A listening DHCP server will respond. But this should really only happen when the printer's network stack is started and its acquiring an address.

Many network printers have support for several protocols - just disable those that you don't want.

I don't see anything obvious in your log - just a bunch of ring buffer management output.

You could try another test - someone could use softsqueeze to connect to your server to see if there are softsqueeze playback problems.

mkosma
2005-09-15, 09:27
Well, my intermittent problems have become more intermittent. I haven't had too much time to test, but the stuttering at beginning of songs seems improved.

However, I am still getting the occasional "freeze" in softsqueeze over the internet. Today, after flawlessly playing about 20 songs, the player froze right at the end of a track. Any ideas, based on what showed up (see below) in the softsqueeze console?

0 [AudioMixer-0] WARN javasound - Java Sound Audio buffer underrun bufAvail=3442176
639183 [AudioMixer-0] WARN javasound - Java Sound Audio buffer underrun bufAvail=3512320
794037 [SlimTCP-1] ERROR player - strm IO error
java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(Unknown Source)
at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at java.net.Socket.<init>(Unknown Source)
at java.net.Socket.<init>(Unknown Source)
at com.slim.softsqueeze.audio.Player.connect(Player.j ava:305)
at com.slim.softsqueeze.audio.Player.slimprotoCmd(Pla yer.java:198)
at com.slim.softsqueeze.Protocol.socketCommand(Protoc ol.java:369)
at com.slim.softsqueeze.Protocol.access$300(Protocol. java:34)
at com.slim.softsqueeze.Protocol$TcpSocket.run(Protoc ol.java:465)

mkosma
2005-09-15, 09:37
I just tried again, playing the same song. At its end, playback froze. There was no error in console this time. However, I was running netstat -se in another ssh window. Although there's a slowly increasing number of "Segments Retransmitted" the number was constant for the last minute or so of the track that was playing.

mkosma
2005-09-15, 10:08
(by the way I am now running java 1.5.0_04)

Ok, now here is the debug output at the end of the track where it freezes (elapsed=233->234):

216283 [Player Status] DEBUG player - decode: 0.0 avail=0 size=1048576
216283 [Player Status] DEBUG player - output: 0.0 avail=0 size=3528000
216283 [Player Status] DEBUG player.verbose - status=STMt fullness=0 bytesRx=4936334 elapsedSeconds=233
216283 [Player Status] DEBUG slimproto - tcp send: STAT length=41
216504 [AudioMixer-0] DEBUG player.verbose - buffer underrun; audioStream=com.slim.softsqueeze.audio.AudioStream @5a67c9 isOpen=closed
216504 [AudioMixer-0] DEBUG javasound - drain line inState=2
217167 [AudioMixer-0] DEBUG player - decode: 0.0 avail=0 size=1048576
217167 [AudioMixer-0] DEBUG player - output: 0.0 avail=0 size=3528000
217167 [AudioMixer-0] DEBUG player.verbose - status=STMu fullness=0 bytesRx=4936334 elapsedSeconds=234
217167 [AudioMixer-0] DEBUG slimproto - tcp send: STAT length=41
217217 [AudioMixer-0] DEBUG javasound - audio mixer paused (stopping player) available=0
217217 [AudioMixer-0] DEBUG javasound - audio mixer paused (waiting)
218171 [Player Status] DEBUG player - decode: 0.0 avail=0 size=1048576
218171 [Player Status] DEBUG player - output: 0.0 avail=0 size=3528000
218171 [Player Status] DEBUG player.verbose - status=STMt fullness=0 bytesRx=4936334 elapsedSeconds=234

mkosma
2005-09-15, 12:51
Hmm. One more datapoint. I thought I might try to set up tunneling through Putty instead of through the SoftSqueeze interface. So I reset Softsqueeze to connect to localhost:9000 and 3483, and turned off the SSH Tunnel checkbox. Then I set putty to tunnel 9000 and 3483, and opened up a putty window.

So far, so good. I have been listening for quite a while now without any freeze-ups. I'll continue to monitor and report, keeping my fingers crossed.

mkosma
2005-09-15, 13:17
Well ... still no freezing. However, I did get a stutter at the beginning of a song. This is what showed up in the debug window:

672972 [AudioMixer-0] WARN javasound - Java Sound Audio buffer underrun bufAvail=3470848
672982 [AudioDecoder-4] WARN javasound - AudioDecoder could not write buf to outputBuffer

bernt
2005-09-15, 23:17
Had the exact same problem so I kicked out my old Alcatel ADSL modem and my Cisco PIX and replaced it with a Netgear all in one solution.

Now it just goes on and on and on.... :-)

Using Softsqueeze at work with SSH over a 512kb ADSL connection and FLAC converted to 192kb mp3.

And belive it or not, slimserver and the SSH server is running on Windows XP Home and have never crashed since I upgraded to Slimserver 6.1.2.

mkosma
2005-09-16, 00:14
huh. I have a newish netgear router connected to an old motorola cable modem. I wonder if replacing the cable modem might be worthwhile?

MrC
2005-09-16, 09:51
I'm curious about a setting - try toggling Compression in your putty ssh settings.

mkosma
2005-09-16, 11:29
Ok ... done.

and ... I listened to a bunch of tracks that used to freeze up, and so far have heard no problems at all.

Was your theory that turning compression on might cause problems? or eliminate more problems?

MrC
2005-09-16, 11:55
Oh... you're testing me! :-)

Glad things are working.

Compression in such protocols often leads to stuttering, until enough data is able to burst. Also, since your music data is compressed already, there's probably no gain in compressing more, and can be harmful.

But it can work the other way too, in that if you have a problematic line, compression can assist, at the expense of some early latency, that data transfers are more reliable.

My guess what that you had it enabled, but that's not the putty default as I recall.

mkosma
2005-09-19, 06:50
Nope. compression was disabled, but changing it made no difference.

So - for now, I guess I am okay. Rather than using the SSH settings built into softsqueeze, I run putty first, configured to tunnel the necessary local ports. It's behaving much better this way, although in theory there should be no difference.

Would be nice not to have to run putty in background, but really that's not such a big deal. Possibly once Richard frees up he may have some additional ideas about this.

monty

mkosma
2005-09-28, 12:40
I'm not certain but I am now suspicious that this freezing-at-song-end is a server-side problem. Reason being, I spent some time listening to music on the SB2 hardware. Played fine for a while, but then it did exactly the same thing as I was experiencing on softsqueeze: it froze right at the end of a song, and wouldn't advance to the next track, with everything on the display indicating that the SB2 thought it was still playing (although track time was not advancing).

Any further thoughts on how to debug this problem?

MrC
2005-09-28, 12:52
How about updating to the latest slimserver and installing the network health plugin/patch. Search the forums for this update.

This will provide you with a page of network health, buffer fullness, latencies, etc. This might be useful.

Triode
2005-09-28, 14:17
I'm afraid at present this requires you to patch slimserver. If this doesn't make any sense to you, you probably don't want to do
it!

However assuming we get the patch in the main slimserver I would be interested to see whether it shows any issues with network
buffers etc.

If your willing to patch - look for posts on the development list in my name....

>
> How about updating to the latest slimserver and installing the network
> health plugin/patch. Search the forums for this update.
>
> This will provide you with a page of network health, buffer fullness,
> latencies, etc. This might be useful.
>
>
> --
> MrC
>

mkosma
2005-09-28, 19:23
Okay. I assume this means:

1. upgrade from current 6.1.2 to latest 6.2 nightly build
2. apply the perfmon.diff patch from perfmon.zip
3. install the plugin from health.zip

Been a while since I was a coder but I'm not afraid to try.

My main question is, how do I do #2? I have Gnu Patch ver. 2.5 on my system, I am guessing that's what's needed.

I assume that #3 simply involves extracting to match "plugins" with c:\program files\slimserver\server\plugins.

MrC
2005-09-28, 20:57
You've got it. Use patch -p0 < perfomon.diff from the server directory. Then start the slimserver script. The rest should come from the health post where the plugin was announced.

Triode
2005-09-29, 10:23
You also need to install Active Perl as you are on windows and you need perl installed to do any changing of the server code.

----- Original Message -----
From: "MrC" <MrC.1w3qtz (AT) no-mx (DOT) forums.slimdevices.com>
To: <discuss (AT) lists (DOT) slimdevices.com>
Sent: Thursday, September 29, 2005 4:57 AM
Subject: [slim] Re: softsqueeze stutters at the beginning of songs


>
> You've got it. Use patch -p0 < perfomon.diff from the server directory.
> Then start the slimserver script. The rest should come from the health
> post where the plugin was announced.
>
>
> --
> MrC
>

mkosma
2005-09-29, 10:51
oh, don't worry, I couldn't live without perl... but a good point for future reference.

mkosma
2005-10-02, 21:52
Okay, tried to apply the (09-27) perfmon.diff patch to the latest (10-02) nightlies. Here's what happened:

$ patch -p0 -i perfmon.diff
patching file `Slim/Utils/PerfMon.pm'
Assertion failed: hunk, file patch.c, line 321

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.


Any ideas what's up? My patch reports:

C:\Documents and Settings\Monty>patch -v
patch 2.5
Copyright 1988 Larry Wall
Copyright 1997 Free Software Foundation, Inc.

This program comes with NO WARRANTY, to the extent permitted by law.
You may redistribute copies of this program
under the terms of the GNU General Public License.
For more information about these matters, see the file named COPYING.

written by Larry Wall with lots o' patches by Paul Eggert

mkosma
2005-10-02, 22:01
fyi, d/l'd the latest gnupatch, and got basically the same error message...

markonu
2005-10-03, 00:33
Hi. I read your post and I think I got kind of the same type of problem
My installation
I got 14 SB2 connected to one slimserver
My network is a cisco network

Slimserver is running on a powerfull windows 2003
Symptom : All the SB2 are playing the same album.And sometimes one of the SB2 stop playing when a new song start.

I find a way to crash one of my SB2 each time: all the SB2 are in the same room, so i can command them with one remote : i just have to put it off and on , then press play , and one or two SB2 don't start. If i try again , the non playing SB2 play the song but another SB2 don't start.

One other thing : i tried to slove my problem with installing an other server this time on windows XP ( same network / same SB2 / same network cables) and it worked
but the performance on windows XP with 14 SB2 is not as good as windows 2003. So if you can solve your problem , i am interested with a solution

thanks

dean
2005-10-03, 08:22
Markonu,

Are the two players that are being controlled both receiving signals
from the remote control? This would mean that when you press play on
two synced players, the group is getting two play commands, possibly
when they are displaying different things. Is this the case?

-dean

On Oct 3, 2005, at 12:33 AM, markonu wrote:

>
> Hi. I read your post and I think I got kind of the same type of
> problem
> My installation
> I got 14 SB2 connected to one slimserver
> My network is a cisco network
>
> Slimserver is running on a powerfull windows 2003
> Symptom : All the SB2 are playing the same album.And sometimes one of
> the SB2 stop playing when a new song start.
>
> I find a way to crash one of my SB2 each time: all the SB2 are in the
> same room, so i can command them with one remote : i just have to put
> it off and on , then press play , and one or two SB2 don't start. If i
> try again , the non playing SB2 play the song but another SB2 don't
> start.
>
> One other thing : i tried to slove my problem with installing an other
> server this time on windows XP ( same network / same SB2 / same
> network
> cables) and it worked
> but the performance on windows XP with 14 SB2 is not as good as
> windows
> 2003. So if you can solve your problem , i am interested with a
> solution
>
> thanks
>
>
> --
> markonu
>

Triode
2005-10-03, 10:49
Did you try "patch -p0 < perfmon.diff" ?

Otherwise I've no idea I'm afraid about this.


---- Original Message -----
From: "mkosma" <mkosma.1wb81n (AT) no-mx (DOT) forums.slimdevices.com>
To: <discuss (AT) lists (DOT) slimdevices.com>
Sent: Monday, October 03, 2005 5:52 AM
Subject: [slim] Re: softsqueeze stutters at the beginning of songs


>
> Okay, tried to apply the (09-27) perfmon.diff patch to the latest
> (10-02) nightlies. Here's what happened:
>
> $ patch -p0 -i perfmon.diff
> patching file `Slim/Utils/PerfMon.pm'
> Assertion failed: hunk, file patch.c, line 321
>
> This application has requested the Runtime to terminate it in an
> unusual way.
> Please contact the application's support team for more information.
>
>
> Any ideas what's up? My patch reports:
>
> C:\Documents and Settings\Monty>patch -v
> patch 2.5
> Copyright 1988 Larry Wall
> Copyright 1997 Free Software Foundation, Inc.
>
> This program comes with NO WARRANTY, to the extent permitted by law.
> You may redistribute copies of this program
> under the terms of the GNU General Public License.
> For more information about these matters, see the file named COPYING.
>
> written by Larry Wall with lots o' patches by Paul Eggert
>
>
> --
> mkosma
>

mkosma
2005-10-03, 11:48
Indeed, I tried patch using the redirect as well as the -i (input file) command line.

Should the patch work against the latest nightlies? If not, is there a different version of the 6.2 build I can get and should try?

Also - what version of patch are you using? is it gnu patch? if not perhaps there's a syntax difference in play...

Triode
2005-10-03, 11:57
I'm using linux:
patch -v
patch 2.5.9
Copyright (C) 1988 Larry Wall
Copyright (C) 2003 Free Software Foundation, Inc.

patch -p0 <perfmon.diff
patching file Slim/Utils/PerfMon.pm
patching file Slim/Utils/Timers.pm

The diff should work for a recent nightly of 6.2.

Anyway, don't get you hopes up that this will fix your problem, it simply gives some more diagnosis information which could help..

----- Original Message -----
From: "mkosma" <mkosma.1wcapc (AT) no-mx (DOT) forums.slimdevices.com>
To: <discuss (AT) lists (DOT) slimdevices.com>
Sent: Monday, October 03, 2005 7:48 PM
Subject: [slim] Re: softsqueeze stutters at the beginning of songs


>
> Indeed, I tried patch using the redirect as well as the -i (input file)
> command line.
>
> Should the patch work against the latest nightlies? If not, is there a
> different version of the 6.2 build I can get and should try?
>
> Also - what version of patch are you using? is it gnu patch? if not
> perhaps there's a syntax difference in play...
>
>
> --
> mkosma
>

mkosma
2005-10-03, 14:44
Understood. Would you be willing to zip and mail me the patched perfmon.pm and timers.pm files? if so, you can send it to (mkosma at gmail dot com)

monty

Triode
2005-10-03, 16:29
Please try tomorrow's nightly version of 6.2 - it should include the patch and plugin.

[But don't get your expectations up that it fixes the problem!]

Adrian
>
> Understood. Would you be willing to zip and mail me the patched
> perfmon.pm and timers.pm files? if so, you can send it to (mkosma at
> gmail dot com)

mkosma
2005-10-03, 16:43
understood! I will try tomorrow's. I don't expect it to fix the problem, but at this point I haven't made any progress towards a solution and more information is the only thing that seems likely to help.

mkosma
2005-10-04, 14:14
Okay, new info here.

First, current versions. From softsqueeze:
Java: 1.5.0_04
Softsqueeze: 2.0b10 (reverted from b11, but hasn't mattered)
Slimserver version: blank (but it's the 10/3 nightly build of 6.2)

Problems are no different than before. I tried my most reliable error-gen combination, playing track 2 then track 3 of The Hold Steady's Separation Sunday, track 3 always pauses at the beginning. And it did it here - stops briefly then resumes.

First: Java console error message:

0 [SlimTCP-1] ERROR slimproto - Exception processing frame
java.lang.NullPointerException
at com.slim.softsqueeze.audio.AudioMixer.setVolume(Au dioMixer.java:176)
at com.slim.softsqueeze.audio.AudioMixer.setVolume(Au dioMixer.java:168)
at com.slim.softsqueeze.audio.Player.slimprotoCmd(Pla yer.java:241)
at com.slim.softsqueeze.Protocol.socketCommand(Protoc ol.java:369)
at com.slim.softsqueeze.Protocol.access$300(Protocol. java:34)
at com.slim.softsqueeze.Protocol$TcpSocket.run(Protoc ol.java:465)
79308 [SlimTCP-1] WARN softsqueeze - Lost contact with Slim Server

Second, warnings in softsqueeze console:

3963725 [AudioMixer-0] WARN javasound - Java Sound Audio buffer underrun bufAvail=3527168
3963755 [AudioDecoder-18] WARN javasound - AudioDecoder could not write buf to outputBuffer
3992262 [AudioMixer-0] WARN javasound - Java Sound Audio buffer underrun bufAvail=3328000
3992262 [AudioDecoder-19] WARN javasound - AudioDecoder could not write buf to outputBuffer
4168302 [AudioMixer-0] WARN javasound - Java Sound Audio buffer underrun bufAvail=3383296
5880319 [AudioMixer-0] WARN javasound - Java Sound Audio buffer underrun bufAvail=3416576
5880319 [AudioDecoder-29] WARN javasound - AudioDecoder could not write buf to outputBuffer
6122152 [AudioMixer-0] WARN javasound - Java Sound Audio buffer underrun bufAvail=3470336

more in next msg...

mkosma
2005-10-04, 14:16
And, newly available, here's the output of the perfmon display, having reset counters at start of track 2. Note I deleted the summary and some explanatory text.

Player Performance : Office_Softsqueeze

Buffer Fullness
< 10 : 62 : 33% ################
< 20 : 2 : 1%
< 30 : 1 : 1%
< 40 : 1 : 1%
< 50 : 2 : 1%
< 60 : 1 : 1%
< 70 : 2 : 1%
< 80 : 28 : 15% #######
< 90 : 42 : 23% ###########
< 100 : 45 : 24% ############
>=100 : 0 : 0%
max : 99.931717
min : -300.000000
avg : 3.117672

Control Connection
This graph shows the number of messages queued up to send to the player over the control connection. A measurement is taken every time a new message is sent to the player. Values above 1-2 indicate potential network congestion or that the player has become disconnected.
< 1 : 4 :100% ##################################################
< 2 : 0 : 0%
< 5 : 0 : 0%
< 10 : 0 : 0%
< 20 : 0 : 0%
>=20 : 0 : 0%
max : 0.000000
min : 0.000000
avg : 0.000000


Server Performance

Server Response Time
This graph shows the length of time between slimserver responding to requests from any player. It is measured in seconds. Lower numbers are better. If you notice response times of over 1 second this could lead to problems with audio performance.
The cause of long response times could be either other programs running on the server or slimserver processing a complex task.
< 0.002 : 3528 : 83% #########################################
< 0.005 : 565 : 13% ######
< 0.01 : 153 : 4% #
< 0.015 : 4 : 0%
< 0.025 : 10 : 0%
< 0.05 : 9 : 0%
< 0.1 : 3 : 0%
< 0.5 : 1 : 0%
< 1 : 0 : 0%
< 5 : 0 : 0%
>=5 : 0 : 0%
max : 0.196408
min : 0.000032
avg : 0.001350

Timer Accuracy
Slimserver uses a timer mechanism to trigger events such as updating the user interface. This graph shows how accurately each timer task is run relative to the time it was intended to be run. It is measured in seconds.
Timer tasks are scheduled by the server to run at some point in the future. As only one timer task can run at once and the server may also be performing other activity, timer tasks always run slightly after the time they are scheduled for. However if timer tasks run significantly after they are scheduled this can become noticable through delay in the user interface.
< 0.002 : 1374 : 91% #############################################
< 0.005 : 32 : 2% #
< 0.01 : 63 : 4% ##
< 0.015 : 39 : 3% #
< 0.025 : 1 : 0%
< 0.05 : 2 : 0%
< 0.1 : 1 : 0%
< 0.5 : 0 : 0%
< 1 : 0 : 0%
< 5 : 0 : 0%
>=5 : 0 : 0%
max : 0.085037
min : 0.000000
avg : 0.001172

Timer Task Duration
This graph shows how long each timer task runs for. It is measured in seconds. If any timer task takes more than 0.5 seconds this is likely to impact the user interface.
< 0.002 : 1510 :100% #################################################
< 0.005 : 0 : 0%
< 0.01 : 0 : 0%
< 0.015 : 0 : 0%
< 0.025 : 0 : 0%
< 0.05 : 0 : 0%
< 0.1 : 1 : 0%
< 0.5 : 1 : 0%
< 1 : 0 : 0%
< 5 : 0 : 0%
>=5 : 0 : 0%
max : 0.102007
min : 0.000043
avg : 0.000620

MrC
2005-10-04, 14:20
The problem seem to show itself here:

Buffer Fullness
< 10 : 62 : 33% ################

If your buffer is less than 10% full 1/3 of the time, I think you can see what's going on.

Triode
2005-10-04, 14:26
This suggests to me that the server is healthy. The only thing here is the high amount of <10% buffer fill - but we can't be sure
whether this is real or just softsqueeze reporting erroneous values.

>
> And, newly available, here's the output of the perfmon display, having
> reset counters at start of track 2. Note I deleted the summary and
> some explanatory text.

mkosma
2005-10-04, 14:36
As I mentioned in another thread, one odd thing is that I'm seeing in the buffer % display and in these charts frequently high negative values (-100% to -200%). Not entirely sure if correlated to the skip behavior.

Triode
2005-10-04, 15:03
Mkosma,

Looking at the buffer fill returned from softsqueeze it just looks like the non playing condition returns a big negative number.
The rest looks resonable.

If you edit Slim/Player/Client.pm to change the line:
$client->[77] = Slim::Utils::PerfMon->new("Buffer Fullness ($id)", [10,20,30,40,50,60,70,80,90,100]);

To be:
$client->[77] = Slim::Utils::PerfMon->new("Buffer Fullness ($id)", [0,10,20,30,40,50,60,70,80,90,100]);

Then this should add an extra bucket to the buffer log which catches all the negative numbers. This means the average is still
wrong but the rest of the values should be accurate.

What does it look like then?

Adrian
[based on other message I think the java sound errors are the ones to look at, but I don't really understand them at present..]

----- Original Message -----
From: "mkosma" <mkosma.1wed8n (AT) no-mx (DOT) forums.slimdevices.com>
To: <discuss (AT) lists (DOT) slimdevices.com>
Sent: Tuesday, October 04, 2005 10:36 PM
Subject: [slim] Re: softsqueeze stutters at the beginning of songs


>
> As I mentioned in another thread, one odd thing is that I'm seeing in
> the buffer % display and in these charts frequently high negative
> values (-100% to -200%). Not entirely sure if correlated to the skip
> behavior.
>
>
> --
> mkosma
>

mkosma
2005-10-04, 16:05
I'll try that. The buffer fullness indicator frequently shows a large negative number, even when playback is working just fine. Need to see if the SB2 does that....

Triode
2005-10-04, 16:11
Don't try that! I've just fixed (hopefully) the negative numbers for softsqueeze - please try the latest 6.2 instead!

Adrian
----- Original Message -----
From: "mkosma" <mkosma.1weheo (AT) no-mx (DOT) forums.slimdevices.com>
To: <discuss (AT) lists (DOT) slimdevices.com>
Sent: Wednesday, October 05, 2005 12:05 AM
Subject: [slim] Re: softsqueeze stutters at the beginning of songs


>
> I'll try that. The buffer fullness indicator frequently shows a large
> negative number, even when playback is working just fine. Need to see
> if the SB2 does that....
>
>
> --
> mkosma
>

mkosma
2005-10-06, 09:19
Ok. Now using the 10/5/05 nightly. Softsqueeze buffer numbers are much more sensible. The behavior is no better. And I really do not think this is a network problem, as the same behavior occurs when softsqueeze and slimserver are running on the same machine.

Here is what I observe.

1. Buffer fullness climbs steadily from 0% to 100% almost exactly 30 seconds after the first track begins. It hovers at 94% or more once it has filled up.

2. When there are almost exactly 70 seconds remaining in the first track, buffer fullness starts starts steadily declining towards zero. It reaches zero with about 23 seconds remaining in track 1.

3. As soon as it hits zero, the buffer fullness starts climbing again (presumably starting to buffer the second track). When the first track ends, buffer fullness is already up to about 74%.

4. It plays the first 0.5 second or so of the second track, then it stutters or pauses for about 1/4 second.

5. After the stutter, I can hit "prev track" to restart track two. When I do that, I NEVER get a stutter. However, the display shows 0%, then 2%, then 0%, then 0%, then a steady climb to 100% fullness.


Other interesting data points discovered that possibly relate to BOTH of the problems I've been experiencing:

1. When I paused playback to check time remaining, I almost always get a stutter when I hit pause button again to resume play. Sounded very similar to the start-of-track stutter I've been experiencing.

2. I paused playback just as the buffer display reached 2%. The display then refreshed, showed 0%, and paused playback. I hit pause again to resume playback, and playback resumed. However, the buffer sat at 0% and REMAINED at zero. When the first track reached its end, Now Playing continued to show that it was being played, but the player never advanced to the second track. I hit "prev track" and it did start playing the first track again.

Here's the errors shown in the softsqueeze console. No debugging is turned on.

0 [AudioMixer-0] WARN javasound - Java Sound Audio buffer underrun bufAvail=3334144
406139 [AudioMixer-0] WARN javasound - Java Sound Audio buffer underrun bufAvail=3459584
406149 [AudioDecoder-8] WARN javasound - AudioDecoder could not write buf to outputBuffer0 [AudioMixer-0] WARN javasound - Java Sound Audio buffer underrun bufAvail=3334144
406139 [AudioMixer-0] WARN javasound - Java Sound Audio buffer underrun bufAvail=3459584
406149 [AudioDecoder-8] WARN javasound - AudioDecoder could not write buf to outputBuffer
427639 [AudioMixer-0] WARN javasound - Java Sound Audio buffer underrun bufAvail=3456000
427639 [AudioDecoder-9] WARN javasound - AudioDecoder could not write buf to outputBuffer
956568 [AudioMixer-0] WARN javasound - Java Sound Audio buffer underrun bufAvail=3287040
1199413 [AudioMixer-0] WARN javasound - Java Sound Audio buffer underrun bufAvail=3415852
1209727 [AudioMixer-0] WARN javasound - Java Sound Audio buffer underrun bufAvail=3456000
1209727 [AudioDecoder-13] WARN javasound - AudioDecoder could not write buf to outputBuffer
1450789 [AudioMixer-0] WARN javasound - Java Sound Audio buffer underrun bufAvail=3470336
1609908 [AudioMixer-0] WARN javasound - Java Sound Audio buffer underrun bufAvail=3472896
1664994 [AudioMixer-0] WARN javasound - Java Sound Audio buffer underrun bufAvail=3460816
1702326 [AudioMixer-0] WARN javasound - Java Sound Audio buffer underrun bufAvail=3479112

427639 [AudioMixer-0] WARN javasound - Java Sound Audio buffer underrun bufAvail=3456000
427639 [AudioDecoder-9] WARN javasound - AudioDecoder could not write buf to outputBuffer
956568 [AudioMixer-0] WARN javasound - Java Sound Audio buffer underrun bufAvail=3287040

mkosma
2005-10-06, 09:46
The other thing that to me discounts network issues is that this happens reliably and repeatably with certain tracks or combinations of tracks. Now none of those mp3 files appear to be particularly demanding - the problem doesn't occur with FLAC files run at full bandwidth.

Additional things I have noticed:

1. normally track 3 on this album stutters when it begins. I tried deleting track 2 from the playlist, so it goes 1->3 instead of 2->3. Result: No skip when track 3 starts.

2. next, I tried deleting track 3 from the playlist, so it goes 2->4 instead of 2->3. Result: SKIP when track 4 starts. So it appears that the bad behavior is being caused by something about the way track 2 ENDS, not how track 3 (or 4) BEGINS. (These are legal, licensed mp3 files downloaded from emusic.com.)

3. another oddity: after the buffer fullness drops to zero when track 2 is still playing, it starts climbing up again presumably buffering track 3. Since it is not emptying the buffered audio of track 3 - yet - it is very strange that the buffer fullness climbs then DROPS -- it goes 0% 2% 5% __4%__ 8%.

dean
2005-10-06, 09:55
What's the CPU load on your system during the stuttering?

On Oct 6, 2005, at 9:46 AM, mkosma wrote:

>
> The other thing that to me discounts network issues is that this
> happens
> reliably and repeatably with certain tracks or combinations of tracks.
> Now none of those mp3 files appear to be particularly demanding - the
> problem doesn't occur with FLAC files run at full bandwidth.
>
> Additional things I have noticed:
>
> 1. normally track 3 on this album stutters when it begins. I tried
> deleting track 2 from the playlist, so it goes 1->3 instead of 2->3.
> Result: No skip when track 3 starts.
>
> 2. next, I tried deleting track 3 from the playlist, so it goes 2->4
> instead of 2->3. Result: SKIP when track 4 starts. So it appears
> that the bad behavior is being caused by something about the way track
> 2 ENDS, not how track 3 (or 4) BEGINS. (These are legal, licensed mp3
> files downloaded from emusic.com.)
>
> 3. another oddity: after the buffer fullness drops to zero when track
> 2 is still playing, it starts climbing up again presumably buffering
> track 3. Since it is not emptying the buffered audio of track 3 - yet
> - it is very strange that the buffer fullness climbs then DROPS -- it
> goes 0% 2% 5% __4%__ 8%.
>
>
> --
> mkosma
>

mkosma
2005-10-06, 09:59
The pause behavior in my 12:19pm message appears to be bug 2169. See http://bugs.slimdevices.com/show_bug.cgi?id=2169

mkosma
2005-10-06, 10:07
Dean, I just generated the skip with the server pc running over vnc. CPU usage hovers around 10% and there are no real spikes of any significance when it occurs.

Note that it is perhaps inaccurate to describe this as "stuttering." Playback pauses for an instant, then resumes. Just once, not repeatedly like you'd expect if CPU or network load was interrupting playback. To me it sounds like a frame of silence is getting inserted into the playback buffer.

Triode
2005-10-06, 11:18
If you configure the server to decode mp3 to wav on the server, does this avoid the problem?

See http://forums.slimdevices.com/showthread.php?t=8385

Sounds to me that the java mp3 decoder used by softsqueeze doesn't like these files?

>
> The other thing that to me discounts network issues is that this happens
> reliably and repeatably with certain tracks or combinations of tracks.
> Now none of those mp3 files appear to be particularly demanding - the
> problem doesn't occur with FLAC files run at full bandwidth.
>

mrfantasy
2005-10-18, 13:08
It seems that SoftSqueeze, at least, is buffering a song at a time. I guess this would make sense if there was no playlist, but I'm playing either Random Mix lists (which load the next 10 songs so the server always knows the next song) or albums in linear play (again, the next song is predictable.) I'd expect the buffer to deplete in Shuffle play because the next song isn't determined until the current one ends, but it seems the server and player should not deplete the buffer after each song if it knows the next one. Interestingly, it starts filling again before the song completely ends, but it goes to zero first.


I don't know if this is working as designed, or if the SqueezeBox2 works this way as well, but keeping the buffer full whenever possible would improve performance over the Internet (I'm using Softsqueeze to access my home player over a congested Internet connection at work--frequently I can't stream 128k reliably, I'm running 96 now.)

mkosma
2005-10-18, 13:27
Good question.

Incidentally, I have been experiencing much fewer interruptions using JLayer for the MP3 decoder instead of Java MP3 Plugin in Softsqueeze. Not sure what the difference is, but the predictable pause-at-track-beginning behavior is no longer occurring since I made that switch.

What's the supposed advantage of the "Java MP3 Plugin" ?

mrfantasy
2005-10-19, 12:22
From the "Server & Network Health" page on the new Slimserver:

"Squeezebox2 uses a large buffer. This drains to 0 at the end of each track and then refills for the next track. You should only be concerned if the buffer fill is not high for the majority of the time a track is playing."

Is it safe to assume SoftSqueeze 2.0 works the same way?

--Mike


It seems that SoftSqueeze, at least, is buffering a song at a time. I guess this would make sense if there was no playlist, but I'm playing either Random Mix lists (which load the next 10 songs so the server always knows the next song) or albums in linear play (again, the next song is predictable.) I'd expect the buffer to deplete in Shuffle play because the next song isn't determined until the current one ends, but it seems the server and player should not deplete the buffer after each song if it knows the next one. Interestingly, it starts filling again before the song completely ends, but it goes to zero first.


I don't know if this is working as designed, or if the SqueezeBox2 works this way as well, but keeping the buffer full whenever possible would improve performance over the Internet (I'm using Softsqueeze to access my home player over a congested Internet connection at work--frequently I can't stream 128k reliably, I'm running 96 now.)

Triode
2005-10-19, 14:02
> "Squeezebox2 uses a large buffer. This drains to 0 at the end of each
> track and then refills for the next track. You should only be concerned
> if the buffer fill is not high for the majority of the time a track is
> playing."
>
> Is it safe to assume SoftSqueeze 2.0 works the same way?
>

Yes - if you enable buffer fullness display (player settings, now playing) and change to the now playing screen, you will see that
it drains to 0% and then refills just before the end of a track.

mkosma
2005-10-23, 16:55
bump ... welcome back Richard. I think where I left things in this thread, I was hoping for your opinion on the Java MP3 plugin and the error logs I have attached. Any thoughts?

rtitmuss
2005-10-24, 15:46
mkosma wrote:

>bump ... welcome back Richard.
>
Thanks :).

>Any thoughts?
>
>
Yeh, this threads got way too long, but I've learnt some useful netstat
commands on windows ;)


It looks like you have had several problems here, lets take each one in
turn:

1) SSH connection problems

From your early logs (for example in post #5) it is clear that you were
having some network problems. In that log a couple of clues exist:

1063491 [AudioDecoder-5] DEBUG audiobuffer.verbose - buf R=6389181
W=6389181 #=7613
1063501 [AudioDecoder-5] DEBUG audiobuffer.verbose - avil R=6389181
W=6389181 A=0
1063501 [AudioDecoder-5] DEBUG audiobuffer.verbose - avil R=6389181
W=6389181 A=0
1063501 [AudioDecoder-5] DEBUG audiobuffer.verbose - audio buffer underrun
1063501 [AudioDecoder-5] DEBUG audiobuffer.verbose - avil R=6389181
W=6389181 A=0
1063501 [AudioDecoder-5] DEBUG audiobuffer.verbose - avil R=131840000
W=135343616 A=3503616

Firstly the A=0 and audio buffer underrun shows that no bytes are
available to the mp3 decoder. The buffer then fills quickly with 3503616
bytes available in the buffer.

1064633 [SlimTCP-1] ERROR player - strm IO error
java.net.ConnectException: Connection refused: connect

Secondly this error shows that the tcp stream could not be opened for
the next track (Squeezebox/Softsqueeze opens a stream per track). This
explains why the play back stops, as the next track has not been opened.
I guess this should be handled more gracefully - I am not sure what a
SB2 does in this situation?

You then tried using putty for SSH, and as I understand things got
better. I would be interested if you could do another comparison now;
was it a software or network issue you originally saw?

I did have some problems with the Java SSH library when I originally
integrated it. The SSH 'window' is not correctly implemented, this only
effects streaming applications like Softsqueeze. I had to make some
workarounds, fixing the library would be a big job and other
applications are less sensitive to the bug.


2) Buffer underruns (see post #20, post #44)

672972 [AudioMixer-0] WARN javasound - Java Sound Audio buffer underrun
bufAvail=3470848
672982 [AudioDecoder-4] WARN javasound - AudioDecoder could not write
buf to outputBuffer

The 'Java Sound Audio buffer underrun' warning is probably not a
problem, it happens sometimes. I added the warning thinking it would
indicate a playback problem but this does not seem in my experience.

The 'AudioDecoder could not write ...' error is a problem. This
indicates that decoded audio has been lost, and will lead to a glitch in
the playback. Does this always happen with the same tracks in the same
place? I will fix this in the release of Softsqueeze - it is caused by
lazy coding on my part.


3) Network health plugin

Nice work Triode :)


4) MP3 Plugins

Your description of the buffer behavior (post #52) is good, just a shame
about audio glitch. Again I suspect this is due to the 'AudioDecoder
could not write ...' error.

As for Java MP3 plugin verses jlayer read the following post for
pros/cons (ignore all the it don't work posts!)
http://weblogs.java.net/blog/jonathansimon/archive/2004/11/suns_mp3_plugin.html.


The Java MP3 plugin does use less CPU to decode the tracks, but it is
not perfect. For example I had to make sure all meta data is parsed out
of the stream before passing it to the decoder, otherwise it can spin in
a tight loop.


Hope this helps. I will post a fix for the AudioDecoder in a day or two,
let me know if this helps.

Richard

mkosma
2005-10-24, 21:10
cool. once again, welcome back Richard.

1. I'll try again and report back on using the softsqueeze ssh connection directly once the new version is updated by you, in a couple days, to fix the other issues.

2. Buffer underruns: This problem appears to occur with Java MP3 Plugin, but not with JLayer. Particular tracks appear to give rise to this problem, and the glitch occurs at the very beginning of the *next* track played.

So ... let us know when the AudioDecoder fix is in, and I'll put it through the paces. Thanks so much for all your hard work, and I only hope I can repay the community over time. (I do have an idea or two kicking around....)

rtitmuss
2005-10-26, 14:48
mkosma wrote:

>So ... let us know when the AudioDecoder fix is in, and I'll put it
>through the paces.
>
Look for Softsqueeze 2.1 in the next nightlies. As well as fixing the
AudioDecoder bug I have replace the "buffer underrun" message. Instead
if you do get stutters in the play back you should get messages like this:

4221812 [AudioMixer-0] WARN javasound - Detected delay writing to audio
buffer readTook=0ms writeTook=843ms bufferedData=725ms

But let's just hope it now works ;)

Richard

adhawkins
2005-10-26, 14:55
Hi,

In article <435FF992.3050805 (AT) gmail (DOT) com>,
Richard Titmuss<richard.titmuss (AT) gmail (DOT) com> wrote:
> Look for Softsqueeze 2.1 in the next nightlies.

I'm currently tracking development through Subversion. What do I need to do
to keep up to date with Softsqueeze through this route?

Thanks

Andy

rtitmuss
2005-10-26, 15:07
Andy Hawkins wrote:

>
>I'm currently tracking development through Subversion. What do I need to do
>to keep up to date with Softsqueeze through this route?
>
>
svn update

Softsqueeze 2.1 is only on the trunk at the moment. I've asked Dan to
merge it to the branch (I don't seem to have permissions). Hopefully it
will make it across before the next nightlies.

Richard

adhawkins
2005-10-27, 01:11
Hi,

In article <435FFE10.2000606 (AT) gmail (DOT) com>,
Richard Titmuss<richard.titmuss (AT) gmail (DOT) com> wrote:
>>I'm currently tracking development through Subversion. What do I need to do
>>to keep up to date with Softsqueeze through this route?
>>
>>
> svn update

I tried this, but don't end up with the 'jar' file that it looks for when
you try to install SoftSqueeze (apologies if my terminology isn't right, I'm
a C++ guy, not a Java guy <g>).

Any steps required after doing the update to be able to use the player from
a server?

Thanks

Andy

rtitmuss
2005-10-27, 01:31
Andy Hawkins wrote:

>I tried this, but don't end up with the 'jar' file that it looks for when
>you try to install SoftSqueeze (apologies if my terminology isn't right, I'm
>a C++ guy, not a Java guy <g>).
>
>Any steps required after doing the update to be able to use the player from
>a server?
>
>
How are you trying to install Softsqueeze? It should just work from if
you use Java Webstart from the slimserver web interface. Otherwise
you'll find all the Softsqueeze files in
..../server/HTML/EN/html/softsqueeze and you can replace your existing
..jar file.

Richard

adhawkins
2005-10-27, 01:41
Hi,

In article <4360907C.1000804 (AT) gmail (DOT) com>,
Richard Titmuss<richard.titmuss (AT) gmail (DOT) com> wrote:
> How are you trying to install Softsqueeze? It should just work from if
> you use Java Webstart from the slimserver web interface. Otherwise
> you'll find all the Softsqueeze files in
> .../server/HTML/EN/html/softsqueeze and you can replace your existing
> .jar file.

That was my question. When I do a subversion checkout of the SoftSqueeze
code, I don't get a jar file...

Andy

rtitmuss
2005-10-27, 02:01
Andy Hawkins wrote:

>In article <4360907C.1000804 (AT) gmail (DOT) com>,
> Richard Titmuss<richard.titmuss (AT) gmail (DOT) com> wrote:
>
>
>>How are you trying to install Softsqueeze? It should just work from if
>>you use Java Webstart from the slimserver web interface. Otherwise
>>you'll find all the Softsqueeze files in
>>.../server/HTML/EN/html/softsqueeze and you can replace your existing
>>.jar file.
>>
>>
>
>That was my question. When I do a subversion checkout of the SoftSqueeze
>code, I don't get a jar file...
>
>
OK, understood. The Softsqueeze directory in svn is just the source
code. You'll find the binary .jar in the slimserver svn in the above
folder. Or if you have the Java JDK and apache ant installed you could
build the .jar file from the source (see the README).

Richard

adhawkins
2005-10-27, 02:43
Hi,

In article <43609766.7050902 (AT) gmail (DOT) com>,
Richard Titmuss<richard.titmuss (AT) gmail (DOT) com> wrote:
> OK, understood. The Softsqueeze directory in svn is just the source
> code. You'll find the binary .jar in the slimserver svn in the above
> folder. Or if you have the Java JDK and apache ant installed you could
> build the .jar file from the source (see the README).

Ah, OK I am tracking the server branch of 6.2 currently, so does that mean
any changes that are made in the 6.2 branch of Softsqueeze (assuming there
are any) will be applied when I do an update?

Thanks

Andy

rtitmuss
2005-10-27, 03:15
Andy Hawkins wrote:

>Ah, OK I am tracking the server branch of 6.2 currently, so does that mean
>any changes that are made in the 6.2 branch of Softsqueeze (assuming there
>are any) will be applied when I do an update?
>
>
Yes, that's right. Softsqueeze 2.1 was merged in r4860 on the 6.2
branch, so you should see it now.

Richard

adhawkins
2005-10-27, 03:43
Hi,

In article <4360A8CD.9060603 (AT) gmail (DOT) com>,
Richard Titmuss<richard.titmuss (AT) gmail (DOT) com> wrote:
> Yes, that's right. Softsqueeze 2.1 was merged in r4860 on the 6.2
> branch, so you should see it now.

Indeed I can :)

Thanks a lot.

Andy

kkitts
2005-10-27, 07:32
I have SS 6.1.1 installed and was using the SoftSqueeze that came with it. I've found some small gltiches in playback occasionally and thought I might download and run the new SoftSqueeze to see if it helps. Can I download the new jar file and just place it in the correct directory - and use it with the already installed SS installation that I have?

Will this version of SoftSqueeze be available for download on softsqueeze.sourceforge.net?

Many Thanks,

Kevin

rtitmuss
2005-10-27, 13:58
Can I download the new jar file and just place it in the correct directory - and use it with the already installed SS installation that I have?

Yes, usually you can do that. Sometimes I might add a new library, then you would need to reinstall Softsqueeze to get it to work.



Will this version of SoftSqueeze be available for download on softsqueeze.sourceforge.net?

No, but I am uploading the next version Softsqueeze 2.2 as I type ...

mkosma
2005-10-28, 11:53
what's new in 2.2? I'm getting a little confused, for the latest fixes, do I want to install from the Help page link in the latest nightly (6.5b1), or from the 6.2.1 nightly, or download softsqueeze from sourceforge?

JJZolx
2005-10-28, 16:10
what's new in 2.2? I'm getting a little confused, for the latest fixes, do I want to install from the Help page link in the latest nightly (6.5b1), or from the 6.2.1 nightly, or download softsqueeze from sourceforge?
If you're on a system that's not running SlimServer then just download the new version from SourceForge. I just downloaded the Windows EXE and the installer installed over top of the previous version. No sweat. And so far (about two hours) absolutely no stuttering.

MrC
2005-10-28, 16:19
what's new in 2.2? I'm getting a little confused, for the latest fixes, do I want to install from the Help page link in the latest nightly (6.5b1), or from the 6.2.1 nightly, or download softsqueeze from sourceforge?
In 2.2, Richard T. changed a congestion control algorithm (Nagel's algorithm). The only files that changed were the Java .jar and .jnlp files, available in the nightlies, svn, or Sourceforge.

JJZolx
2005-10-28, 16:33
And so far (about two hours) absolutely no stuttering.
Just got my first stutter. As before, near the beginning of the song, maybe 1-2 seconds into it.

Anyway, it's still working much better than it was.

LavaJoe
2005-10-29, 19:20
If you configure the server to decode mp3 to wav on the server, does this avoid the problem?

See http://forums.slimdevices.com/showthread.php?t=8385

Sounds to me that the java mp3 decoder used by softsqueeze doesn't like these files?

>
> The other thing that to me discounts network issues is that this happens
> reliably and repeatably with certain tracks or combinations of tracks.
> Now none of those mp3 files appear to be particularly demanding - the
> problem doesn't occur with FLAC files run at full bandwidth.
>


I've been following this thread and others in which play stops at the end of a song, requiring the user to hit a button (e.g. ">>" to resume).

I have noticed SoftSqueeze has been discussed as the possible problem. I have noticed this problem on the actual hardware SqueezeBox2 as well, so I think it's a server issue and not necesasrily a SoftSqueeze problem.

Anyway, I just wanted to provide a data point to consider and to perhaps stop the chasing of a SoftSqueeze problem (if in fact it is a read herring). But I have not yet come up with a way to reproduce this issue as a test case, so it's hard to debug for sure!

-Joe

P.S., I am now running the daily 6.5 beta (10/29). Tonight, I noticed this problem happening, but I had paused and unpaused a couple of times during the song that halted when it reached the end.

mkosma
2005-10-30, 15:22
Still having trouble. I'm using java 1.5.0_04, softsqueeze 2.2, slimserver 6.5b1, using JLayer, and connecting over putty/ssh. No network issues, and especially high bandwidth right now since it's sunday afternoon and I have the whole corporate network to myself.

Here's output from the softsqueeze console (no debug options turned on):

2780507 [AudioDecoder-14] WARN javasound.verbose - audioDecoder did not write (0) the same number of bytes as read (4608)
2792554 [AudioDecoder-15] WARN javasound.verbose - audioDecoder did not write (0) the same number of bytes as read (4608)
7360861 [AudioDecoder-33] WARN javasound.verbose - audioDecoder did not write (0) the same number of bytes as read (4608)

mkosma
2005-10-30, 15:45
turned on more debugging and tried again, got an additional potentially interesting msg. (This problem is entirely repeatable when playing two particular tracks - Richard, any interest in my sending you the two mp3's?)

8764406 [AudioMixer-0] WARN javasound - Detected delay writing to audio buffer readTook=0ms writeTook=1102ms bufferedData=576ms

mkosma
2005-10-30, 15:48
here's a little more context after it occurred again:

8987230 [AudioDecoder-51] DEBUG audiobuffer.verbose - free R=89216000 W=92509696 F=234304
8987270 [AudioDecoder-51] DEBUG audiobuffer.verbose - free R=89216000 W=92514304 F=229696
8987320 [AudioDecoder-51] DEBUG audiobuffer.verbose - free R=89216000 W=92518912 F=225088
8987351 [AudioDecoder-51] DEBUG audiobuffer.verbose - free R=89216000 W=92523520 F=220480
8987401 [AudioDecoder-51] DEBUG audiobuffer.verbose - free R=89216000 W=92528128 F=215872
8987451 [AudioDecoder-51] DEBUG audiobuffer.verbose - free R=89216000 W=92532736 F=211264
8987511 [AudioStream-51] DEBUG audiobuffer.verbose - free R=320005 W=1187840 F=180741
8987551 [AudioStream-51] DEBUG audiobuffer.verbose - free R=320005 W=1188352 F=180229
8987601 [AudioMixer-0] DEBUG javasound.verbose - playFrame: bytes written=64000,open:true
8987631 [AudioMixer-0] DEBUG javasound.verbose - readTook=100ms writeTook=1412ms bufferedData=616ms
8987631 [AudioMixer-0] WARN javasound - Detected delay writing to audio buffer readTook=100ms writeTook=1412ms bufferedData=616ms
8987631 [AudioMixer-0] DEBUG audiobuffer.verbose - avil R=89216000 W=92537344 A=3321344
8987631 [AudioMixer-0] DEBUG audiobuffer.verbose - buf R=89280000 W=92537344 #=64000
8987631 [AudioMixer-0] DEBUG javasound.verbose - playFrame: bytes read=64000 bufLen=64000 fillLen=64000 available=81%
8987631 [AudioMixer-0] DEBUG javasound.verbose - playFrame: bytes written=64000,open:true
8987631 [AudioMixer-0] DEBUG javasound.verbose - readTook=30ms writeTook=0ms bufferedData=136ms
8987631 [AudioMixer-0] DEBUG audiobuffer.verbose - avil R=89280000 W=92537344 A=3257344
8987631 [AudioMixer-0] DEBUG audiobuffer.verbose - buf R=89344000 W=92537344 #=64000
8987631 [AudioMixer-0] DEBUG javasound.verbose - playFrame: bytes read=64000 bufLen=64000 fillLen=64000 available=31%
8987691 [AudioDecoder-51] DEBUG audiobuffer.verbose - free R=89344000 W=92537344 F=334656
8987741 [AudioDecoder-51] DEBUG audiobuffer.verbose - free R=89344000 W=92541952 F=330048
8987781 [AudioDecoder-51] DEBUG audiobuffer.verbose - free R=89344000 W=92546560 F=325440

rtitmuss
2005-11-03, 15:54
mkosma wrote:

>turned on more debugging and tried again, got an additional potentially
>interesting msg. (This problem is entirely repeatable when playing two
>particular tracks - Richard, any interest in my sending you the two
>mp3's?)
>
>
Yes, it would be helpful to have those files. Please post me a link to
them offlist.

Richard

mkosma
2005-11-08, 11:51
Richard - did you get the files? Any luck reproducing the problem?

rtitmuss
2005-11-09, 16:09
mkosma wrote:

>Richard - did you get the files? Any luck reproducing the problem?
>
Yes, I have the files - thanks. I have a very busy with the day job at
the moment so have not had chance to listen to them yet. I hope to get
change to try them out over the weekend ...

Richard