From kosnickx at gmail.com Fri Sep 5 20:40:39 2008
From: kosnickx at gmail.com (kosnickx)
Date: Fri, 05 Sep 2008 23:40:39 +0300
Subject: [Icecast] schedule a fallback and / 2 sources streaming at 1 server
???
Message-ID: <48C19947.40908@gmail.com>
Hi everyone.
I was wondering if it is possible to schedule a fallback. I know there
is the option when no source is streaming then icecast server falls back
to another mount point. So my question is if it is possible to schedule
some sort of fallback to another mount point whenever i want to. Let me
give you an example:
source 1 is streaming to server from 16:00 until 16:59 at mount point 1.
At 16:59 server falls back (by schedule) to mount point 2 (which
includes some jingles ads and so on) until 17:02 when a new source
(source 2) takes over control and streams again at mount point 1.
Is this possible?
Another question. I saw some option about the number of sources that can
connect to the same server simultanously. What happens when source 2
connects to the server that source 1 is streaming already and source 2
starts its own stream? Are they both streaming? Source 1 is kicked off
or does it keep control over the server?
These questions have to do with the fact that i am thinking of having a
server and many sources in different places streaming to this server.
The thing is how to keep all the sources synchronized.
Thanx in advance
From dtrump1 at triadav.com Fri Sep 5 22:47:50 2008
From: dtrump1 at triadav.com (Dick Trump)
Date: Fri, 5 Sep 2008 17:47:50 -0500
Subject: [Icecast] schedule a fallback and / 2 sources streaming at 1
server ???
In-Reply-To: <48C19947.40908@gmail.com>
References: <48C19947.40908@gmail.com>
Message-ID: <3210104919.20080905174750@triadav.com>
kosnickx wrote:
> So my question is if it is possible to schedule
> some sort of fallback to another mount point whenever i want to
Yes. I have a Windows installation where my live stream comes from Simplecast with multiple mount points with the same data.
At certain points in the day, I need to insert alternate material to an individual mount point instead of the main stream provided by Simplecast. I wrote a separate scheduling application that launches EZstream for the one hour inserts. All other mount points continue to receive the main program.
--
Regards
Dick Trump
From kosnickx at gmail.com Sat Sep 6 07:59:17 2008
From: kosnickx at gmail.com (kosnickx)
Date: Sat, 06 Sep 2008 10:59:17 +0300
Subject: [Icecast] schedule a fallback and / 2 sources streaming at 1
server ???
In-Reply-To: <3210104919.20080905174750@triadav.com>
References: <48C19947.40908@gmail.com> <3210104919.20080905174750@triadav.com>
Message-ID: <48C23855.3090503@gmail.com>
Dick Trump wrote:
> kosnickx wrote:
>
>> So my question is if it is possible to schedule
>> some sort of fallback to another mount point whenever i want to
>>
>
> Yes. I have a Windows installation where my live stream comes from Simplecast with multiple mount points with the same data.
>
> At certain points in the day, I need to insert alternate material to an individual mount point instead of the main stream provided by Simplecast. I wrote a separate scheduling application that launches EZstream for the one hour inserts. All other mount points continue to receive the main program.
>
>
First of all thanks for your answer.
Now let's see if i got it right.
You have lets say 5 mount points, all of them playing the same stream
(from the same client - Simplecast).
Every hour you use one of these mount points (lets say #3) to insert
alternate stream.
So with your own application (kind of scheduler i guess) you connect a
new client (that is EZstream) to mount point 3 (i suppose only for a few
moments - some ads and jingles maybe).
So EZstream provides mount point 3 with new stream right?
What happens to Simplecast (it was streaming to mount point 3 too - now
both Simplecast and EZstream stream to mount point 3)?
What happens when EZstream stops streaming to mount point 3 (while, i
guess, Simplecast kept streaming to mount point 3)?
Once again thanks.
From dtrump1 at triadav.com Sat Sep 6 15:38:07 2008
From: dtrump1 at triadav.com (Dick Trump)
Date: Sat, 6 Sep 2008 10:38:07 -0500
Subject: [Icecast] schedule a fallback and / 2 sources streaming at 1
server ???
In-Reply-To: <48C23855.3090503@gmail.com>
References: <48C19947.40908@gmail.com> <3210104919.20080905174750@triadav.com>
<48C23855.3090503@gmail.com>
Message-ID: <1681809874.20080906103807@triadav.com>
kosnickx wrote:
> Now let's see if i got it right.
Mostly right.
> You have lets say 5 mount points, all of them playing the same stream
> (from the same client - Simplecast).
Yes
> Every hour you use one of these mount points (lets say #3) to insert
> alternate stream.
> So with your own application (kind of scheduler i guess) you connect a
> new client (that is EZstream) to mount point 3 (i suppose only for a few
> moments - some ads and jingles maybe).
No. The inserts are usually an hour long and for a given mount, only occur once or twice a day. This is a state-wide radio network for the blind, serving multiple communities. These inserts are pertinent to the local community, not the rest of the stations in the network.
> So EZstream provides mount point 3 with new stream right?
Yes
> What happens to Simplecast (it was streaming to mount point 3 too - now
> both Simplecast and EZstream stream to mount point 3)?
Simplecast continues to encode to all mount points but is temporarily disconnected from mount point 3 (in your example).
> What happens when EZstream stops streaming to mount point 3 (while, i
> guess, Simplecast kept streaming to mount point 3)?
When EZstream is forced to stop by the application (necessary since by default, it would just loop), Icecast reconnects to the primary source from Simplecast.
Here's where my application is somewhat backward from what the normal intent of fallbacks would be. Instead of the Simplecast mount point being the primary one, it is configured as the fallback-mount. The insert (temporary) mount point is the primary mount for that destination. So the configuration for destination 3 would look something like this:
/MOUNTNUM3-INSERT
3
/MOUNTNUM3
1
The INSERT mount is sourced by EZstream and the fallback-mount is sourced by Simplecast.
Of course, the max-listeners tag of 3 has nothing to do with the MOUNTNUM3 but rather allows me to connect for monitoring purposes only.
Since all of this happens on a single machine, I can only handle one insert at a time (one instance of EZstream). If I ever need to schedule two inserts simultaneously, I'll need to use a 2nd machine to handle that.
Incidentally, this same machine also runs another program on schedule that captures segments of the stream that are live, archives them and FTP's them to our web server for on-demand streaming. Not too bad for an old P3 machine donated when it was "obsolete".
--
Dick
dtrump1 at triadav.com
From kosnickx at gmail.com Sat Sep 6 17:39:21 2008
From: kosnickx at gmail.com (kosnickx)
Date: Sat, 06 Sep 2008 20:39:21 +0300
Subject: [Icecast] schedule a fallback and / 2 sources streaming at 1
server ???
In-Reply-To: <1681809874.20080906103807@triadav.com>
References: <48C19947.40908@gmail.com>
<3210104919.20080905174750@triadav.com> <48C23855.3090503@gmail.com>
<1681809874.20080906103807@triadav.com>
Message-ID: <48C2C049.90302@gmail.com>
Dick Trump wrote:
> kosnickx wrote:
>
>> Now let's see if i got it right.
>>
>
> Mostly right.
>
>
>> You have lets say 5 mount points, all of them playing the same stream
>> (from the same client - Simplecast).
>>
>
> Yes
>
>
>> Every hour you use one of these mount points (lets say #3) to insert
>> alternate stream.
>> So with your own application (kind of scheduler i guess) you connect a
>> new client (that is EZstream) to mount point 3 (i suppose only for a few
>> moments - some ads and jingles maybe).
>>
>
> No. The inserts are usually an hour long and for a given mount, only occur once or twice a day. This is a state-wide radio network for the blind, serving multiple communities. These inserts are pertinent to the local community, not the rest of the stations in the network.
>
>
>> So EZstream provides mount point 3 with new stream right?
>>
>
> Yes
>
>
>> What happens to Simplecast (it was streaming to mount point 3 too - now
>> both Simplecast and EZstream stream to mount point 3)?
>>
>
> Simplecast continues to encode to all mount points but is temporarily disconnected from mount point 3 (in your example).
>
>
>> What happens when EZstream stops streaming to mount point 3 (while, i
>> guess, Simplecast kept streaming to mount point 3)?
>>
>
> When EZstream is forced to stop by the application (necessary since by default, it would just loop), Icecast reconnects to the primary source from Simplecast.
>
> Here's where my application is somewhat backward from what the normal intent of fallbacks would be. Instead of the Simplecast mount point being the primary one, it is configured as the fallback-mount. The insert (temporary) mount point is the primary mount for that destination. So the configuration for destination 3 would look something like this:
>
>
> /MOUNTNUM3-INSERT
> 3
> /MOUNTNUM3
> 1
>
>
> The INSERT mount is sourced by EZstream and the fallback-mount is sourced by Simplecast.
>
> Of course, the max-listeners tag of 3 has nothing to do with the MOUNTNUM3 but rather allows me to connect for monitoring purposes only.
>
> Since all of this happens on a single machine, I can only handle one insert at a time (one instance of EZstream). If I ever need to schedule two inserts simultaneously, I'll need to use a 2nd machine to handle that.
>
> Incidentally, this same machine also runs another program on schedule that captures segments of the stream that are live, archives them and FTP's them to our web server for on-demand streaming. Not too bad for an old P3 machine donated when it was "obsolete".
>
>
Thanks a lot!
From dtrump1 at triadav.com Sat Sep 6 22:30:28 2008
From: dtrump1 at triadav.com (Dick Trump)
Date: Sat, 6 Sep 2008 17:30:28 -0500
Subject: [Icecast] schedule a fallback and / 2 sources streaming at 1
server ???
In-Reply-To: <48C2CA6C.2060903@gmail.com>
References: <48C19947.40908@gmail.com> <3210104919.20080905174750@triadav.com>
<48C23855.3090503@gmail.com>
<1681809874.20080906103807@triadav.com>
<48C2CA6C.2060903@gmail.com>
Message-ID: <19010602866.20080906173028@triadav.com>
kosnickx wrote:
> Well i just tried what you said and it works fine.
> But there is one thing : while falling back from one mount point to
> another it takes about 10 to 15 seconds. Does this happen to you too? Is
> there any way to reduce this to minimum or to 0 if possible.
> Sorry for being so anoying.
Not annoying at all. I'm happy to be able to add some of my own experience to how useful Icecast can be.
I suspect the gap may vary with the connected client (listener). Since there is an interruption in the stream, the receiving software must resync. All my "receivers" are running mpg123 on Linux with a custom script that is constantly looking at the received stream status. If there is any interruption, it will immediately kill mpg123 and restart it making the interruption as brief as possible. Since these receivers are all remotely located, I don't hear them but I have never heard a complaint about it.
--
Dick
dtrump1 at triadav.com
From david.baelde at gmail.com Sun Sep 7 11:20:57 2008
From: david.baelde at gmail.com (David Baelde)
Date: Sun, 7 Sep 2008 13:20:57 +0200
Subject: [Icecast] schedule a fallback and / 2 sources streaming at 1
server ???
In-Reply-To: <19010602866.20080906173028@triadav.com>
References: <48C19947.40908@gmail.com> <3210104919.20080905174750@triadav.com>
<48C23855.3090503@gmail.com>
<1681809874.20080906103807@triadav.com>
<48C2CA6C.2060903@gmail.com> <19010602866.20080906173028@triadav.com>
Message-ID: <53c655920809070420s464ad352v73d72c2df52afdfa@mail.gmail.com>
Hi,
On Sun, Sep 7, 2008 at 12:30 AM, Dick Trump wrote:
> kosnickx wrote:
>> But there is one thing : while falling back from one mount point to
>> another it takes about 10 to 15 seconds. Does this happen to you too? Is
>> there any way to reduce this to minimum or to 0 if possible.
I've been wanting to advise you to give liquidsoap a try since the
beginning of this thread. Now I'm decided.
As long as you're happy with icecast-level fallbacks, it's cool, since
it does not put any constraint on your source clients. Maybe you're
tied to particular source clients for functionalities or availability
on Windows. But that solution has some limitations as you noticed: the
listeners can hear it, and the transition is not very smooth. If you
want to do better, you need to use a tool for that.
Liquidsoap [1] is a solution: it's a source client that can relay
other source clients, and manage a fallback between them, possibly
with transitions. Then liquidsoap creates the stream and sends it to
icecast, it's seamless for the listener. And in case you don't _need_
to have two separate source clients, let me precise that the fallback,
like any other operation in liquidsoap, works as well with source
clients than with internal sources such as playlists.
Feel free to ask on savonet-users at lists.sf.net if you have any questions.
Cheers,
--
David
[1] http://savonet.sf.net
From DXDragon at yandex.ru Sun Sep 7 12:20:14 2008
From: DXDragon at yandex.ru (=?utf-8?B?0KDQvtC80LDQvSDQlNC+0L3Rh9C10L3QutC+?=)
Date: Sun, 7 Sep 2008 16:20:14 +0400
Subject: [Icecast] ezstream build failure and AC_LIB_PREPARE_PREFIX
References: <19A6BE950816429A820E35C7C163158B@Tortoise>
Message-ID:
I posted a follow-up, but it was delayed due to being overlong. Summary:
dumping lib-link.m4, lib-ld.m4 and lib-prefix.m4 from Gnulib into
ezstream/m4/ eliminates the errors.
Roman.
From kosnickx at gmail.com Sun Sep 7 17:21:48 2008
From: kosnickx at gmail.com (kosnickx)
Date: Sun, 07 Sep 2008 20:21:48 +0300
Subject: [Icecast] schedule a fallback and / 2 sources streaming at 1
server ???
In-Reply-To: <53c655920809070420s464ad352v73d72c2df52afdfa@mail.gmail.com>
References: <48C19947.40908@gmail.com>
<3210104919.20080905174750@triadav.com> <48C23855.3090503@gmail.com> <1681809874.20080906103807@triadav.com> <48C2CA6C.2060903@gmail.com>
<19010602866.20080906173028@triadav.com>
<53c655920809070420s464ad352v73d72c2df52afdfa@mail.gmail.com>
Message-ID: <48C40DAC.7020209@gmail.com>
David Baelde wrote:
> Hi,
>
> On Sun, Sep 7, 2008 at 12:30 AM, Dick Trump wrote:
>
>> kosnickx wrote:
>>
>>> But there is one thing : while falling back from one mount point to
>>> another it takes about 10 to 15 seconds. Does this happen to you too? Is
>>> there any way to reduce this to minimum or to 0 if possible.
>>>
>
> I've been wanting to advise you to give liquidsoap a try since the
> beginning of this thread. Now I'm decided.
>
> As long as you're happy with icecast-level fallbacks, it's cool, since
> it does not put any constraint on your source clients. Maybe you're
> tied to particular source clients for functionalities or availability
> on Windows. But that solution has some limitations as you noticed: the
> listeners can hear it, and the transition is not very smooth. If you
> want to do better, you need to use a tool for that.
>
> Liquidsoap [1] is a solution: it's a source client that can relay
> other source clients, and manage a fallback between them, possibly
> with transitions. Then liquidsoap creates the stream and sends it to
> icecast, it's seamless for the listener. And in case you don't _need_
> to have two separate source clients, let me precise that the fallback,
> like any other operation in liquidsoap, works as well with source
> clients than with internal sources such as playlists.
>
> Feel free to ask on savonet-users at lists.sf.net if you have any questions.
>
> Cheers,
> --
> David
>
> [1] http://savonet.sf.net
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
>
>
Well Peter Brooks mentioned this earlier in the thread but it seemed
tricky to me. After you mentioned it (again) i took a closer look at it,
i tried it a bit and i liked it but though I haven't found the time to
look carefully at it.
Anyway thx for mentioning (both)
From andre_grundmann at gmx.de Mon Sep 8 11:06:16 2008
From: andre_grundmann at gmx.de (andre_grundmann at gmx.de)
Date: Mon, 08 Sep 2008 13:06:16 +0200
Subject: [Icecast] Running ices on startup
Message-ID: <20080908110616.309380@gmx.net>
Hi everyone.
I'm running icecast and ices2 on OpenSuse 10.2 (could upgrade to 11.0 in a breeze though).
What I'm trying to achieve right now is to use this for a kind of "baby-phone" functionality.
That means:
1. There is a microphone attached to the server which records sound in the room
2. I'm in another room, listening to the server on Winamp, so I can hear what goes on in the room with the server
This works more or less fine, with one catch: icecast starts when I start the server, but ices doesn't. I have to start ices manually. This is unpleasant at least, so I would like to start ices on server startup. I already tried entering icecast into the runlevel manager and wrote a script to start it. What happens, is this:
Ices starts, if I run the script manually through the runlevel manager (runlevel manager reports success, and I hear sound), but after a bootup, no sound, although the runlevel manager still tells me ices is running. I can then still start ices manually, either using the script or running "ices /etc/ices.xml".
I had a similar setup with icecast and, I believe, oddsock on a Windows machine, and there I had the problem that icecast and the stream source would start concurrently, and the stream source couldn't find icecast, because it wasn't fully loaded yet.
According to yast, icecast loads in runlevels 3 and 5, and ices loads in runlevel 5.
For good measure, the startup script:
#!/bin/bash
RETVAL=0
ICES2_BIN=/usr/bin/ices
test -x $ICES2_BIN || { echo "$ICES2_BIN not installed";
if [ "$1" = "stop" ]; then exit 0;
else exit 5; fi; }
# What you want to do when you start the script
start() {
# put your commands here
RETVAL=0
}
# What you want to do when you stop the script
stop() {
# put your commands here
RETVAL=0
}
case $1 in
start)
echo -n "Starting ices2 "
## Start daemon with startproc(8). If this fails
## the return value is set appropriately by startproc.
/sbin/startproc $ICES2_BIN /home/mitarbeiter/icecast/ices.xml
# Remember status and be verbose
#rc_status -v
;;
stop)
echo -n "Shutting down ices2 "
## Stop daemon with killproc(8) and if this fails
## killproc sets the return value according to LSB.
/sbin/killproc -TERM $ICES2_BIN
# Remember status and be verbose
#rc_status -v
;;
restart)
stop
start
;;
status)
# put here what you want to display on status command
RETVAL=0
;;
*)
echo "Usage: name of script {start|stop|restart|status}"
RETVAL=1
esac
Essentially a modified icecast startup script.
Hope you folks can help me out.
CU,
Andre
--
GMX Kostenlose Spiele: Einfach online spielen und Spa? haben mit Pastry Passion!
http://games.entertainment.gmx.net/de/entertainment/games/free/puzzle/6169196
From dm8tbr at afthd.tu-darmstadt.de Mon Sep 8 19:39:37 2008
From: dm8tbr at afthd.tu-darmstadt.de (Thomas B. Ruecker)
Date: Mon, 08 Sep 2008 22:39:37 +0300
Subject: [Icecast] Running ices on startup
In-Reply-To: <20080908110616.309380@gmx.net>
References: <20080908110616.309380@gmx.net>
Message-ID: <48C57F79.9000208@afthd.tu-darmstadt.de>
andre_grundmann at gmx.de schrieb:
> Hi everyone.
>
> I'm running icecast and ices2 on OpenSuse 10.2 (could upgrade to 11.0 in a breeze though).
> What I'm trying to achieve right now is to use this for a kind of "baby-phone" functionality.
> That means:
> 1. There is a microphone attached to the server which records sound in the room
> 2. I'm in another room, listening to the server on Winamp, so I can hear what goes on in the room with the server
>
> This works more or less fine, with one catch: icecast starts when I start the server, but ices doesn't. I have to start ices manually. This is unpleasant at least, so I would like to start ices on server startup. I already tried entering icecast into the runlevel manager and wrote a script to start it. What happens, is this:
> Ices starts, if I run the script manually through the runlevel manager (runlevel manager reports success, and I hear sound), but after a bootup, no sound, although the runlevel manager still tells me ices is running. I can then still start ices manually, either using the script or running "ices /etc/ices.xml".
>
Did you check if ices is actually running?
What does the ices log say?
If not enough set it to debug level logging.
Does it start _after_ icecast? check in the rc.5 directory if everything
else fails to tell you that.
For the init related part I recommend reading the suse documentation. If
in doubt which part of it ask the opensuse people for hints.
Cheers
Thomas
From dm8tbr at afthd.tu-darmstadt.de Sun Sep 14 10:21:03 2008
From: dm8tbr at afthd.tu-darmstadt.de (Thomas B. Ruecker)
Date: Sun, 14 Sep 2008 13:21:03 +0300
Subject: [Icecast] Icecast + theora stream + Firefox 3.1a2 = promising
Message-ID: <48CCE58F.1020605@afthd.tu-darmstadt.de>
Hi folks,
just wanted to let you in on my research into use of theora streams in