similar to: How do I list in YP? icecast2 ices0

I thought the YP code was going to be fixed to use less resources so it could be used with other stream formats. It seems to be taking a long time. As it is now, Icecast2 is not a good solution for those wanting to be on a popular directory. I am forced to recommend using Shoutcast to my clients so they can get onto a popular directory. I would prefer to recommend Icecast2. Ross Levis.

I can understand wanting to boost the adoption of Xiph codecs, but I think restricting the directory to vorbis streams only will not help this endeavour. I can imagine it will just piss a lot of people, including myself, and give Xiph a bad name. I get very few listeners of my AAC+ stream now since this occured. The restriction is not an insentive to switch to Ogg Vorbis at all. The incentive

Hi Rob The stream format has nothing to do with your audio files. I probably have 70% MP3's and 30% Ogg Vorbis files, and 1 or 2 WAV files for jingles on my hard drive. I only encode new CD's to Ogg Vorbis. But my station is streaming in AAC+ format, and I have also streamed in Ogg Vorbis format simultaneously. There is no way I would bother streaming in MP3 format. It's 15+

it was fixed a long time ago actually. The current YP is now benefitting from the changes made by me (with help from Karl), and yet despite the requests from both Karl and I recommending that these streams be allowed again, it falls on deaf ears. Ultimately it's up to Xiph to decide, although I was hoping that when the objection "it performs badly so we turned off all non-vorbis

I only have mp3s and it doesn't make sense to me to change all of them to ogg. My MDA(windows mobile phone) plays mp3s with no problem. It uses them as ringtones. Its more widely used in my circles. Why would I and everyone else want to switch to ogg? What is the benefit? Why the shun on mp3? And I can stream at 64 and 32 which is great for those streams that will get a lot of

Jack Moffitt <jack@xiph.org> writes: > Now I see the problem. This will not cause anything to show up. You > have no sources. Eh? -> sources Listing sources [Id: 509] [Sock: 14] [Time of connect: 18/Feb/2002:20:55:14] [IP: 205.147.43.110] [State: 1] [Type: pulling relay] [Proto: x-audiocast] [Clients: 2] [Dumpfile/fd: (null)/-1] [Priority: 0] [Song Title: ] [Song URL:

This is my first time setting this up and having a problem. I don't know where the problem lies. Do the files need a special permissions? What is wrong with my setup? $cat icecast.xml <icecast> <limits> <clients>2</clients> <sources>2</sources> <threadpool>5</threadpool>

[Reposted here, silence on the icecast list, is this deliberate?] Once again, I'm clueless as to what is going on because I don't have the source or logs to yp.icecast.org. I am touching yp.icecast.org fine: [14/Feb/2002:01:39:22] directory_touch_xa([yp.icecast.org:80]) completed...server id = 69 but my radio station isn't shown. More details on my setup: xmms -> darkice

Once again, I'm clueless as to what is going on because I don't have the source or logs to yp.icecast.org. I am touching yp.icecast.org fine: [14/Feb/2002:01:39:22] directory_touch_xa([yp.icecast.org:80]) completed...server id = 69 but my radio station isn't shown. More details on my setup: xmms -> darkice 0.7 -> relay icecast server -> main icecast server

Hi all, 1. I recently noticed that yp.xml is still limited to 1,000 entries only while the web directory says there are over 21K streams. I remember some discussions regarding the bandwidth required to serve this file, so is it possible to get it in compressed format? Here are some figures: - the yp.xml as served now (1K entries) is 343 KB. This means 21K entries will be around 7 MB. -

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 >

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

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

I am trying to connect to an icecast2 server that I have running on redhat 9. Via Ice0. Here are the errors that I am getting. Any help would be greatly appreciated. Kris. <p>[root@wyatt icecast]# ices -m mymp3stream -c ices.conf -P hackme Unknown Node: Server Unknown Execution keyword: Base_Directory Logfile opened DEBUG: Sending following information to libshout: DEBUG: Stream: 0

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

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

The public URL of your Icecast server http://live.coolradio.rs <directory> <yp-url-timeout>15</yp-url-timeout> <yp-url>http://dir.xiph.org/cgi-bin/yp-cgi</yp-url> </directory> <directory> <yp-url-timeout>15</yp-url-timeout> <yp-url>http://icecast-yp.internet-radio.com</yp-url> </directory>

hello, I have a stream which has been up and running for about 20 hours now. It's already in the yp.shoutcast.com, that happened within minutes. However, I would also like my stream to be in the yp.icecast.org list as well. How long should this take? cheers, t. (p.s. is under genre "jazz" in the shoutcast yp. the stream is http://194.109.227.136:8000, using liveice and