similar to: lots of icecast help needed

> >First, my server isn't being posted to yp.icecast.org or yp.shoutcast.com. > >Error results: > >WARNING: Connect to yp.icecast.org failed > >directory_add([yp.shoutcast.com:80]) failed, could not connect. (retry in 0 > >seconds) > > I can't say for sure what could be causing this, but I'm having problems > with yp.shoutcast.com myself. I get:

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,

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

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

Folks, I've been running an icecast server for about a year, and never really had the chance to test it out on the other side of our Internet link. We've had a lot of people trying us out, but very short connect times in the whole. I finally got a cable modem at home, tried having a listen, and found the stream to be very stuttery. So, first things first, I went and grabbed the

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 >

Another, but more recent problem, I am having is Live365. I haven't done much work with it, but can you relay to Live365 properly? They give me an ip and it works, but I don't show up in their listings, and the song title doesn't show up in the client's mp3player. (whereas if someone listens to the local broadcast they do get the song titles). Using latest, from CVS, Icecast

Scott, > If you go look at the result codes for errors, it says this for #3: Where are these codes, in the source or somewhere on shoutcast's website? > once you fix this.. You'll get error #404: > > 404: This typically means you're running software that isn't a > SHOUTcast > DNAS server. The only supported software for listings in the > SHOUTcast

I have setup a stream running icecast 1.3.7 and liveice. I would like lto list my stream in the icecast directory, but I dont want the song being played to show up in the dir listing. How can I suppress this? Thanks, vikas _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com --- >8 ---- List archives:

I have the same problem below; does anyone know what the problem is with that and how to fix it -- I haven't seen any response to the message below .. Louis > Hello, > > I'm struggling with getting my stream at the various directory services > out there. Here are my experiences with icecast up to and including > 1.3.9, which I installed today. I've had the same

At 23:25 3/15/2001 -0500, you wrote: >Asym, > >What streaming program are you using? I'm using icecast 1.3.10 with meta >data turned on and it doesn't want to list on yp.shoutcast.com. Can you >e-mail me your icecast.conf and your streaming config file via e-mail? >Thanks... I'm running icecast 1.3.10 on FreeBSD 3.5-Stable, and my source is Winamp 2.72 w/

I don't see that Nullsoft can do anything about it if Icecast was modified to update the SC directory exactly emulating SC Server. We would then utilize Icecast server for all our hosting, which is much more flexible. But our customers cannot do without being listed on the popular SC directory. Currently we have about 98% SC servers and 2% Icecast. -----Original Message----- From:

It has long been known that the nullsoft method of streaming metadata is a hack. I like the Icecast approach much better but still I think that it can be much improved. When in doubt turn it off. Two machines?? Have you tried the win32 source lately...? Just a thought. Lithium ----- Original Message ----- From: "dj66" <route66@machineandsoul.com> To: <icecast@xiph.org>

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

jaromil, > > > > wanted to ask again if someone has some online documentation on the > > icecast (or shoutcast) protocol at the socket/data level. > > have a look into MuSE/libmpeg/httpinput.cc (http://muse.dyne.org) > i hope that code can help you figuring out > No actually not. It just makes the connection to the shoutcast/icecast server. I've gotten this

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 >

Hi Everybody, It works with Peercast because Peercast receives the headers from Icecast2 and sends its own headers back to the client (Winamp, WMP, Real...). Remember that Peercast is a client AND a server... I guess Peercast doesn't send back the headers in the same way than Icecast2. Maybe Peercast doesn't use ICY/X-audiocast. Talking about Real (v9.0 and 10), I already got the

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

Hi, Could anyone tell me about the different login schemes sources can use to connect to IceCast, ShoutCast, etc? From what I can tell: ShoutCast uses something called icy login? IceCast uses something called x-audiocast, but can also use icy? IceCast2 uses what? Also, where can I find details about these login schemes? I sort of figured out a basic use of x-audiocast by looking at the JScream

I saw a post a minute ago and stupidly hit the delete button instead of reply, so no quoted response but.. You don't have to relay to a shoutcast server to get listed on yp.shoutcast.com. You probably have metadata disabled, and they won't list you without it. I know it's "experimental" in the config file, but I haven't had any problems with it since icecast 1.3.9,