Mission Impossible: The Perfect Shoutcast Configuration

[Jim]

"Your mission, if you choose to accept it, is to create a Shoutcast station that actually works like it's supposed to!!"

Okay, I've been using Shoutcast for almost three years now, so I suppose I consider myself somewhat of a veteran. However, in those three years, I have only been able to get a station up and running for a maximum of a few days. Either Winamp, the Shoutcast server, or plugins will always cause something to eventually crash/freeze.

Needless to say I've become extremely fed up. And recently, I've only been able to keep my station up for a few hours before crashing!?

Now I know that there are Shoutcast stations out there that actually stay up for extended periods of time. So I am asking those of you who may have one of these "mystical" stations to please, PLEASE post your system specs, along with Winamp version, Shoutcast version, and anything else you think could help myself and other Shoutcast stations to extend the up-time of our servers.

Here are my current specs:

Winamp
-Winamp 2.7
-Shoutcast DNAS v.1.7.1
-Plugins: Oddsock's SongRequester & DoSomething

System
-Pentium III 500
-128MB
-Windows 98

So if you are running a successful Shoutcast station, I beg of you, please let myself and others know your configuration by replying to this post.

[Nercm]

Here are my current specs:

Winamp
Here is my configuration...It works perfectly so far...been running since July 13, 2000...

-Winamp 2.7
-Shoutcast DNAS v.1.7.1
-Plugins: AudioRealm Spacial Audio (SAM)version 1.0

System
-Pentium 300
-128MB
-Windows NT

I found that Oddsocks utilities took up a LOT of my CPU time as well as memory and caused it to crash from time to time...but maybe that was just me...

here is my shoutcast stream... http://tnlradio.servemp3.com:8000

here is the live request playlist http://www.the-nextlevel.com/multimedia/playlist/playing.htm

I recommend downloading SAM (www.audiorealms.com)...it can solve a lot of problems

[Jimbonator]

Consider changing one variable at a time. My first suggestion would be to remove DoSomething and OddSock and see if your problem goes away. (When I say remove, I don't mean deactivate; delete them from your plugins directory).

My second suggestion is to try Windows NT or 2000. While it has its problems, it has real process protection and memory management, versus the hack-it-sort-of thing they call Windows 95/98. While I have had minor problems with Winamp or the SHOUT server, I've not once had NT crash on me since starting my station, nor had to reboot "just because."

Just my observations.

[Jim]

Okay, that helps a lot. I might just try switching to NT, and I'll definitely try taking out plugins to see if those are causing problems. Thanks again.

[plucky]

I have to agree on the switch to NT.
I use Win98 only for my "use" PC, not for my server. I tried WarFTPd on my 98 PC, and it would crash on a regular basis, but it has run for 2 years without a hitch on NT/2000.

I suspect it'll be similar for Winamp for you, as NT is much better at just plugging away at a few tasks for extended periods of time.

I would be warry of Winamp 2.7 though. There were many people had problems with 2.666 and up (don't know if 2.7 FINAL fixed these problems, but I know 2.7 beta 4 didn't for everyone). I still use Winamp 2.65 on my 2000 machine, and it works very well, with multiple plugins stacked (I don't use any Oddsock ones yet, but I might sometime). If it weren't for the fact my server is doing 20 other things constantly, I'm sure Winamp 2.65 and shoutcast would go for weeks with no problem.

98 sucks for server type apps.

plucky

[weed]

First of all - Lots of plugins are coded very roughly and JUST good enough to get by, the plugin that shoutcast recommends, the DSP SHOUTcast source plugin, is EXTREMELY bugging, alot of things can make this plugin mess up and lock winamp, and secondly, like everyone else said, get rid of win98, very unstable OS, a good uptime for 98 is 1 week. I suggest NT or 2000, where you can get great uptimes...

[weed]

If all else fails, GO WITH LINUX http://forums.winamp.com/ubb/smile.gif

[Jay]

Also back when I ran on 98, my uptime perfomance regularly relied on my ISP's Stability.

If there was alot of network connectivity issues (like static in the line) I use Broadband. Then 98 would last 10hours on a good day, after they came out and serviced my Cable line, I could stay up for days, but never more than a week, if you want a true 24hour station get NT or 2K, I use 2K now, and can leave my station up for months. (still haven't seen a crash)

I am on a PII 350 with 64MB RAM running Windows2000 Advanced Server.

------------------
KXRM
http://www.shoutclub.com/
"Broadcasting with the Web in Mind"

[Jim]

Thanks once again to all the replies. I'm definitely leaning toward NT from reading these responses, although Linux is an attractive alternative as well. Thanks again, keep 'em comin' if you have any more advice.

[NeoAlphaOmega]

For whatever it's worth, I switched my Shoutcast server over from NT 4.0 Enterprise Server to a Windows 2000 Advanced Server Configuration, and I actually ended up with a better baseline and more resources available. In other words, it ran faster http://forums.winamp.com/ubb/smile.gif

The only factor that I want to bring up concerning this is that when I ran DCPromo and tested the effects that Active Directory would have on my new 2k Advanced Server install, it really put a drain on the system. My server is currently configured with DNS Server, WINS Server, DHCP Server(for my internal LAN), Shoutcast Server, ISA Server (firewall/proxy), and with websites and ftp servers for 8 domains, so my AD on top of this may have had a larger impact than it would on most. I would suggest running 2k advanced server if you have that option available to you, and just not configuring active directory on that particular server.

[Donald]

this is so much harder than Destiny.

Here I am with three programs, Shoutcast, Winamp and
Audio Solutions SAM-broadcaster. So what the heck
do I do with this mess.
I am supposed to install a dsp into winamp but what files.
Could someone help me out here, thanks.

[Shirow]

I ran on Win2k for a bit but ended up back on Win98, I had a lot of problems with it (I think due to crummy hardware)

However, when Win2k worked right, it was a dream - the station was up for about 3 weeks before I had to reformat the drive.

[terracomm]

First Jim -- A couple of things. I think your most recent down-turn in up-time is due to the WinAmp version 2.7, I too upgraded to this version and noticed a dramatic shift in my up-time, with my WinAmp freezing like clockwork every four or five hours. I un-installed the 2.7 and re-installed the 2.65 I was previously using, and voila I am back to my standard up-time of between 3 to 7 days on Win98. To bad, too, because the sound is dramatically better on the 2.7 version, oh well. Second, my absolute BEST results for up-time has been with using Win98 and WinAmp but streaming to a linux box containing my ShoutCast Server. This combination has allowed me to get up-times of upwards of two or three weeks. Mind you, both the Win98 box and the Linux box were task-dedicated and on a broadband pipe, so....

Donald -- I too am a veteran of Destiny. E-Mail me with your questions and I will be glad to help. PEACE and Happy Holidays all.