similar to: relaying IceCast from ShoutCast

This is killing me... I've tried everything I can think of, but Icecast still crashes if I define more than 10 listen-socket ports. Is there a limit that's not documented or is this a bug? I'm using the latest Windows build that OddSock compiled. Thanks for any help/ideas Fred -----Original Message----- From: Fred Black [mailto:fred@batanga.com] Sent: Tuesday, July 19, 2005

Ok, Found the issue, I needed to specify another listen-socket for the port I specified in the alias section. The alias works now, AND, I successfully relayed it to Shoutcast! <listen-socket> <port>8000</port> </listen-socket> <listen-socket> <port>8010</port> </listen-socket> <paths> .. ..

I Found some old posts with some syntax for this, but it does not appear to work. Should this work in the Windows version? Here's the line from the Path section of my config file: <alias bind-address="38.116.36.8" port="8010" source="/" dest="/Jazz"/> Fred -----Original Message----- From: Fred Black [mailto:fred@batanga.com] Sent: Tuesday,

I forgot something! We also have a even lower quality MP3 stream, so I need 44 listen-socket ports, not 22. The plan of moving Icecast to the "radio" servers will work because it's still under 10 (8). Fred -----Original Message----- From: Fred Black [mailto:fred@batanga.com] Sent: Wednesday, July 20, 2005 10:21 AM To: 'icecast' Subject: RE: [Icecast] relaying IceCast

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]

Hi; Has anyone successfully relayed an Icecast stream using Shoutcast? I realize that this is backwards! However, several organizations that want to use our streams use Shoutcast, I really don't want to setup shoutcast and Icecast, but unless I can relay an Icecast stream with Shoutcast, I'm going to have to. Thanks, Fred -------------- next part -------------- An HTML attachment was

On 7/20/05, Fred Black <fred@batanga.com> wrote: > This is killing me... > I've tried everything I can think of, but Icecast still crashes if I define > more than 10 listen-socket ports. Is there a limit that's not documented or > is this a bug? I'm using the latest Windows build that OddSock compiled. It's a hardcoded limit (MAX_LISTEN_SOCKETS in the source)

Is this a new build? 7/30/05 version.. Where can I find the changelog on it, as well as features setup. Sorry about the ignorance, I just now saw this part of it. Also, what is the buildtree? You can respond back private if you don't want to send this to everyone. Much Thanks ~Doc -----Original Message----- From: icecast-bounces@xiph.org [mailto:icecast-bounces@xiph.org] On Behalf

Hi ! Well what I basically want to do is set up a local relay in our company for some popular shoutcast radio streams available on the winamp.com main site. Right now like 10 or 20 ppl here are listening to basically the same two or three streams, so thats quite a waste of bandwith. So I thought there must be some kind of stream relay that would connect as client to the Shoutcast server and be a

Hello List Having great trouble relaying an icecast2 mp3 stream to a shoutcast server. My client program successfully streams to icecast which is listening on port 7000. I can listen to this stream with mozilla and xmms with no problems. I can also stream my client directly to the shoutcast server but it makes the client unstable (which is why i'm attempting a relay). The shoutcast server is

I set up an Icecast server yesterday to relay a Shoutcast server with on-demand off. This was working yesterday for several hours at least but today it wasn't relaying the stream. I restarted the server and it started working again. Does Icecast handle reconnecting if the Shoutcast server goes down for a few minutes, etc? What would be the problem? I've switched it to on-demand to see

btw i just noticed that the icecast2 relay sounds fine in whamb (mac os x mp3/ogg client). so it does seem that some clients don't have the problem. here's the relay configs we're using: <relay> <server>server.to.be.relayed</server> <port>8000</port> <mount>/</mount>

Hello, I would like to put my server Shoutcast in relay with my server Icecast. But I does not understand how to make. You will find my config below. <!--<master-server>67.43.228.244</master-server>--> <!--<master-server-port>8001</master-server-port>--> <!--<master-update-interval>120</master-update-interval>-->

Hi: Let me see if I understand what you're doing. You're using winamp (or whatever) to stream to a shoutcast server which pushes a relay on to live365 (or live365 pulls from shoutcast, same deal really). Now you've got a second winamp with samcast trying to pull shoutcast or live365 and pass it to icecast. Is that right? OK. Firstly, there is no source connecting to icecast. The

On 20 Jul 2005 14:53:10 +0100, Karl Heyes <karl@xiph.org> wrote: > On Wed, 2005-07-20 at 14:33, Fred Black wrote: > > This is killing me... > > I've tried everything I can think of, but Icecast still crashes if I define > > more than 10 listen-socket ports. Is there a limit that's not documented or > > is this a bug? I'm using the latest Windows build

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>

Just checked using RealPlayer Windows 10.5 latest release. This also glitches. This is more than likely due to the differences in metadata between SHOUTcast and Icecast2. This is exactly the reason I was asking for the exact differences between the protocols so I can help get these things fixed with the player folks. Real is not the only player with this problem. I may be in the AAC/aacPlus camp,

figured it out! I have a dynamically allocated IP address - and i was entering a dynamic DNS name in the shoutcast server config expecting it to be resolved. It wasn't. I entered the IP address just then and it relays perfectly! Will follow up with the shoutcast service support to see why my dynamic name isn't being resolved (perhaps it can't be with shoutcast?). re. 44.1 and

Geoff you are a genius! I have been at this for soooo long today and you are spot on with the solution. I had a feeling it would be something simple! thanks a lot :) Andy ----- Original Message ----- From: "Geoff Shang" <geoff@hitsandpieces.net> To: <icecast@xiph.org> Sent: Tuesday, April 05, 2005 1:53 AM Subject: Re: [Icecast] Using alias to relay Icecast2 to shoutcast

relaying a shoutcast stream via icecast2 is pretty much unlistenable -- it constantly stutters. for example, shoutcast relay -- http://205.188.234.1:8030/listen.pls icecast2 relay -- http://liveradio.indymedia.org:8001/sf-hifi.mp3.m3u --mark --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a