PDA

View Full Version : SB2 Wireless Help Needed - Audio Drops



patrija
2005-11-08, 20:25
Continuous problems with SB2 wireless drops. Got a good setup - Dell 9100 Pentium D 3.2 GH with 1 Gig RAM, router is a Belkin Pre-N, music stored on a Linkstation, no iTunes. Music plays fine for awhile then starts dropping - and always drops whenever try to sync the 2 SB2's. Here the network health logs while dropping, unsynced. Slim.exe taking 40-50k RAM. CPU generally ruinning < 5%. SB2 is Firmware 26. SlimServer Version: 6.5b1 - 4898 - Windows XP - EN - cp1252. Getting frustrated. Thoughts on how to improve?

Home / Server & Network Health

Server & Network Health

Performance monitoring is currently enabled on your server. Performance statistics are being collected in the background while your server is running.

Disable Performance Monitoring

Reset Counters

Update Page



--------------------------------------------------------------------------------
BarPlease queue up several tracks to play on this player and start them playing. Then press the Reset Counters link above to clear the statistics and update this display.

Summary
Control Connection : OK
Streaming Connection : OK
Player Signal Strength : OK
Buffer Fullness : Low
Server Response Time : Occasional Poor Response


Warnings
The playback buffer for this player is occasionally falling lower than ideal. This is a Squeezebox2 and so the buffer fullness is expected to drop at the end of each track. You may see this warning if you are playing lots of short tracks. If you are hearing audio dropouts, please check our network signal strength.

Your server response time is occasionally longer than desired. This may cause audio dropouts, especially on Slimp3 and Squeezebox1 players. It may be due to background load on your server or a slimserver task taking longer than normal.


--------------------------------------------------------------------------------
Player Performance : BarThe graphs shown here record the long term trend for each of the player performance measurements below. They display the number and percentage of measurements which fall within each measurement band.

It is imporant to leave the player playing for a while and then assess the graphs.


Player Signal Strength
This graph shows the strength of the wireless signal received by your player. Higher signal strength is better. The player reports signal strength while it is playing.
< 10 : 1 : 0%
< 20 : 0 : 0%
< 30 : 0 : 0%
< 40 : 0 : 0%
< 50 : 0 : 0%
< 60 : 67 : 1%
< 70 : 2954 : 24% ############
< 80 : 6754 : 56% ###########################
< 90 : 2294 : 19% #########
< 100 : 0 : 0%
>=100 : 1 : 0%
max : 100.000000
min : 0.000000
avg : 73.153343

Buffer Fullness
This graph shows the fill of the player's buffer. Higher buffer fullness is better. Note the buffer is only filled while the player is playing tracks.
Squeezebox1 uses a small buffer and it is expected to stay full while playing. If this value drops to 0 it will result in audio dropouts. This is likely to be due to network problems.

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.

Playing remote streams can lead to low buffer fill as the player needs to wait for data from the remote server. This is not a cause for concern.

< 10 : 4431 : 40% ####################
< 20 : 141 : 1%
< 30 : 71 : 1%
< 40 : 49 : 0%
< 50 : 59 : 1%
< 60 : 47 : 0%
< 70 : 44 : 0%
< 80 : 46 : 0%
< 90 : 56 : 1%
< 100 : 6082 : 55% ###########################
>=100 : 0 : 0%
max : 99.999968
min : 0.000000
avg : 57.129062

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 : 8882 :100% ##################################################
< 2 : 0 : 0%
< 5 : 0 : 0%
< 10 : 0 : 0%
< 20 : 0 : 0%
>=20 : 0 : 0%
max : 0.000000
min : -1.000000
avg : -0.000113


--------------------------------------------------------------------------------
Server PerformanceThe graphs shown here record the long term trend for each of the server performance measurements below. They display the number and percentage of measurements which fall within each measurement band.
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 : 307349 : 93% ##############################################
< 0.005 : 23274 : 7% ###
< 0.01 : 357 : 0%
< 0.015 : 48 : 0%
< 0.025 : 92 : 0%
< 0.05 : 133 : 0%
< 0.1 : 126 : 0%
< 0.5 : 63 : 0%
< 1 : 4 : 0%
< 5 : 10 : 0%
>=5 : 32 : 0%
max : 8.714937
min : 0.000042
avg : 0.001562

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 : 56870 : 97% ################################################
< 0.005 : 358 : 1%
< 0.01 : 438 : 1%
< 0.015 : 348 : 1%
< 0.025 : 121 : 0%
< 0.05 : 30 : 0%
< 0.1 : 27 : 0%
< 0.5 : 57 : 0%
< 1 : 15 : 0%
< 5 : 48 : 0%
>=5 : 162 : 0%
max : 8.421772
min : 0.000000
avg : 0.022682

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 : 35529 : 61% ##############################
< 0.005 : 22787 : 39% ###################
< 0.01 : 69 : 0%
< 0.015 : 8 : 0%
< 0.025 : 17 : 0%
< 0.05 : 38 : 0%
< 0.1 : 19 : 0%
< 0.5 : 7 : 0%
< 1 : 0 : 0%
< 5 : 0 : 0%
>=5 : 0 : 0%
max : 0.191858
min : 0.000047
avg : 0.001282

Ben Sandee
2005-11-08, 21:31
On 11/8/05, patrija <patrija.1y7mrz (AT) no-mx (DOT) forums.slimdevices.com> wrote:
>
>
> Continuous problems with SB2 wireless drops. Got a good setup - Dell
> 9100 Pentium D 3.2 GH with 1 Gig RAM, router is a Belkin Pre-N, music
> stored on a Linkstation, no iTunes. Music plays fine for awhile then
> starts dropping - and always drops whenever try to sync the 2 SB2's.
> Here the network health logs while dropping. Slim.exe taking 40-50k
> RAM. CPU generally ruinning < 5%. Thoughts on how to improve?


I believe that some have reported problems with the Belkin router when UPNP
was enabled. If you do not need UPNP, maybe try disabling it in your router
and see if it helps.

Otherwise, you might be running into bandwidth issues because you are
streaming two streams over wireless. You didn't say what format your music
is -- is it MP3, lossless or a transcoded format (AAC)? I wouldn't think you
could reliably and effectively stream many more than two or three SB2's with
lossless formats over a 802.11g network.

Ben

seanadams
2005-11-08, 23:03
I agree, this looks like the network can't keep up, not that the server is bogging down.

CavesOfTQLT
2005-11-09, 03:43
I believe that some have reported problems with the Belkin router when UPNP
was enabled. If you do not need UPNP, maybe try disabling it in your router
and see if it helps.

Ben
I had issues with my Belkin Pre-N with drop-outs and Belkin informed me to enable the uPNP function on the router. So I did and I've never had problems since. This is on (router) firmware 1.01.03 and boot version 2.01.08. As it's all running sweetly I've never disabled the option to see if the problem returned. Have a go at enabling it and see what happens.

If you're running Windows I'd download Network Stumbler and check for other networks in close proximity, and change the router channel to one that's further away and/or best SNR and take it from there. Good luck.

Ben Sandee
2005-11-09, 07:06
On 11/9/05, CavesOfTQLT <CavesOfTQLT.1y86wz (AT) no-mx (DOT) forums.slimdevices.com>
wrote:
>
>
> Ben Sandee Wrote:
> >
> > I believe that some have reported problems with the Belkin router when
> > UPNP
> > was enabled. If you do not need UPNP, maybe try disabling it in your
> > router
> > and see if it helps.
> >
> > Ben
> I had issues with my Belkin Pre-N with drop-outs and Belkin informed me
> to _enable_ the uPNP function on the router. So I did and I've never had
> problems since. This is on (router) firmware 1.01.03 and boot version
> 2.01.08. As it's all running sweetly I've never disabled the option to
> see if the problem returned. Have a go at enabling it and see what
> happens.


my mistake, thanks for clarifying....

MrC
2005-11-09, 10:11
I agree, it does seem that the network cannot keep up.

The Belkin provides no useful stats or information about connection and transfer rates (I will not purchase another one for this reason alone). And the Network and Server Health plugin only provides evidence that packets are not arriving fast enough, not why.

Perhaps it might be possible to add to the Health plug some additional information that might help further diagnose or clarify. See my question in the following thread:

http://forums.slimdevices.com/showthread.php?p=64140#post64140

patrija
2005-11-09, 14:30
Thanks everyone, at work so won't have a chance to play with it until later tonight. I'll check my UNPNP setting, can't remember which way I have it right now. Music is all MP3, a lot are iTunes converted using JHymn. I'll look for the Network Stumbler program to see what I can find.

patrija
2005-11-11, 17:06
I checked the setting on my router and UPNP was turned off. I turned it back on and let SB2 play for a day. Worked fine for a long time and then started dropping again. Here's the logs. Any suggestions? My wife's about to throw it out - can't stand listening to every other word of a song. I ran Network Stumbler and I am the only one on Channel 1 - closest is Channel 6. Note, I had stopped streaming just before I grabbeded this health log. Thanks.

Bar
Please queue up several tracks to play on this player and start them playing. Then press the Reset Counters link above to clear the statistics and update this display.

Summary
Control Connection : OK
Streaming Connection : Inactive
Player Signal Strength : OK
Server Response Time : OK


Warnings
There is currently no active connection for streaming to this player. A connection is required whenever you play a file from the server (but not when you play remote radio streams on a Squeezebox2 player).

If you are attempting to play a local file on this player, then this indicates a network problem. Please check that your network and/or server firewall do not block connections to TCP port 9000.


--------------------------------------------------------------------------------
Player Performance : BarThe graphs shown here record the long term trend for each of the player performance measurements below. They display the number and percentage of measurements which fall within each measurement band.

It is imporant to leave the player playing for a while and then assess the graphs.


Player Signal Strength
This graph shows the strength of the wireless signal received by your player. Higher signal strength is better. The player reports signal strength while it is playing.
< 10 : 22 : 0%
< 20 : 0 : 0%
< 30 : 0 : 0%
< 40 : 0 : 0%
< 50 : 0 : 0%
< 60 : 43 : 0%
< 70 : 15196 : 9% ####
< 80 : 89206 : 51% #########################
< 90 : 71850 : 41% ####################
< 100 : 1 : 0%
>=100 : 15 : 0%
max : 100.000000
min : 0.000000
avg : 76.674360

Buffer Fullness
This graph shows the fill of the player's buffer. Higher buffer fullness is better. Note the buffer is only filled while the player is playing tracks.
Squeezebox1 uses a small buffer and it is expected to stay full while playing. If this value drops to 0 it will result in audio dropouts. This is likely to be due to network problems.

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.

Playing remote streams can lead to low buffer fill as the player needs to wait for data from the remote server. This is not a cause for concern.

< 10 : 40464 : 39% ###################
< 20 : 2469 : 2% #
< 30 : 1748 : 2%
< 40 : 1606 : 2%
< 50 : 1632 : 2%
< 60 : 1467 : 1%
< 70 : 1361 : 1%
< 80 : 1473 : 1%
< 90 : 1502 : 1%
< 100 : 49639 : 48% ########################
>=100 : 0 : 0%
max : 99.999968
min : 0.000000
avg : 54.016724

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 : 96690 :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 PerformanceThe graphs shown here record the long term trend for each of the server performance measurements below. They display the number and percentage of measurements which fall within each measurement band.
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 : 4408462 : 93% ##############################################
< 0.005 : 344242 : 7% ###
< 0.01 : 5033 : 0%
< 0.015 : 302 : 0%
< 0.025 : 666 : 0%
< 0.05 : 1059 : 0%
< 0.1 : 383 : 0%
< 0.5 : 474 : 0%
< 1 : 89 : 0%
< 5 : 98 : 0%
>=5 : 326 : 0%
max : 9.082465
min : 0.000024
avg : 0.001220

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 : 642798 : 91% #############################################
< 0.005 : 37045 : 5% ##
< 0.01 : 12111 : 2%
< 0.015 : 7210 : 1%
< 0.025 : 1160 : 0%
< 0.05 : 198 : 0%
< 0.1 : 169 : 0%
< 0.5 : 487 : 0%
< 1 : 224 : 0%
< 5 : 471 : 0%
>=5 : 1316 : 0%
max : 8.764019
min : 0.000000
avg : 0.016290

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 : 406465 : 58% ############################
< 0.005 : 295510 : 42% #####################
< 0.01 : 551 : 0%
< 0.015 : 39 : 0%
< 0.025 : 106 : 0%
< 0.05 : 437 : 0%
< 0.1 : 66 : 0%
< 0.5 : 15 : 0%
< 1 : 0 : 0%
< 5 : 0 : 0%
>=5 : 0 : 0%
max : 0.310747
min : 0.000026
avg : 0.001428

MrC
2005-11-11, 17:14
Please look at this diagram that shows Channel overlap. Channel 6 does not overlap with channel 1, so there is no problems with your neighbor using it. But check the others that do overlap.

http://img.cmpnet.com/nc/1310/graphics/1310ws1b.gif

patrija
2005-11-14, 09:53
Thanks, I should be ok based on this chart. I ran CAT5 to one of the SB2 this weekend, the other one I can't get a wire to very easily. Still hoping to sort out this issue with audio drops....