I'll give that a shot. To bad the winamp forums won't let me post yet or I'd
ask them as well. *frowns* Thanks.
----- Original Message -----
From: "Ken Scott" <shellworldradio@xxxxxxxxx>
To: <winamp4theblind@xxxxxxxxxxxxx>
Sent: Tuesday, March 28, 2006 6:49 PM
Subject: Re: a shoutcast query
If nothing else works, yes. To do what you want to do, there are going to have to be two instances of the Shoutcast server running. If the Windows version is only able to look at one config file, that being sc_serv.ini, then the only way to do it will be to install it twice, in two different directories, and run each of them with its own sc_serv.ini file, containing different port numbers for their servers. You may have one using port 8000 and the other using port 8002, for example. Then just set up a second encoder to stream to the second server, and presumably it will work. If it doesn't, then it may just not be possible to do what you're wanting to do via the Windows version of the Shoutcast server, in which case you should probably just set up a single stream, say at 32k, that everybody can listen to. And frankly, with limited bandwidth on a broadband connection, where you're only going to be able to serve a small number of listeners anyway, that might be the best way to go--if you have 256k up, with a 64k broadband stream and a 32k dialup stream, you're only going to be able to serve three listeners on the broadband and two on the dialup, for example. If you run a single 32k stream, you can serve eight listeners, and you won't have to be worried about who's dialup and who's broadband, or trying to run two servers, etc.
-- Ken, ShellworldRadio@xxxxxxxxx
----- Original Message ----- From: "Sarah" <kales2@xxxxxxx>
To: <winamp4theblind@xxxxxxxxxxxxx>
Sent: Tuesday, March 28, 2006 7:49 PM
Subject: Re: a shoutcast query
What, install shoutcast twice? I'm just making sure I understand.
----- Original Message ----- From: "Ken Scott" <shellworldradio@xxxxxxxxx>
To: <winamp4theblind@xxxxxxxxxxxxx>
Sent: Tuesday, March 28, 2006 5:21 PM
Subject: Re: a shoutcast query
That should work, right, assuming again that there's some way to make the second Windows Shoutcast server look for a config file of a different name. If all it's capable of recognizing is sc_serv.ini, I suppose what you'll have to do is set up two entirely different copies of the server in different directories and running them that way, so neither of them will get confused.
-- Ken, ShellworldRadio@xxxxxxxxx
----- Original Message ----- From: "Sarah" <kales2@xxxxxxx>
To: <winamp4theblind@xxxxxxxxxxxxx>
Sent: Tuesday, March 28, 2006 5:28 PM
Subject: Re: a shoutcast query
O yeah I use sam for my broadcasting already so I copy the SCServe.ini to someware else or name it SCServe1.ini and run the shoutcast dos prompt thngy once then use SAM to conect to both streams?
----- Original Message ----- From: "Ken Scott" <shellworldradio@xxxxxxxxx>
To: <winamp4theblind@xxxxxxxxxxxxx>
Sent: Tuesday, March 28, 2006 3:06 PM
Subject: Re: a shoutcast query
You need something like the Sam encoders from Spatial Audio, or else the most recent version of the Shoutcast plugin--I believe only the most recent one will do it, anyway. Either of these will allow you to set up multiple encoders to send multiple streams simultaneously. You would set up one encoder to send at the appropriate bitrate and to the appropriate port of your existing server, and then another with your desired parameters for the second server, whatever those might be. Basically, you'll just be doing everything twice, using different values for most of the various options.
-- Ken, ShellworldRadio@xxxxxxxxx
----- Original Message ----- From: "Sarah" <kales2@xxxxxxx>
To: <winamp4theblind@xxxxxxxxxxxxx>
Sent: Tuesday, March 28, 2006 4:46 PM
Subject: Re: a shoutcast query
lol. It is a windows server. do I use the dsp encoder to specify the port. and do I run a separate instance of the shoutcast GUI?
----- Original Message ----- From: "Ken Scott" <shellworldradio@xxxxxxxxx>
To: <winamp4theblind@xxxxxxxxxxxxx>
Sent: Tuesday, March 28, 2006 2:06 PM
Subject: Re: a shoutcast query
This is correct, in theory. I'm assuming this is a Windows server we're talking about here, and if so, that there's some way of telling it to look for either an ini file with a different name or in a different location from the default. If there is, you'd just need to specify alternate ports in the second ini file for the second server, and fire it up. This would be far more easily done in Linux/Unix, but then, so is must everything else.
-- Ken, ShellworldRadio@xxxxxxxxx
----- Original Message ----- From: "Chris Skarstad" <toonhead5@xxxxxxxxxxx>
To: <winamp4theblind@xxxxxxxxxxxxx>
Sent: Tuesday, March 28, 2006 3:58 PM
Subject: Re: a shoutcast query
Hi Sarah
Nope this is fine, cause ultimately you'd use Winamp to broadcast. Only trouble is, I'm not sure about it myself. My gut feeling is, you'd copy Sc_serv.ini to another location and then just make sure you have another copy of the stream running on something like 8002 or 8004 for your dial-up stream. when you broadcast, you're actually using both port 8000 and 8001. so see if that works. I've never tried it so I can't speak for it being correct. Someone else may have to confirm it.
At 03:11 PM 3/28/2006, you wrote:Ok. I have no idea if this is O.TO or not so hear it goes. I Set p a shoutcast server, but for only one stream. This is fine, but what if I have some dial up listeners who want to listen as well? do I copy the ScServe.ini file someware else or what? the directions are a bit confusing. If this is the wrong for this question. maybe there is a list I can post to for this purpose. Thanks.
Sarah Alawami
MSN: <mailto:chellist@xxxxxxxxxxx>chellist@xxxxxxxxxxx
skype: marrie1
AIM: marriewon
Don't talk with a full mouth ... or with an empty head
To post a message to the list, send it to winamp4theblind@xxxxxxxxxxxxxx
To unsubscribe from this mailing list, please send a message to:
winamp4theblind-request@xxxxxxxxxxxxx with the word unsubscribe in the subject line.
Archives located at:
//www.freelists.org/archives/winamp4theblind>
If you have any concerns about the list, post received from the list, or
the way the list is being run, do not post them to the list directly. Instead, please contact
the list owners at winamp4theblind-admins@xxxxxxxxxxxxxx
To post a message to the list, send it to winamp4theblind@xxxxxxxxxxxxxx
To unsubscribe from this mailing list, please send a message to:
winamp4theblind-request@xxxxxxxxxxxxx with the word unsubscribe in the subject line.
Archives located at:
//www.freelists.org/archives/winamp4theblind>
If you have any concerns about the list, post received from the list, or
the way the list is being run, do not post them to the list directly. Instead, please contact
the list owners at winamp4theblind-admins@xxxxxxxxxxxxxx
To post a message to the list, send it to winamp4theblind@xxxxxxxxxxxxxx
To unsubscribe from this mailing list, please send a message to:
winamp4theblind-request@xxxxxxxxxxxxx with the word unsubscribe in the subject line.
Archives located at:
//www.freelists.org/archives/winamp4theblind>
If you have any concerns about the list, post received from the list, or
the way the list is being run, do not post them to the list directly. Instead, please contact
the list owners at winamp4theblind-admins@xxxxxxxxxxxxxx
To post a message to the list, send it to winamp4theblind@xxxxxxxxxxxxxx
To unsubscribe from this mailing list, please send a message to:
winamp4theblind-request@xxxxxxxxxxxxx with the word unsubscribe in the subject line.
Archives located at:
//www.freelists.org/archives/winamp4theblind>
If you have any concerns about the list, post received from the list, or
the way the list is being run, do not post them to the list directly. Instead, please contact
the list owners at winamp4theblind-admins@xxxxxxxxxxxxxx
To post a message to the list, send it to winamp4theblind@xxxxxxxxxxxxxx
To unsubscribe from this mailing list, please send a message to:
winamp4theblind-request@xxxxxxxxxxxxx with the word unsubscribe in the subject line.
Archives located at:
//www.freelists.org/archives/winamp4theblind>
If you have any concerns about the list, post received from the list, or
the way the list is being run, do not post them to the list directly. Instead, please contact
the list owners at winamp4theblind-admins@xxxxxxxxxxxxxx
To post a message to the list, send it to winamp4theblind@xxxxxxxxxxxxxx
To unsubscribe from this mailing list, please send a message to:
winamp4theblind-request@xxxxxxxxxxxxx with the word unsubscribe in the subject line.
Archives located at:
//www.freelists.org/archives/winamp4theblind>
If you have any concerns about the list, post received from the list, or
the way the list is being run, do not post them to the list directly. Instead, please contact
the list owners at winamp4theblind-admins@xxxxxxxxxxxxxx
To post a message to the list, send it to winamp4theblind@xxxxxxxxxxxxxx
To unsubscribe from this mailing list, please send a message to:
winamp4theblind-request@xxxxxxxxxxxxx with the word unsubscribe in the subject line.
Archives located at:
//www.freelists.org/archives/winamp4theblind>
If you have any concerns about the list, post received from the list, or
the way the list is being run, do not post them to the list directly. Instead, please contact
the list owners at winamp4theblind-admins@xxxxxxxxxxxxxx
To post a message to the list, send it to winamp4theblind@xxxxxxxxxxxxxx
To unsubscribe from this mailing list, please send a message to:
winamp4theblind-request@xxxxxxxxxxxxx with the word unsubscribe in the subject line.
Archives located at:
//www.freelists.org/archives/winamp4theblind>
If you have any concerns about the list, post received from the list, or
the way the list is being run, do not post them to the list directly. Instead, please contact
the list owners at winamp4theblind-admins@xxxxxxxxxxxxxx
To post a message to the list, send it to winamp4theblind@xxxxxxxxxxxxxx
To unsubscribe from this mailing list, please send a message to: winamp4theblind-request@xxxxxxxxxxxxx with the word unsubscribe in the subject line. Archives located at: //www.freelists.org/archives/winamp4theblind> If you have any concerns about the list, post received from the list, or the way the list is being run, do not post them to the list directly. Instead, please contact the list owners at winamp4theblind-admins@xxxxxxxxxxxxxx
