similar to: Icecast 2.1 RC2 Announcement

After 8 months in development, the icecast development team is pleased to announce Version 2.1.0 of Icecast. New features for 2.1 * Listener Authentication Icecast now supports listener authentication. This provides a mechanism for creating/maintaining users and passwords for listeners. Currently, we only have implemented a simple, file-based storage for users and passwords. New

After 8 months in development, the icecast development team is pleased to announce Version 2.1.0 of Icecast. New features for 2.1 * Listener Authentication Icecast now supports listener authentication. This provides a mechanism for creating/maintaining users and passwords for listeners. Currently, we only have implemented a simple, file-based storage for users and passwords. New

At 05:29 AM 11/6/2004, Dennis Heerema wrote: >Hi There, > >Is there a nice helpfile to telle me how to set up: apparently there was a bit of a disconnect on what actually is currently supported in 2.1 regarding this. Multi-level fallbacks are implemented, however the part about automatic cascading of clients between fallbacks based on their bitrate capability is not. Adding this

Hi There, Is there a nice helpfile to telle me how to set up: * Multi-Level Fallbacks Multi-level fallbacks allow for specifications of a series of fallback mounts that you could use, for instance, to set up a series of progressively lower bitrate streams that would be cascaded through. For instance, a modem user would connect to the highest bitrate stream, and then could be cascaded down to

Hi There, Is there a nice helpfile to telle me how to set up: * Multi-Level Fallbacks Multi-level fallbacks allow for specifications of a series of fallback mounts that you could use, for instance, to set up a series of progressively lower bitrate streams that would be cascaded through. For instance, a modem user would connect to the highest bitrate stream, and then could be cascaded down to

The Icecast development team is pleased to announce RC2 of Icecast 2.3. This will most likely be the final RC before the 2.3 release. We appreciate everyone who has tested the RC's so far. All bugs (for this release and all others) should be logged in Trac - http://trac.xiph.org. The downloads: Tarball : http://downloads.xiph.org/releases/icecast/icecast-2.3.0.rc2.tar.gz SRPM :

The Icecast development team is pleased to announce RC2 of Icecast 2.3. This will most likely be the final RC before the 2.3 release. We appreciate everyone who has tested the RC's so far. All bugs (for this release and all others) should be logged in Trac - http://trac.xiph.org. The downloads: Tarball : http://downloads.xiph.org/releases/icecast/icecast-2.3.0.rc2.tar.gz SRPM :

Ok, this bug has been identified, logged, and fixed in SVN. We will be most likely building an RC3 in short order... oddsock At 03:43 PM 9/9/2005, Joel Ebel wrote: >Playing around with it some, it seems to be related to the web >interface. If I don't touch the web interface it seems to stay running, >but when I start trying to view pages in the web interface it quickly dies.

Hello List Having great trouble relaying an icecast2 mp3 stream to a shoutcast server. My client program successfully streams to icecast which is listening on port 7000. I can listen to this stream with mozilla and xmms with no problems. I can also stream my client directly to the shoutcast server but it makes the client unstable (which is why i'm attempting a relay). The shoutcast server is

Hi, I installed from source using the tarball on the liquidsoap website. I installed curl as a prerequisite before building icecast from source. A version check shows that I have the current version of curl as follows: curl 7.52.1 (x86_64-pc-linux-gnu) libcurl/7.52. The first part of the log shows that YP server handling is disabled though. (I pasted a fuller snippet of the log earlier but it’s

Folks: I'm trying to set up a streaming server under Fedora Core 2 using Icecast 2.2.0. Everything compiles; everything runs. There are no indications of a problem in any of the log files. When I look at http://192.168.0.128:8000/status.xsl, everything looks ok. But when I click on "Click to listen", it brings up xmms, but there's no indication of audio, and xmms shows a bit

hi all how do i editing line that has to be uncommented so that the server starts?? <icecast> <!-- location and admin are two arbitrary strings that are e.g. visible on the server info page of the icecast web interface (server_version.xsl). --> <location>Earth</location> <admin>icemaster at localhost</admin> <limits>

This press release went out on a limited basis, but no one seemed to notice the good parts. Read about the contest, and start looking for bugs :) ---- Xiph.org Foundation Announces Ogg Vorbis Release Candidate 2 Featuring Bug-Hunting Contest on the Path to 1.0 The Xiph.org Foundation is proud to announce the latest release candidate of the Ogg Vorbis open source audio codec. This new

Hi, I am running Icecast 2.1.0 on a Debian Sarge with a 2.6.8 Kernel. After upgrading to the new version i have the problem that the icecast2 process. It is regularly dying after running 20-26 hours. There are no messages in the icecast logfile nor in any other logfile. The only message, which is written to the shell which started the process, is xsltApplyOneTemplate: template was not compiled

My listeners connect to a publicly accessible Icecast server with the config below. Between broadcasts it uses a fallback mp3, which loops. During broadcasts it relays from a local Icecast server that I broadcast to (config also below). I am aiming for approx 30-45 seconds buffering, as the connection from public to local icecast server is 'less than ideal'. The set up is working fine

Hi, could you please help me with this situation, the operating system in my computer is Windows 10, and icecast cannot start properly here is my configuration: <icecast> <!-- location and admin are two arbitrary strings that are e.g. visible on the server info page of the icecast web interface (server_version.xsl). --> <location>Earth</location>

-----Originalmeddelande----- Fr?n: "Per Gunnarsson" <per at 80-244-81-186.customer.t3.se> Till: per.gunnarsson at lappstockholm.se Datum: 2012-02-19 17:45 ?mne: Icecast doesn't bind to my external network interface? I can listen to my stream with mplayer -cache 1024 http://localhost:8000/ices.mp3 but not mplayer -cache 1024 http://80.244.81.186:8000/ices.mp3 This

Hi, thanks in advance for any help that can be provided for this head-scratcher. I'm configuring a new server and can't get it to move listen clients to the fallback file when the source client disconnects. I probably have a misconfiguration in icecast.xml. Here is the <mount> section: <mount type="normal">

Hi Mark, Add extensions to all of your mountpoints for the appropriate audio codec/format you're using. For example, <mount-name>/test.opus</mount-name> for an Ogg/Opus stream. Don't forget to add extensions in the <fallback-mount> sections, too. I didn't look too closely at your config otherwise, that error was standing out. Cheers, Jordan P.S. Please

theprogpalace.com wrote: > Hi, > > My stream host upgraded me to 2.2 and since that time I am no longer > listed on the Icecast directory. I use SAM3 and it is setup correctly > on my end and my provider states all is set correctly there, but it > still does not work. Has anyone had this problem? > thanks, i have yp problems with 2.2-kh and 2.2.0 as well. i get the