ShoutCast (source) no data (30 second timeout)

MyTjoe · 13th November 2007, 15:44

My station has been up for 2 months now, working great, and last night was the first time that this "no data (30 second timeout)" problem ever came up.

With regards to the encoding rate, I was running it just fine a few weeks ago with a variety of tracks of different rates (some lower than my broadcast) and it did not cause any problem. Those songs are off now (they were my ancient halloween collection) and only freshly ripped tracks are on now (all are higher than I am streaming). I have tried to narrow it down to a particular song or songs and there is no detectable pattern. It is doing it on songs that have been in my list from the beginning and on newer ones.

When it first started, I assumed it was my ISP, but nothing else was having issues. I thought it was Shoutcast themselves but I could kill WinAmp and it would immediately connect on startup and be fine again - for a little while. Then I noticed that some of the times, the Shoutcast Source (v1.9) plugin was locked up. The display was still showing activity (reconnecting on both of my streams and the signal bars moving) but I couldn't close the window, or switch to "none" in the DSP plugin config. Other times, as soon as it timed out, I was able to switch to "none" in the DSP config and then switch back to Shoutcast Source v1.9 and it would startup right away and streaming again.

This also created another symptom. This morning, the stream was alive and well, but I couldn't access the data from Song Requester from other computers (inside router and out) or any other file in my "server". A reboot of the PC got it all working again, but that is the first time this has happened. Seems rather coincidental that it happens when this other issue has just come up. Later I found that I don't have to reboot the pc, just stopping winamp and restarting it takes care of it.

I am also running the DoSomething plugin. I have it set to post the current song and the last three songs to another html file and then ftp that up to another server so that I can get that data from my office (only allows port 80 traffic). When this "no data" issue comes up, WinAmp keeps on playing the songs and DoSomething keeps posting the correct data. Yet when I try to access html files from where I have Shoutcast Source set as my server, I cannot reach the destination. It is like the server stops being a server.

Stopping and restarting just the Shoutcast Source plugin gets the music playing again, but the html files there are not accessible until I close WinAmp and then restart it. Then everything works again - until the next timeout.

Again, I sometimes think it is my ISP blocking outbound, or my router, but simply stopping and restarting WinAmp gets everything running again.

I am running WinAmp 5.35. I see that 5.5 is available but am reluctant to upgrade. Any thoughts on that?

This is frustrating because it has been working great up until now. And it is random... it will run fine for hours, or it will bomb after 20 minutes....

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Switch to Linear Mode Switch to Hybrid Mode Threaded Mode

13th November 2007, 15:44	#10
MyTjoe Junior Member Join Date: Sep 2007 Posts: 24	My station has been up for 2 months now, working great, and last night was the first time that this "no data (30 second timeout)" problem ever came up. With regards to the encoding rate, I was running it just fine a few weeks ago with a variety of tracks of different rates (some lower than my broadcast) and it did not cause any problem. Those songs are off now (they were my ancient halloween collection) and only freshly ripped tracks are on now (all are higher than I am streaming). I have tried to narrow it down to a particular song or songs and there is no detectable pattern. It is doing it on songs that have been in my list from the beginning and on newer ones. When it first started, I assumed it was my ISP, but nothing else was having issues. I thought it was Shoutcast themselves but I could kill WinAmp and it would immediately connect on startup and be fine again - for a little while. Then I noticed that some of the times, the Shoutcast Source (v1.9) plugin was locked up. The display was still showing activity (reconnecting on both of my streams and the signal bars moving) but I couldn't close the window, or switch to "none" in the DSP plugin config. Other times, as soon as it timed out, I was able to switch to "none" in the DSP config and then switch back to Shoutcast Source v1.9 and it would startup right away and streaming again. This also created another symptom. This morning, the stream was alive and well, but I couldn't access the data from Song Requester from other computers (inside router and out) or any other file in my "server". A reboot of the PC got it all working again, but that is the first time this has happened. Seems rather coincidental that it happens when this other issue has just come up. Later I found that I don't have to reboot the pc, just stopping winamp and restarting it takes care of it. I am also running the DoSomething plugin. I have it set to post the current song and the last three songs to another html file and then ftp that up to another server so that I can get that data from my office (only allows port 80 traffic). When this "no data" issue comes up, WinAmp keeps on playing the songs and DoSomething keeps posting the correct data. Yet when I try to access html files from where I have Shoutcast Source set as my server, I cannot reach the destination. It is like the server stops being a server. Stopping and restarting just the Shoutcast Source plugin gets the music playing again, but the html files there are not accessible until I close WinAmp and then restart it. Then everything works again - until the next timeout. Again, I sometimes think it is my ISP blocking outbound, or my router, but simply stopping and restarting WinAmp gets everything running again. I am running WinAmp 5.35. I see that 5.5 is available but am reluctant to upgrade. Any thoughts on that? This is frustrating because it has been working great up until now. And it is random... it will run fine for hours, or it will bomb after 20 minutes....