similar to: more directory questions

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 >

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

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 >

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

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

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

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

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

Thanks to Adam Greenbaum for recently helping me get libshout fully icy compatible. I'll be releasing a new libshout and libshout-perl this weekend, but int he meantime, you can grab the head of CVS for each and you'll get the same thing. Also, he tracked down some yp.shoutcast.com problems, and I have checked in a solution that lists icecast servers on yp.shoutcast.com once again.

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.

Greeting all -- I'm having some problems setting up multiple streams with iceS, for example, a hi-bandwidth and lo-bandwidth stream of the same audio. Could someone post a config that works in this case? thanks .oOo.oOo.o..o.oOo.oOo. Ben Wilson admin -- thelocust.org ben@thelocust.org 'OoO'OoO'O''O'OoO'OoO' --- >8 ---- List archives:

http://forums.winamp.com/showthread.php?s=&threadid=172236 its like they think there the only webcasting solution out there, does xiph have anyone promoting the directory for icecast.org? <p>Regards Dave St John Mediacast1 Administrator <p>--- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list,

Hello- You guys have done an excellent job with the Icecast2 server. I probably don't need to tell you that, but I did anyway. We are Coding Technologies licensees and have recently developed a streaming audio encoder supporting AAC/HE-AAC/aacPlus using RTSP/RTP, SHOUTcast HTTP/ICY, and Icecast2 HTTP/ICY, Orban Opticodec-PC. More information here:

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

We are pleased to announce Icecast 2.5 beta2 (2.4.99.2). This is a beta release and not recommended for production use. ## Downloads -   Source:     http://downloads.xiph.org/releases/icecast/icecast-2.5-beta2.tar.gz -   SHA256sum:     a83baf4ae3ee5c2822bcb4286b7438b01317ccb8387371922e9cd32fe1c453e8 -   Packages:     https://build.opensuse.org/repositories/multimedia:xiph:beta ## New features

We are pleased to announce Icecast 2.5 beta2 (2.4.99.2). This is a beta release and not recommended for production use. ## Downloads -   Source:     http://downloads.xiph.org/releases/icecast/icecast-2.5-beta2.tar.gz -   SHA256sum:     a83baf4ae3ee5c2822bcb4286b7438b01317ccb8387371922e9cd32fe1c453e8 -   Packages:     https://build.opensuse.org/repositories/multimedia:xiph:beta ## New features

I have a weird one... I installed icecast 2 and ices .23 on Mandake, and am not having any luck I compiled and installed the nightly icecast just today. It seems to work fine, however when I telnet to it (10.0.0.3, port 8000), I am unable to login unless the first line contains ONLY the password. I used ethereal to see that iceS is trying to send to authenticate, and it is sending (as the first

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

On Sun, 7 Mar 2004, oddsock wrote: > neat, how ironic is it that you can stream mp3pro with the Shoutcast DNAS, > but their YP will not let you list if you do so...talk about your mixed > messages... I think what they're trying to do here is not only block non-SCDNAS servers, but also as many non-Shoutcast sources as they can. Think about it - if you're streaming MP3Pro without