Streaming delay is being weird

[bboytails]

Hi, my shoutcast radio is acting weird...
I have mine on port 80, when i connect to:
http://myip:80 -- it would have a very long delay, maybe because my bitrate is at 64...
but neways, when i connect to:
http://myip:81 -- the quality and volume is a bit lower, but there is no delay... but here's the catch...
http://myip:81 works rarely, i have no idea why, it would be working at one point, another point it will say "error synchronizing"

Anyone have any idea why port 81 is acting like this?

[djmastermind]

I'm not sure I understand why it would work at all.. I've never seen any other port but the assigned portbase work.

Please post the link(s).

[bboytails]

I don't have a stable network yet, so the ip may have changed since i posted this msg.

but here are the ips.

http://217.239.0.145:80
http://217.239.0.145:81

If those for some reason don't work just by clicking on it, please go to your winamp/WMP and add the url.

Thank You

P.S. If that doesnt work either, please search "TaiLNeT" at www.shoutcast.com

[Jay]

port 81 is a source port.

[bboytails]

Could you rephrase that in a simpler term please.

[Jay]

port 80 is your client port (that is where you tune in to hear the stream, port 81 is used for sourcing the server.

One instance of SHOUTcast will consume portbase and portbase +1

[bboytails]

Oh i see, thank you very much.
But i still dont see why it would randomly start working.
I actually rather have port 81 instead of 80.

I'm using ProfileAmp 8.0 for AIM, which displays what my winamp is playing, i also have a link to my radio station, but the delay is really irritating since it is streaming what my profile displayed 90 secs ago.

Anyway of getting around this delay w/o having to change the bitrate?

[djSpinnerCee]

A guess -- You're running WinAMP or another player for listening that does crossfading -- when you switch from port 80 to port 81, what's left of the port 80 stream "volume+quality" will begin to get lower [fade out+remove silence] while the connection attempt is made on port 81, at some point it will die [when the buffer has run out ~90 seconds]. If you try port 81 again, you'll likely get nothing+the error message. You kind of answered your own question about the delay -- it's the buffer+crossfade that allows you to think that a connection to port 81 works, but it also allows you to continue listening long after you have disconnected.

You can "see" what's really happening if you look at the DNAS GUI while you do this -- in every case, you will not see a successful connection attempt when you use port 81 to listen, that connection will be refused by the DNAS, especially if a source is present.

add: Estimating delay -- Roughly, a 128kbps MP3 is 1 MegaByte per minute -- the DNAS buffers about 1 MB of source regardless of bitrate, so the maximun source to DNAS delay for 128kbps would be 1 minute -- 64kbps is 500KB/min, so the delay would double to 2 min, at 32kbps and 250KB/min, you have a whopping 4 minute maximum delay. --- when your delay exceeds the maximum [you are behind] -- you will underrun. That's why a lower bitrate stream is less prone to skipping.

[DJ Zath]

you should NEVER have anything except the DNAS connection to port 81 (or X+1) the fact that you CAN have the X+1 port connect at all suggests a serious security vurlability!

DjZ

[bboytails]

When i connected to http://myip:81
It showed up on my GUI the same exact way as it did for
http://myip:80
I don't think it's "crossfading" because port 81 is streaming with absolutely no delay at all.
Neways, thank you for your help, I'll just simply lower the max users and increase the bitrate to avoid the delay.