similar to: yp.shoutcast.com

My icecast server (1.3.11) has been getting 404 errors for the past couple of days from the yp.shoutcast.com server. If I send the URL manually by telneting to the webserver at yp.shoutcast.com I get the following response: [chrisp@ayeka httpd]$ telnet yp.shoutcast.com 80 Trying 205.188.234.56... Connected to scastlb1.shoutcast.com. Escape character is '^]'. GET

Scott, > Thats what i do.. just relay. Exactly how are you doing it, and what software are you using (shoutcast version / icecast version / what streaming software are you using)? I'm running icecast 1.3.10, shoutcast 1.8.0, and irpd 0.16 to stream. When I try to relay from shoutcast to my main icecast server, I get the following: <03/15/01@22:38:06> [main] dns thread starting

unfortunately, the kind folks over at Nullsoft axed all icecast entries on their YP... Quote from Tom Pepper : "I also had to pull support for icecast today from the directory, since I found no less than 40% of the server operators sending in doctored listener counts. garf." oddsock At 09:25 AM 1/23/2002 -0600, you wrote: >My icecast server (1.3.11) has been getting 404 errors

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 >

Hi, I've been running Icecast on my server for over five months now and am having lots of problems with it. I must have pulled out half of my hair on this product, mostly due to lack of support. (I mean, have you ever gotten an answer to your question at icecast.org?) I've tried it all: sc_serv, Icecast, shout, ices, streamcast, liveice. I could greatly use any help. I am using the

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 >

yes this is darkice. perhaps we could work in 'icy-public' support...? --mark On Tuesday, Jul 8, 2003, at 19:58 US/Pacific, Arc wrote: > On Tue, Jul 08, 2003 at 03:40:42PM -0500, oddsock wrote: >> what source client is generating that ? > > I believe they run darkice, Mark Burdett would have to supply more > specific details as this is a relay of their lofi-mp3

I'm using Icecast 1.3.11.. It connects to yp.icecast.org and yp.mp3.de just find.. it looks like it's trying to go to http://yp.icecast.org/cgi-bin/touch However, the shoutcast one says: completed...server id = -1 While the others say: serverid = 69 <p>Has Shoutcast changed something, so that icecast can no longer find Shoutcasts directory? -- Arathena Email:

At 05:31 PM 6/25/2003 +1000, you wrote: > > I'm not concerned with how players see anything right now, tho that is a > > concern I guess. I'm concerned with getting the vitals - the stream > > name, genre, and description, to be relayed to a YP server when Icecast2 > > is relaying a Shoutcast stream. Currently it does not, this is missing > > functionality

Ok I've been discovering many bugs in Icecast's YP implementation.. The most serious of which is, if a YP server is rejecting a stream the server has a memory leak which, as it continues to re-try to publish it's rejected streams, grows until the server segfaults. On our server, for instance, we're relaying shoutcast streams (which does not relay the stream name and other

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Michael and thanks for answer! On Tue, 13 Jan 2004, Michael Smith wrote: > This shouldn't be being passed to _check_pass_icy() at all - this isn't the > "icy" (shoutcast nasty ugly) protocol at all. We support that (icy) protocol > because it's widely used - but it's a horribly ugly hack to pretend that

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

In trying to find out why neither icecast nor shoutcast no longer lists my radio station (I thought it might be the connectivity issues which plagued me this month), I find this: >> unfortunately, the kind folks over at Nullsoft axed all icecast entries on >> their YP... >> Quote from Tom Pepper : >> >> "I also had to pull support for icecast today from the

Some of the ices config files were pointing at localhost for the host name, even though the Icecast server is specifically told which IP to listen on. I changed them to make sure they matched. Here's some more info on our configuration: We launch three instances of Icecast, each with it's own configuration file that listen on different IPs and different ports (8000, 8001, 8002). Ices is

Mike hodson <mystica@darktech.org> writes: > Might I ask -how- precisely they banned all icecast servers. Perhaps the real question you should ask is..."should" anyone worry about this at all? Personally speaking, I've been streaming for quite a while (barring a few networking problems) and I've always seen the same behavior from the shoutcast (Nullsoft) people.

At 19:57 2/27/2001 -0600, dj66 wrote: >Hi, I've been running Icecast on my server for over five months now and am >having lots of problems with it. I must have pulled out half of my hair on >this product, mostly due to lack of support. (I mean, have you ever gotten >an answer to your question at icecast.org?) I've tried it all: sc_serv, >Icecast, shout, ices, streamcast,

At 04:30 PM 7/8/2003 -0400, you wrote: >On Tue, Jul 08, 2003 at 03:10:25PM -0500, oddsock wrote: > >Already checked that. this is the HTTP header for the stream: > >Content-Type: audio/mpeg >icy-bitrate:16 >icy-description:SF Indymedia >icy-genre:Talk >icy-name:Enemy Combatant Radio >icy-public:1 >icy-url:http://sf.indymedia.org/ >Server: Icecast 2.0-alpha2/cvs

Maybe this is the wrong place to post, but... When trying to start up liveice to a shoutcast server I'm getting the following error, and then it dies and screws up the terminal emulation for my session. Anyone seen this before? LiveIce Streaming Mpeg Audio Generator Input Mode: Direct

The ice-* headers are the standard protocol for connecting to icecast2, the trouble is making all source clients adhere to the standard. The option is to be very militant about it, and basically deny any source clients that do not connect with the ice-* headers , but we chose the more compatable route...although there is a limit to this compatability....I would strongly urge darkice to use

According to what I've read on this mailing list, it should be possible to stream MP3 data to icecast2 using ices-0.2.3, which I assume also should be the case for any other streaming client based on libshout1. So I decided to test this out to see if we really could dispense with icecast1 altogether on the server I help administer. My results were not promising, to say the least. I wiped out