oreillymj;168539 Wrote: 
> Just my 2p worth.
> 
> andy's thought's that wireless might be the culprit is based on the
> info you yourselves have given him.

if you look in this thread, you'll see andy say that in my case, it
doesn't seem to be my wireless.

and the OP isn't wireless.

oreillymj;168539 Wrote: 
> i.e. In 6.2, the stream went to your slimserver and then on to the SB.
> This, you say worked fine.

yes, it was good.  the one bad thing is i don't know exactly when the
versions switched, and when comcast started the switchover...  so
unfortunately, i can't say for sure what the "test results" were under
different versions and conditions, and so on...

suffice it to say, ~6.3 - 6.5 comcast began taking over, and my
problems started.  unfortunately i can't be more accurate then that.  i
also don't know exactly when (or what ver) SD changed the code to have
SB handle shoutcast directly rather than sending it to SS first, but i
am pretty sure all 6.2.x vers did it that way, (ie. send it to SS
first).

oreillymj;168539 Wrote: 
> Maybe there was some bit-rate limiting happening here or, prior to WMA
> streams being supported, transcoding using WMADec/Lame.
> 
> With 6.5 you have 2 changes, 1 WMA is supported natively and the SB
> handles the streaming itself.

wma?  the shoutcast streams encode as mp3.  and neither they, nor i had
any bitrate limiting setup that i know of, (and i admin the shoutcast
servers).  also even the 32kbps stream was too much for the SB.

oreillymj;168539 Wrote: 
> So there are 2 possibilities I can think of.
> 
> 1) The stream exceeds the bandwith of your wireless network. It would
> be interesting to get some info about the stream bitrate. 
> Prior to 6.5 the transcoding might have covered this up, once your
> broadband was up to the task of keeping the stream going.

like i said, it couldn't do the 32kbps stream, but it ALWAYS could play
my 256kbps local mp3s fine.

oreillymj;168539 Wrote: 
> 2)Your default gateway is mis-configured. Perhaps you have your default
> gateway set to your Slimserver and not your router, causing extra hops.

i am pretty sure this is not the case.

oreillymj;168539 Wrote: 
> Also, are you in a mixed 802.11b/g environment. Do you have some 802.11b
> devices you use ocassionally.

no G at all, only b, which is plenty good enough it would seem, since
its all working currently, as it had in the past.

oreillymj;168539 Wrote: 
> It's a pity there wasn't a way to drop back to the old behaviour within
> a playlist.
> i.e a comment in the playlist which forces Slimserver to stream from
> the radio station and transcode to the SB as it used to.

YES! this is something i think should be optional.

if you experience issues with the "direct to SB" method, as clearly
some of us have, then forcing it to go to SS first, then to SB would
probably rectify it, (given that winamp works).  this would be great.


but i don't know if its possible codewise to give such an option, thats
an andy question.  and to even be able to push for such an option, we
all have to agree that my wireless in my case, isn't the problem,
something i guess i can't prove to all the doubting thomas'es out there
until the problem resurfaces for me, and i switch the SB to wired to
eliminate it as a possibility.

thx, -mdw


-- 
MrSinatra

www.LION-Radio.org
Using:
Squeezebox2 w/SS 6.5.1 (beta!?) - Win XP Pro SP2 - 3.2ghz / 2gig ram
------------------------------------------------------------------------
MrSinatra's Profile: http://forums.slimdevices.com/member.php?userid=2336
View this thread: http://forums.slimdevices.com/showthread.php?t=31359

_______________________________________________
discuss mailing list
discuss@lists.slimdevices.com
http://lists.slimdevices.com/lists/listinfo/discuss

Reply via email to