similar to: Icecast's YP bugs

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

On Sun, Aug 03, 2003 at 06:50:56PM +0100, Karl Heyes wrote: > > > We've been having a major problem with our icecast servers, some streams > > are being sent to the YP servers and others are not, and yes the public > > bit is set as confirmed by connecting to the streams directly and > > looking at the headers they send. > > There was a header mismatch, make

At 03:58 PM 7/8/2003 -0400, you wrote: >That isnt the only bug. One one of our icecast servers the third >stream, sf-lofi.mp3, is not being announced to YP servers at all. On my >local diagnostics (logs all connections to the liveradio.indymedia.org >YP server) I see that icecast isnt even trying to add it. The other YP >servers are not showing this stream either. It doesnt

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

On Mon, Aug 04, 2003 at 02:09:58AM +0100, Karl Heyes wrote: > > Who said that the protocol had changed, libshout still sent what it had > before and I don't in fact know when the protocol was last changed. So > saying it keeps changing is completely wrong. Also the YP servers don't > see this part anyway. I thought that you had said that they source-server protocol had

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

On Wednesday 25 June 2003 15:11, Arc wrote: > 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

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

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

On Wednesday 25 June 2003 15:55, Arc wrote: > 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

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 Stephan, I am talking about the meta-data: Artist - Song. It's weird because you are the second person on the list who doesn't get it working in Real... I just tried again with "BEK_dns" and "Radio Alcanzando Naciones" the 2 first MP3 radios I found in the stream directory and everything worked perfectly for Real (but not for WMP). In RealPlayer, I clicked

I was a bit confused by that statement as well Lee. I've done a bit of work with mp3PRO using a source developed from scratch and a version of the original Icecast modified only trivially to deal with specific metadata requirements. There is a very high level explanation of mp3PRO at the http://www.mp3prozone.com/basics.htm site. At the risk of being somewhat incomplete i will add: 1) The

On Thu, 14 Aug 2003, Arc wrote: > "Origional" Icecast (icecast1) uses ICY protocol for streaming, being > compatable with Shoutcast to the point that you can use a Shoutcast > client to connect to it. The same is not true for Icecast2. This is not correct, or at least is not meant to be. icecast2 is meant to be able to accept connections from ICY sources. Some people,

Hi Karl, Thanks for your help, About the "Connection:" header, you are right, it's: "Connection: close" and NOT "Connection: keep-alive". The protocol when the SERVER sends the data is http 1.0. It's http 1.1 when the browser requests the data. I don't understand the "Content-Length: 54000000" header either. Also I noticed the flash player on

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>