similar to: YP Directory

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

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

I wanted to let folks know that I had a problem with unreliable, and mostly dysfunctional listing of a server's mounts on YP directories. This server has a few dozen mounts. If all the relays and sources were connected, YP wouldn't work; if only some were connected, YP would start working. I had to increase the <yp-url-timeout> for all the <yp-url>'s to a much larger

Greetings icecasting amigos! I?ve had an incredibly frustrating journey getting a new icecast origin server going to supplant an older machine set for retirement. The setup is relatively simple ? a beefy Debian bookworm host running icecast as a relaying slave pulling the streamlist from an icecast2 2.4.4 ingest server, for mass distribution. The ingest / origin server runs fine. I opted for

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

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

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

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

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 am writing to see if icecast can be configured to send a stream update to StreamFinder.com in a similar manner to the way it handles talking to shoutcast yp. ? We would like to be able to offer live updates of icecast servers on our site for our visitors and broadcasters... In the config - this is the current xiph yp update part <directory>

On Mon, 2005-07-25 at 23:55, mark burdett wrote: > For 100% reliability I ended up removing dir.xiph.org from my > list of YP directories. My guess is it was taking too long to > respond to requests, which could be a problem if an icecast > server has a large number of mounts. But it could be a > problem unique to me (I'd be curious to know if anyone else > has had

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, On 2 Sep 2024, at 12:19, Marek Dziembowski wrote: > Greetings icecasting amigos! > > > I?ve had an incredibly frustrating journey getting a new icecast origin server going to supplant an older machine set for retirement. > > The setup is relatively simple ? a beefy Debian bookworm host running icecast as a relaying slave pulling the streamlist from an icecast2 2.4.4 ingest

At 10:08 AM 7/8/2003 -0400, you wrote: >On Tue, Jul 08, 2003 at 11:36:10AM +0100, David Jones wrote: > > and Ross Levis wrote: > > > Sometimes when I restart my stream it appears for a while without > > > updating the title etc and then disappears a few minutes later. I'm > > > sure Dave will fix it eventually but he is away for the week. > > >

should there be a constant GET /admin/streamlist on a relay main server ?? this may be my problem ; what would cause this to stop updating ? but still remain running .. -- access.log on main server ( not relay ) 130.63.239.188 - - [03/Apr/2003:21:14:48 -0500] "GET /admin/streamlist HTTP/1.0" 200 46 "-" "-" 0 130.63.239.188 - - [03/Apr/2003:21:16:48 -0500] "GET

Good Day, Looking at the SVN repo: there's 30+ commits since the 2.6.2 release; the last one from August 2009. Are there any intentions to roll a release anytime soon? Are there any more recent branches? I'm currently looking into extending icecast2 (more below) and am wondering if I should base the patches on 2.6.2+debian-fixes or work from svn-trunk? We are using a cluster of icecast

I think I have everything set correctly, but still not getting there. Requested data: <hostname>stream.wortfm.org</hostname> <listen-socket> <port>8443</port> <ssl>1</ssl> </listen-socket> <listen-socket> <port>8000</port> <!-- <bind-address>127.0.0.1</bind-address> -->

Hello all - In the interest of getting an open, mp3-compatible YP directory available to the public, I have begun www.openradiodirectory.org Directions for YP listing are here: http://www.openradiodirectory.org/list.php It's a 100% fresh YP implementation in PHP/MySQL. Touch frequency is currently at four minutes while I work out some of the minor kinks. There's still a few rough

One more thing needed ? <!-- The certificate file needs to contain both public and private part. Both should be PEM encoded. --> <ssl-certificate>icecast.pem</ssl-certificate> ? This needs a path to the PEM file ? Icecast needs to know where to find the file. ? Tony ? _____ From: Icecast [mailto:icecast-bounces at