PDA

View Full Version : ANDY, problems with internet radio again



MrSinatra
2007-03-21, 13:11
Andy,

your fix to allow one to proxy the station on SS has been a great help, but i am facing similar issues.

just to recap, i now must use SS proxing the net stream to hear it on SB. i also set it to a 30 second buffer.

but that doesn't stop the SB from constantly dropping the signal and restarting it.

and once again, winamp has no issues consistently playing it.

now, SS/SB can play it at times fine. but at other times, it'll play for a while, (random lengths), drop out for 5-9 seconds, restart, or sometimes, stop itself all together. winamp however, when SS is doing this, can stream successfully np.

now, i can tell this is different and better than b4 SS proxied, b/c it isn't as bad. but its still unlistenable ultimately.

same question as always, why can't SS/SB in a proxied & 30 second buffer situation do what winamp can do?

btw, just as an side, shoutcast seems to identify SS connecting to it as 'itunes 4.7.1'

pretty old version... could it at all be related?

mherger
2007-03-21, 13:23
> same question as always, why can't SS/SB in a proxied & 30 second
> buffer situation do what winamp can do?

Please recapitulate your configuration as well. Are you running wireless?
Any other wireless devices? Channels tested? Tested using rj45 etc. I'm
sure you must be more interested in a solution than the why-oh-why, don't
you?

--

Michael

-----------------------------------------------------------------
http://www.herger.net/SlimCD - your SlimServer on a CD
http://www.herger.net/slim - AlbumReview, Biography, MusicInfoSCR

bpa
2007-03-21, 13:24
You could use ethereal ( http://www.ethereal.com ) to record exactly what is happening on the network on a bad SB session and a good Winamp session - ideally with no other traffic.

It would then be possible to see what Winamp is doing differently to SS/SB.

MrSinatra
2007-03-21, 14:03
bpa, i will try that.

and yes its wireless, and no, wireless (as andy has said) is not the problem in my case. (it does work sometimes, and local music, at 256kbps works too. even the 32kbps net stream can give me a hassle)

mherger
2007-03-21, 14:10
> and yes its wireless, and no, wireless (as andy has said) is not the
> problem in my case. (it does work sometimes, and local music, at
> 256kbps works too. even the 32kbps net stream can give me a hassle)

Please do the cabled test anyway. Just to be sure wireless really isn't
the problem.

--

Michael

-----------------------------------------------------------------
http://www.herger.net/SlimCD - your SlimServer on a CD
http://www.herger.net/slim - AlbumReview, Biography, MusicInfoSCR

bpa
2007-03-21, 14:16
You should use ethereal to record the session between the PC and the internet (i.e. that specific network interface) - it doesn't matter if it is wireless or not. Ethereal will record the ethernet frames and ignore the medium (wired or wireless). Problems in the medium will appear as invalid or missing packets or possibly timeouts.

MrSinatra
2007-03-22, 12:26
BPA,

i have DL'd and installed the pgm, but its a bit overwhelming.

i'm not sure if i have it configured properly, or monitoring the right thing... i did tell it to "display in real time" so i could see what it was doing while it "captured" but other than that its all defaults i think.

its produces a huge amount of data for a log in a very short time... how long should i capture for and do you want me to post it all?

also, should i capture, then start trying to play the stream; or try to start the stream first, then capture?

bpa
2007-03-22, 15:41
It looks like you're doing OK. The aim is to capture relevant data ideally from just before a connection is made and then stop just after you hear a 5-9 secs drop out on a Squeezebox. For intermittent problem I usually stop a recording session if the problem doesn't show within a few minutes and start again so that the capture file is not huge.

I'm nor sure about the windows version but I normally use the "prepare" option so that i can press easily "start" just before I start Slimserver playing the station.

Since Ethereal captures everything on the selected network interface - this include confidential data - I shut down all unnecessary apps and services (in Windows MS has a lot of things which use the network in the background).

The default Ethereal setup has a packet size limit so that only about 68 bytes of the packet header are saved. I ran a test on a 32kbit/sec WMA station and it saved about 60kbytes for 2 mins - as a result of proxy playing to a SB, the traffic will be doubled. This data also compresses quite well so depending on the size it may be necessary to mail the file.