similar to: Shoutcast compatibility suggestions

Hi all, I have been Shoutcasting for six years now but am looking at using an Icecast server because of its active and ongoing development. I have broadcasters who use Shoutcast-compatible tools so the Shoutcast compatibility is important to me. I downloaded the latest version of Icecast and used the supplied configuration file for Shoutcast compatibility as a template. I can in fact connect

On Wed, Dec 29, 2004 at 08:49:54AM -0600, oddsock wrote: > So, while technically you could connect 2 (or more) Shoutcast > DSPs to icecast, you would have no way to map the metadata updates from > those 2 to the correct mountpoints. It may be possible to do this based > off the port the request came in on (that would then require you to setup a > set of

At 12:32 AM 12/29/2004, you wrote: >Hi: > >Ok, I've not managed to find any documentation on the shoutcast >compatibility introduced in icecast 2.2.0, so please humour me if I >missunderstand how it's meant to work. > >This is my understanding of it currently: > >1. You configure Icecast (as shown in the shoutcast example) so that >shoutcast connections

On Saturday 19 April 2003 00:53, Daniel Seebald wrote: > Hmm...so how does it work? I already tried it without success. > The Shoutcast DSP Plugin doesn't support the option to specify a > mountpoint for mp3-streaming on icecast2 so I wonder how I could > connect with the DSP. > There was a recently fixed bug that may have caused this problem in some circumstances, it's

Hi all, I set up a icecast server 2.3.2 with two shoutcast listeners (port 8000 and port 8002). What I have noticed is , if I have only one "DSP" source that stream to the first listener (on port 8001), audio become available on both listener ? Meaning that a player will open with success on http://myhost:8000/stream or http://myhost:8002/stream with the same audio. With two source,

Hi, I happened to need the shoutcast compatibility today and used it for the first time. Apart from reminding me of my earlier suggestion regarding this which would allow more than one shoutcast compatible port (see thread starting at http://lists.xiph.org/pipermail/icecast/2004-December/008120.html), I discovered some inconsistant behaviour. I notice that the shoutcast port wants the

Hi: I have some people who want to be able to broadcast using a shoutcast DSP plugin with MP3, to an icecast2 server. But we can't get it to work. Since I can't be bothered booting one of our boxes into windows to try the shoutcast DSP itself, I decided to use darkice in shoutcast mode. I know this works with shoutcast servers. anyway, it connects, but only briefly, and then is

Thanks for the quick response, Philipp. I'll specify the mount and see if that fixes my problem. For what it's worth, the following appears in the icecast.xml which came with my download of 2.4.2 just beneath the authentication section. Is there help I can offer in removing this section from, or correcting it in, the file for future packages? set the mountpoint for a shoutcast source

On Friday 18 April 2003 23:53, Daniel Seebald wrote: > but a shoutcast source can't connect to an icecast2 server, can it? Yes, it can. It's even been tested! Mike --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to 'icecast-request@xiph.org' containing only the word

Hi all, I have set up a an icecast server and have a Shoutcast DSP source connected. Is it possible to set up multiple shoutcast compat ports and shoutcast mount points. When I try to set up another port pair (8700 and 8701) and connect it says that the shoutcast mount point (live.nsv) is currently in use. I set up a seperate mount point in the <mount> config and it also will not use the

On Saturday 19 April 2003 01:17, Daniel Seebald wrote: > Do I have to manually configure these mountpoints in the icecast > configuration file? > And if I have to, what shout be the username for the shoutcast dsp? Or > can it be just > anything I like? No, you don't have to configure the mountpoints in icecast. Mike --- >8 ---- List archives:

Just wanted to let everyone know that we are prepping for a 2.2.0 release of icecast. Just as before, we are doing Release candidates first, and if no bugs are reported, these will become the official release. We ask that anyone that can, please test the RC and send any issues or bug-reports to the mailing list or http://trac.xiph.org/ until the mirrors get updated, please download the release

Hello. I'd like to broadcast my Winamp audio via the Shoutcast DSP to my Icecast server. According to all i've read, this can be done and should be simple, but I can't get it to work. Here are details for how my server is set up. Anyone spot anything obvious? The Icecast version is 2.4.2 on Windows 8.1 I have only the default listen socket defined. <listen-socket>

I'm not sure if this is an icecast issue or oddcast issue or both, but the latest Winamp (v5.22) is not now playing AAC+ streams encoded with Oddcast. Winamp v5.21 and earlier versions work fine. This may be some attempt by Winamp developers to force people to use Shoutcast, or to prevent oddcast from using their enc_aacplus.dll. Right, just took some time to set up the Shoutcast DSP to

Hi: I know it's possible to listen to a stream mounted on a mountpoint using winamp. I'd like to know if it's possible to make the shoutcast DSP plugin source a stream on a mountpoint? If so, how do you do it? Does the version matter? If you can't, will plugins like oddcast do it? Geoff. --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage:

Just so you know the what's happening with the competition, Nullsoft has released Shoutcast DSP v1.90 supporting AACPlus encoding for free. http://www.shoutcast.com/downloads/shoutcast-dsp-1-9-0-windows.exe The shoutcast website hasn't been updated yet. You need Winamp v5.1 which includes the AAC+ encoder DLL. Regards, Ross.

I have successfully set up a system with Ices0.4 and IceCast2.20 (and Tunez). It plays well using mpg123 or WinAmp. But I would like to use also my KiSS DVD player for the stream, and I have not been able to do so - It appearently needs 110% SHOUTcast compatibility. So I tried the IceCast2.3.1 - but it still didn't like the KiSS (or the other way around). In stead, I have added a SHOUTcast

----- Forwarded message from owner-icecast@xiph.org ----- Date: Mon, 12 Mar 2001 15:46:10 -0600 (CST) From: Scott Weingartner <scott@john.ikansas.com> To: Icecast List <icecast@xiph.org> Subject: [icecast] Anyone Know Shoutcast? In-Reply-To: <a05100100b6d2ec751b7b@[193.252.11.95]> Message-ID: <Pine.LNX.4.21.0103121541140.26914-100000@john.ikansas.com> MIME-Version: 1.0

I've been thinking more about this. It would be really nice if Icecast could add a port to a mountpoint and emulate whatever information Shoutcast requests when it relays a shoutcast stream. This way Shoutcast could relay Icecast streams. Fred _____ From: Fred Black [mailto:fred@batanga.com] Sent: Monday, July 18, 2005 2:36 PM To: 'icecast' Subject: RE: [Icecast]

I believe that Oddsock is using a Content Type of aacp. Using a .aac extension with this Content Type may present a conflict. This might actually be by design. I will do some further testing with Winamp and report here tomorrow. I will also double-check with the developer of Winamp for complete clarification. FYI, Orban Opticodec-PC allows the use of either Content Type of aac or aacp. aac is