[Icecast] Mount with Relay: Fallback-override does not work

ak18 at 5x9.de ak18 at 5x9.de
Fri Aug 3 16:38:02 UTC 2018


Hello,

I'm using Icecast over 10 years, so let me first say *Thank you to all 
developers* of Icecast!

I have a problem using a mount with relay and a fallback. The option 
<fallback-override> is not working.

I tested two different configurations:

_Configuration A:_

     <mount>
         <mount-name>/Stream-096k.mp3</mount-name>
         <max-listeners>2000</max-listeners>
         <burst-size>122880</burst-size>
<fallback-mount>/Recordings/Record1.mp3</fallback-mount>
         <fallback-override>1</fallback-override>
     </mount>
     <relay>
         <server>xxx.xxx.xxx.xxx</server>
         <port>8080</port>
         <mount>/Masterstream-096k.mp3</mount>
         <local-mount>/Stream-096k.mp3</local-mount>
         <on-demand>1</on-demand>
        <fallback-override>1</fallback-override>
     </relay>

_Configuration B:_

     <mount>
         <mount-name>/Stream-096k.mp3</mount-name>
         <max-listeners>2000</max-listeners>
         <burst-size>122880</burst-size>
<fallback-mount>/Stream-Recorded.mp3</fallback-mount>
         <fallback-override>1</fallback-override>
     </mount>
     <relay>
         <server>xxx.xxx.xxx.xxx</server>
         <port>8080</port>
         <mount>/Masterstream-096k.mp3</mount>
         <local-mount>/Stream-096k.mp3</local-mount>
         <on-demand>1</on-demand>
        <fallback-override>1</fallback-override>
     </relay>

     <mount>
         <mount-name>/Stream-Recorded.mp3</mount-name>
         <max-listeners>2000</max-listeners>
         <burst-size>61440</burst-size>
<fallback-mount>/Recordings/Record1.mp3</fallback-mount>
         <fallback-override>1</fallback-override>
         <limit-rate>49152</limit-rate>
     </mount>

Problem 1:
In both configurations the fallback is played if the relay is offline. 
But if the stream of the relay is going to online, the listeners are not 
switched back from the fallback. Even if I wait hours, that does not happen.
Currently I still use the older icecast-version 2.3.1 - so pherhals this 
could be the reason...

Problem 2:
I also found that <limit-rate> (I did not find this option in the 
dokumentation, why?) does not have any effect, no matter what value I 
used. Maybe it's because of the older version? (I used limit-rate 
because the recording is 48k instead of 96k).

Kind regards.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20180803/8f7a4010/attachment.htm>


More information about the Icecast mailing list