similar to: relaying IceCast from ShoutCast

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]

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

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,

Well, I've hit another problem: Icecast crashes if I define more than 10 listen-socket ports. I have 44 streams that I'm trying to relay via Icecast. It works just fine until I try to add the listen-socket port definitions. If I put the 11th one in, it will crash on startup without entering anything in the log files (log level on 4). I've use sysinternal tcpView to verify that the

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>

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> .. ..

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

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

The relaying-configuration seems to be straight-forward, unfortunately it does not work. That's my configuration: <relays-on-demand>1</relays-on-demand> <relay> <server>http://mp3stream7.apasf.apa.at</server> <port>8000</port> <mount>/</mount> <local-mount>/oe3.mp3</local-mount> <on-demand>1</on-demand>

HI , Sorry as I did not read all the thread , but I answer from here : 2011/8/8 Karl Heyes <karl at xiph.org>: > On 08/08/11 18:15, Raymond Lutz wrote: >> I've been reading posts on the difficulty in getting an icecast stream >> listed in the shoutcast directory. > you should be able to allow shoutcast to relay icecast by adding an > alias of / to /stream <alias

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>-->

I've been reading posts on the difficulty in getting an icecast stream listed in the shoutcast directory. Apparently, it is necessary to run the shoutcast server to do this. Before I go down a cheeseless rathole, I thought I'd pass this over this list to see what response I would get.

On Wed, Jun 25, 2003 at 11:34:07AM +1000, Michael Smith wrote: > > > 2) Should relay icy/x-audiocast stream metadata when connecting to > > icecast1/shoutcast/etc so that this information is available to YP > > Eh? It does. I even tested that with someone's shoutcast stream. It works. > Just add >

On Wed, Jun 25, 2003 at 04:27:58PM +1000, Michael Smith wrote: > > > > notice that, with exception of the last, they're all ice-* not icy-*... > > prehaps this is incompatable with the way most players operate to get > > stream data? Is this a typo? > > No. This is deliberate. There could be a bug in the code that takes these > headers and puts bits of them

On Sun, 5 Jun 2005, Iain Mott wrote: > 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

Just to refresh my memory, is it possible to relay a stream from elsewhere? We have a DSL line here and 2 machines that listen to the same shoutcast stream and dont want to clog the connection. Mind providing an example for that portion of the config? <p>Thanks in advance! Bryan --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage:

Hi, on my home server I'm using Icecast to stream my music, but a few days ago I decided to try to increase the number of listeners by using an external server with a greater band. The problem is that this server is Shoutcast and after a week I still can't to make Shoutcast relayng from my Icecast2. Is it actually possible to do this, or am I wasting my time? thanks very much Satrik

On Wed, Jun 25, 2003 at 03:33:25PM +1000, Michael Smith wrote: > > Is the metadata relayed to connecting clients. i.e. take a client that > supports shoutcast-style metadata, like winamp (and probably most others). > Connect as a listener to the relay. Do you get metadata? You should. If you > don't, the metadata relaying could have been broken (I think this is >

----- 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

Hi all, 2012/2/29 Tom Swirly <tom at swirly.com>: > On Wed, Feb 29, 2012 at 11:29 AM, Raymond Lutz <raylutz at cognisys.com> wrote: >> >> This is absolutely not "off-topic" and if this list will not support this >> VERY IMPORTANT discussion, then I will be happy to host the discussion on a >> different list for those who are interested. I have been