similar to: fallback to static mp3 file?

Karl, It would certainly be a useful feature for me and I guess others. The current solution with ezstream works but listeners all end up at the same (current) point in the mp3 file. With the mp3 file as a fallback each individual listener would want to start hearing it from the start. This might be more difficult to implement with the single-q that is in the current trunk code, I don't know.

Hi Geoff, Thanks, that sounds like a good idea. I've just tried it and of course it works. Then I discovered that when the original source is not connected icecast doesn't fall through to the fallback mount. Is this a known problem? KJ > > Van: Geoff Shang <gshang@pacific.net.au> > Aan: Klaas Jan Wierenga <k.j.wierenga@home.nl> > CC: icecast@xiph.org > Datum:

On Tue, 2004-09-07 at 17:54, Klaas Jan Wierenga wrote: > Karl, > > It would certainly be a useful feature for me and I guess others. The > current solution with ezstream works but listeners all end up at the > same (current) point in the mp3 file. With the mp3 file as a fallback > each individual listener would want to start hearing it from the > start. This might be more

Do you mean you can relay within a single icecast server instance? So the relay is running on the same icecast process from which it is relaying a stream? KJ -----Oorspronkelijk bericht----- Van: Karl Heyes [mailto:karl@xiph.org] Verzonden: maandag 15 november 2004 22:18 Aan: Klaas Jan Wierenga CC: icecast Onderwerp: Re: FW: [Icecast] Multi-Level Fallbacks On Mon, 2004-11-15 at 20:36, Klaas

Hi Karl, I've not been able to duplicate it (yet). Assuming that brendan's snapshot is a daily build from icecast/trunk I've compared icecast_2_3_1 and trunk code for src/source.c. The most likely change that fixes the problem is the introduction of avl_tree_rlock (and matching unlock) just below "Applying mount information for". Another lock that might be related is

I'm using ezstream-0.1.2 KJ -----Oorspronkelijk bericht----- Van: Joel Ebel [mailto:jbebel@ncsu.edu] Verzonden: donderdag 3 februari 2005 21:05 Aan: Klaas Jan Wierenga Onderwerp: Re: [Icecast] Stream drops during handoff. Suggestions? Thanks. I'll have to try that. I wonder why ezstream would ever stop sending data for that long though. What version of ezstream are you running? Joel

Karl, I've managed to patch up my branch of Icecast to do the batching. Checked everything with valgrind and tested it extensively. It looks good. Tcpdump now shows nice size frames (mostly 1400 bytes). Any reason why you're not settings the MTU to something closer to 1500? Many thanks for your help, KJ -----Oorspronkelijk bericht----- Van: Karl Heyes [mailto:karl@xiph.org] Verzonden:

Again, forwarding to the list. Please try to reply to the list. Cheers, KJ -----Oorspronkelijk bericht----- Van: Iceuse - Kris [mailto:iceuse@wwlang.net] Verzonden: woensdag 15 september 2004 7:17 Aan: k.j.wierenga@home.nl Onderwerp: Re: [Icecast] SOURCE access logging in 2.1-trunk breaks webalizer (streaming version) Thanks, I'm very confused by this kind of lists where the answer goes to

Hi Karl, Thanks for your info. I have a standard Icecast-2.2 release with a few local patches. I'm a little apprehesive to apply my patches to the kh14 branch, so I'd rather patch my branch with the changes related to batched reads from the kh branch. I've looked at your code to see if I could spot the changes related to batching reads. So far I have not been able to find where

Posting it on the mailing list for you Chris :-) KJ -----Oorspronkelijk bericht----- Van: Iceuse - Kris [mailto:iceuse@wwlang.net] Verzonden: dinsdag 14 september 2004 16:49 Aan: Klaas Jan Wierenga Onderwerp: Re: [Icecast] SOURCE access logging in 2.1-trunk breaks webalizer (streaming version) Hello, Yes, that's something which is making trouble with webalizer stats... when I made this

'The work' are you referring to http://svn.xiph.org/icecast/branches/kh ? Most important is that I shouldn't have to edit the icecast configuration file when a new mountpoint needs to be added. Therefor all authentication of source and listener should go through the URL's. KJ Karl Heyes schreef: > Klaas Jan Wierenga wrote: >> >> In my case that's not needed,

In my case that's not needed, but yes it would be really nice if all mount options could be retrieved from the database using an authenticated URL. KJ Stefan de Konink wrote: > On Fri, 8 Sep 2006, Klaas Jan Wierenga wrote: > > >> I guess if the <authentication type="url> section could be used as a >> top-level tag (instead of as a sub-tag of

Yes that is the plan. I'll have to find some time to graft the patch onto 2.1 mainline and post it here. KJ -----Oorspronkelijk bericht----- Van: Myke Place [mailto:mp@trans.xmission.com]Namens Myke Place Verzonden: donderdag 18 november 2004 22:14 Aan: Klaas Jan Wierenga Onderwerp: Re: [Icecast] Dumping streams to a file? Is the plan to eventually move this from -trunk to the mainline

Please post to the mailing list the next time Ralf. I'm not using yp directory listings, but I can guess why it is not working. You're probably missing the libcurl.so library in your chroot jail directories. Here's the listing of files I have in the chroot jail: -----%< cut here > ls -R .: admin etc lib opt usr var web ./admin: listclients.xsl listmounts.xsl

Klaas Jan Wierenga wrote: > Hi Henri and others, > > Very interesting post about TCP_CORK. I would be very interested in having > it applied in the next version of Icecast. I'd be more interested in some figures to show there being a benefit, most examples talk about HTTP servers with short lived connections where sendfile(2) is used. > For low-bitrate streams the problem

Klaas Jan Wierenga wrote: >>This is exactly why it was implemented, a few people complained about >>the overhead with large numbers of listeners, not only because of the >>TCP overhead but also the fact that it reduces the write syscall >>overhead. Will TCP_CORK (linux) and TCP_NOPUSH (BSD) give noticable >>benefits wrt icecast? It might prove helpful if available but

Care to shed some light on this? I have about 10 IPs that are at my disposal and 3 I've been keeping for spares and whatnot. Though binding them is a little beyond me. TIA Justin On 6/22/05, Klaas Jan Wierenga <k.j.wierenga@home.nl> wrote: > > Hi, > > You can if your machine is assigned two IP addresses. Then you can bind the > webserver to port 80 on the first

I'm curious about why you would want to run Icecast on port 80. Geoff Justin Bot wrote: >Care to shed some light on this? I have about 10 IPs that are at my >disposal and 3 I've been keeping for spares and whatnot. Though >binding them is a little beyond me. > >TIA > >Justin > >On 6/22/05, Klaas Jan Wierenga <k.j.wierenga@home.nl> wrote: > >

On Mon, 2004-11-15 at 20:36, Klaas Jan Wierenga wrote: > Hi, > > I have used the SVN icecast-2.1-trunk version in my production system at > http://audioserver.nl for 2 months now without problems. The fallbacks work > fine as long as you make sure that the format (sampling frequency and > bitrate) of the mount and it's fallback match. samplerate and channels are the main

I have a patch on icecast-2.2.0 svn version which was written specifically to support SimpleCast users to retrieve the stats for their mountpoint and only that mountpoint. This is based on per mount-point username password. Using HTTP authentication the client can retrieve only http://hostname/admin/stats.xml given the correct username/password. This will only return the stats for that