similar to: icecast.xml syntax for relaying.

> behavior you are seeing....(that also is a difference between iceast1 and > icecast2 - no server-side buffering in icecast2 and there was in > icecast1)... What do you mean stream buffering? We never buffered in either version that I remember. If you fall behind, you get kicked. It's always been that way. jack. --- >8 ---- List archives: http://www.xiph.org/archives/

I'm relaying an icecast1 mp3 stream with icecast2. This works fine, and the song title is displayed correctly no matter if I use <relay-shoutcast-metadata>1</> or not on the relay. But, the stream name and other metadata provided by ices0 on the icecast1 server is not displayed in the listening client. Icecast1 source: [Id: 1] [Sock: 11] [Time of connect: 09/Aug/2004:10:01:24]

Hi guys, Can anyone point me to some good icecast1 documentation? I looked on the icecast.org website, but the /docs link only list the icecast2 documentation now and the whole site is void of icecast1 documentation... Using icecast1 instead of icecast2 because I need on-demand-streaming... Thanks, Kelv

Greetings, I have some confusion. I've seen it mentioned, somewhere in some docs, that Icecast2 does not (as yet) support Push relaying. Is this actually the case? Should I be looking at icecast1 (which does support push relay, I believe) until such capability is implemented on icecast2? Or should I be creating a combination of both? Or what? Here's my situation: I have a customer

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 >

I guess as a mercy plee for help I'll mention why I need to have the static ogg files play as the mp3 static files play with icecast1. I'm the founder of the LPBN and I've recently made Richard Stallman's files available as downloads (it is a work that is still in process). Stallman has requested I make them available as streams as well as downloads. So is there anybody out

Hi All, I attempted to switch my MP3 server from Icecast 1 to Icecast 2 today. I run a Live365 station, Big Planet Radio, which simply relays my local Icecast server. My Icecast 2 error.log file shows a lot of the following messages when the Live365 server, Nanocaster 2.5.6, is connected to it: [2003-05-14 22:09:15] DBUG format-mp3/format_mp3_write_buf_to_client Client had recoverable error

Hi All, I attempted to switch my MP3 server from Icecast 1 to Icecast 2 today. I run a Live365 station, Big Planet Radio, which simply relays my local Icecast server. My Icecast 2 error.log file shows a lot of the following messages when the Live365 server, Nanocaster 2.5.6, is connected to it: [2003-05-14 22:09:15] DBUG format-mp3/format_mp3_write_buf_to_client Client had recoverable error

Hi Assorgia, It would be very nice if you could provide a network dump for both versions of Icecast1 and Icecast2. We could make comparisons of the results and maybe identify why Flash doesn't work with Icecast2. If you need it, I can help you by performing the tests on Icecast2/Windows but not on Icecast1 because I don't have any Linux box for the moment (I only found a version of

I have 4 instances of icecast running on my server. #Command to start icecast /usr/bin/icecast -c /etc/icecast.xml -b & /usr/bin/icecast -c /etc/icecast1.xml -b & /usr/bin/icecast -c /etc/icecast2.xml -b & /usr/bin/icecast -c /etc/icecast3.xml -b & I am trying to integrate an automated Let's Encrypt Certificate renewal. My testing found that I need to restart the icecast

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

This is in CVS, FWIW (that is, not much since the odds of 1.3.13 being released are epsilon close to nil). On Wednesday, 02 July 2003 at 11:38, Ned Wolpert wrote: > Folks, > I email abit ago about using 1.3.12 in my environment, and fixing a > dead-lock problem. Since 1.3.12 is 'obsolete', not supported, and GPL > I'm provided a patch to the mailing list of my

Hi Assorgia, Thanks for the flash animation. I think Icecast1 might be the solution. I am just a little bit scared by the message "Note that icecast 1 is deprecated and unsupported, and may possibly induce nausea in small children, hair loss in men, and estrogen fluctuations in women" that appears on the download page. I have a nice blond hair of "Principe Azzuro" that I

I've gotten a request from another broadcasting partner to set up yet another streaming audio server. They would like to stream in both ogg and mp3 formats from off a single icecast machine. I have been searching through the archives and I have seen this mentioned as being possible, but no real configurations. I would of course place LAME on the box and use that for streaming just as I would

> > ( icecast2 only handles .MP3 for fileserving , as far as i know ..) > > Nope. Icecast2 doesn't care about what the format of the files it serves is > for fileserving. (i meant :: .MP3 is handled for fileserving , but .MP3 is not avail for live reencoding, as far as i know .. ) for the record , the OGG streaming w/ icecast2 has been great . tho (seperate issue ) : OGG files

this is probably caused by the lack of buffering in icecast2. Their relay client may be doing some buffering in itself, and if it's expecting for there to be buffering on the server side as well, it might exhibit a behavior you are seeing....(that also is a difference between iceast1 and icecast2 - no server-side buffering in icecast2 and there was in icecast1)... fwiw, I am trying to

Hello again all. I want to thank Karl H. for pointing me to xiph.org/~karl and getting me some save files winamp likes the first time. That ucler is at an end. The next ucler involves two rather quick questions: I > In icecast1, when a user attempted to connect to the server, didn't it just kick them to the "default stream", where the default stream was the only stream being

Behold, gtgbr@gmx.net hath decreed: > Aaron Gaudio wrote: > > or developing for it. The fact that no release packages are available > > signifies to me that icecast2 is not yet ready for prime time. This > > Well, there are, see Geoff's mail ... those are official. Multiple > problems of pretty much any kind prevented Xiph.org from getting > icecast.org in order; I

Yes, the web players I've tested have a hard time parsing meta properly using only one instance with separate streams. Tested at least 6 of them looking for reliable meta and cross browser/OS compatibility. On May 29, 2017, at 10:23 AM, Marvin Scholz <epirat07 at gmail.com<mailto:epirat07 at gmail.com>> wrote: Any specific reason to run 4 Icecasts? On 29 May 2017, at 16:21,

Behold, Adon Irani <adon@YorkU.CA> hath decreed: > > the icecast2 developers be guilt-tripped into repeating icecast's > performance ? > _ is it not enough that OGG can have a streaming server that supports it ? Perhaps, if that is the only requirement to have a fully-functional streamer. Unfortunately, I believe this is not sufficient for the user base. So, if the