Pauses in server sound
 

When listening to any server at any bitrate, I hear short pauses in the sound about evert 5 seconds. I also get very loud screeching sounds every now and then (probably unrelated). I have tested this on a friends computer using Winamp3 and Music Match (evil). The shoutcast servers sounds just as distorted on his computer as mine, but when I connect to the same server using Music Match - it sounds fine. The only commonality between our two systems is the operating system. We both use the same copy of XP Corp.

There is no way in hell I'm using Music Match, so can anyone help?

p.s. this happens on both winamp2 and 3 both systems

I suppose 21 views means no one has any clue how to fix this.

Which winamp version you using?

I tested it with 2 and 3

both have the same problem

Update:

I just noticed im the only person who gets 4 digit numbers for titles when listening to a shoutcast station. I also noticed that when I find a server without a 4 digit number name, it does not have distortions (pauses and other shiat).

Currently the only station I've found to "work properly" for me is Japan-A-Radio. I'll look for more "working" stations later, but right now I'm listening to some nice anime music ^_^

Update:

I have figured out the problem.

It seems that server URL's like below will have problems on my machine.
http://205.188.209.193:80/stream/1003 (I think this is where the title comes from..the 4 digit number previously mentioned)

But URL's like below work perfectly fine:
http://205.188.245.131:8004
The title of the song playing shows and the sound is perfect.

So my question is, why? The two urls mentioned here are for the SAME shoutcast station (digitally imported euro trance). Why is the working url at the bottom of the playlist? Why is there more than one item in the playlist editor?

why me?

Hey,

You're not the only one with that problem...

I get 4 digits as the song name for streams that look like this:
http://198.81.31.133:80/stream/1016
Is the metadata not reaching me? is it a bug?
It also has a lot of pauses, choppiness.

However, the metadata and song title works fine (name changes when song changes) for streams whose playstring look like this:
http://205.188.234.4:8008
I get no choppiness here...

btw, these are Flaresound streams

I've tested this in both Winamp3 and Winamp2 on both Win98 and WinXP

I was running Winamp3 at school today listening to a stream that looked like http://198.81.31.133:80/stream/1016. I think the metadata showed up properly there... What is causing this problem for me at home?
My ISP? Firewall? Please help....

Using 2.83 (3.0 = bloat) and I get the same issue when connecting to the digitally imported sites as well as others.

I have DirectX 8.1 and have an onboard sound card. I've tried using different output plugins without any change.

Interesting thing to note.

EuroDance HiNRG Pop] CLUSTER D I G I T A L L Y - I M P O R T E D - EuroDance & HiNRG - Finest imported cheese on the net!

When I connected to that I was getting the same issue. But since they're clustered they list a bunch of possible servers to connect to. I figured what the heck and tried connecting to each one and was pleasantly suprised when I connected to #4 and the name of the song playing showed up and the song started playing flawlessly.

So it would appear that this is more of a server issue then anything?

yes the ultravox system is at a beta phase of developement and those stations have volunteered to be apart of it, as part of it though there comes problems, if you can't get it to work and really need to listen to the station go to Preferences -> Input -> Mpeg Audio Decoder -> Streaming (tab) and uncheck Shoutcast title streaming.

what about us winpimp3 users?

Hehe.. well then.. just to let you know.. your beta has a bug ;) Any ETA on it being fixed?

I am not a nullsoft team member so I have no idea, talk to nullsoft.

Ok,
Now I'm at school with Winamp3 installed on a freshly installed Win98 machine.

I'm listening to a stream whose URL (playstring) is of the following format:
http://XXX.XXX.XXX.XX:80/stream/####
The title seems to show up fine, the metadata works, and it's not choppy.

How come it doesn't work for me at home? I just get those 4 last numbers as the song title at home. This problem is hard to diagnose.
But right now I'm guessing it's either my ISP or my software based firewall at home.

Streams whose playstring is of the following format:
http://XXX.XXX.XXX.XXX:8###/
work fine at both school and home. The song title shows up properly.

Maybe this has something to do with the port. One connects to port 80, and the other connects to 8 thousand something.

Whoever is working on Ultravox might want to take a look at this issue.

they already know about this issue. That's really all I know regarding it, just disable the title streaming and you should be golden no matter where you are at.

i had win98 and cable net and streaming worked great, i upgraded to winxp pro and it works bad.

i get about 30 seconds of music before it has to reconnect to the station.
i tried increasing the buffer and it kept the music going for longer but it would still drop out after some time.

i disabled the firewalls, it's no better.

i have 512meg of ram so it wont run out of space.
my system is faster now with the upgrade than before. so it's not performance problems.

i suspect that winamp connects to the station fills the buffer and disconnects, once the buffer is gone it has to reconnect to get more data.

not the way it should work.
i think it's an option or a setting or a way that winxp works with ports and connections that is causing this problem. ie it cuts the connection after the buffer is filled. this did not happen in win98.

is there a known solution to this, ie a setting or a work-around to keep the music flowing?

ohhh and yeah i've tried it with winamp 3 and 2 and i've tried that solution up above.

sounds like you don't have enough download speed to handle the streams you are connecting to, try listening to a 24 or even a 8kbps stream and see if it still disconnects.

justsomeoni has 1.5 meg down 128 up cable.

Not a bandwidth problem.

that is your problem, not the bandwidth I was speaking to DopeFishhh with my last post.

im blonde

whoops i forgot to mention i have cable, and that was before i had xp
i got plenty of speed (i downloaded a file at 800k/s once)

and i did try a smaller stream size. the difference with those was the stream went for longer before cutting out.

Same problem over here: When doing what KXRM said (disabling the title streaming, but then appears the second problem that DopeFishhh mentions, winamp filling the buffer and then reconecting to the station when the buffer run out... and it seems not to be a problem of winXP alone since i´m over a wink2k pro.

Tried every possible configuration of the input MPEG Decoder and nothing seems to work. This seems a server problem to me, since my winamp was streaming perfectly those stations last year.

Any other software recomendation to stream mp3s from shoutcast servers?

and is it solved?
 

I searched on and on and have not found a solution yet except that this post has given me a station:
---------------------------
" Hey,

You're not the only one with that problem...

I get 4 digits as the song name for streams that look like this:
http://198.81.31.133:80/stream/1016
Is the metadata not reaching me? is it a bug?
It also has a lot of pauses, choppiness.

However, the metadata and song title works fine (name changes when song changes) for streams whose playstring look like this:
http://205.188.234.4:8008
I get no choppiness here...

btw, these are Flaresound streams

I've tested this in both Winamp3 and Winamp2 on both Win98 and WinXP"
-------------------------------

And my 12 sec pause is over.
Only the sender has mainstream music...
So it is not my firewall.
My problems do NOT go away by disabling Shoutcast title streaming and I am not th eonly one
See post of DopeFishhh

No moderators with knowledge that can help me out?

no Solution?
 

May I conclude there is no solution for this problem?
Luziano's and Dopefishhh's problem did not have any solutions since May this yr. and for myself I wait already 6 days... for a helpnig hand :(