[Icecast] Always question about live and playlist

LeBoUc Bob assadetptn.assadetptn at neuf.fr
Wed Jan 12 14:13:40 PST 2005

Hi everyone,

My first mail was: 
"I'm a french user of icecast2 on a distant serveur.
I have 1 stream running on the serveur (with ices) that play random mp3 and when i want to do a live i connect my PC (winamp+oddcastv3) to the icecast and then i have 2 stream on the icecast serveur. The question is "How can i replace the first stream (playlist) by my live stream, and when i've finished the live, the playlist hang on and the listeners don't see anything".

I want to do that because actually i have to move all the listeners manually from the first stream to the live. And when a new listener conect i have to move it to. It's not usefull"

Some people give me some help but i don't eally understand what i have to do. I juste understand that the options wich could interst me (to resolve my prob) is the fallback option but thats all....
This is my icecast.xml config file if you can help me...

        <!-- If enabled, this will provide a burst of data when a client 
             first connects, thereby significantly reducing the startup 
             time for listeners that do substantial buffering. However,
             it also significantly increases latency between the source
             client and listening client.  For low-latency setups, you
             might want to disable this. -->
        <!-- same as burst-on-connect, but this allows for being more
             specific on how much to burst. Most people won't need to
             change from the default 64k. Applies to all mountpoints  -->

        <!-- Sources log in with username 'source' -->
        <!-- Relays log in username 'relay' -->

        <!-- Admin logs in with the username given below -->

    <!-- Uncomment this if you want directory listings -->

    <!-- This is the hostname other people will use to connect to your server.
    It affects mainly the urls generated by Icecast for playlists and yp
    listings. -->

    <!-- You can use these two if you only want a single listener -->
    <!--<port>8000</port> -->

    <!-- You may have multiple <listener> elements -->
        <!-- <bind-address>fairartposse.net</bind-address> -->



    <!-- Only define a <mount> section if you want to use advanced options,
         like alternative usernames or passwords


        <authentication type="htpasswd">
                <option name="filename" value="myauth"/>
                <option name="allow_duplicate_users" value="0"/>


  <!-- basedir is only used if chroot is enabled -->

        <!-- Note that if <chroot> is turned on below, these paths must both
             be relative to the new root, not the original root -->

        <!-- Aliases: treat requests for 'source' path as being for 'dest' path
             May be made specific to a port or bound address using the "port"
             and "bind-address" attributes.
        <alias source="/foo" dest="/bar"/>
        <!-- Aliases: can also be used for simple redirections as well,
             this example will redirect all requests for http://server:port/ to
             the status page
        <alias source="/" dest="/kiviv"/>

       <loglevel>4</loglevel> <!-- 4 Debug, 3 Info, 2 Warn, 1 Error -->


THX a lot !!!!!!

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.xiph.org/pipermail/icecast/attachments/20050112/4324da46/attachment.html

More information about the Icecast mailing list