| View previous topic :: View next topic |
| Author |
Message |
JohnnyOh
Joined: 10 Feb 2009
Posts: 50
Location: Germany
|
 Posted: Mon Aug 31, 2009 1:34 pm Post subject: Latency for Distributing streams |
 |
|
Hi together,
I have a configuration request. I am using icecast 2.3.2 and my encoder is edcast (MP3-stream only)
everything works fine, but there is a problem of distribution-latency:
when my encoder is connected to the icecast server, the stream is available after about 7 minutes.
Please note that I am not connecting to the same server I am encoding to. I use the following structure:
Entry-server (source connects to this) -> relay-server -> Client-server (where I connect to hear the stream)
Is there any configuration-parameter, which handles this latency of about 7 minutes? what do I have to do, to reduce this latency?
I am looking forward to get your hints
Kind regards
Johnny |
|
| Back to top |
|
 |
karlH
Code Warrior
Joined: 13 Jun 2005
Posts: 5476
Location: UK
|
| Posted: Mon Aug 31, 2009 2:32 pm Post subject: |
|
|
It sounds like the relay server has a long retry time set.
<master-update-interval> is 2 mins by default, maybe it is set higher.
karl. |
|
| Back to top |
|
|
JohnnyOh
Joined: 10 Feb 2009
Posts: 50
Location: Germany
|
| Posted: Mon Aug 31, 2009 2:54 pm Post subject: |
|
|
Hi karlH,
thank you for your quick reply.
Unfortunately I do not use the master-slave configuration.
The Relay is configured manually with <relay></relay> |
|
| Back to top |
|
|
karlH
Code Warrior
Joined: 13 Jun 2005
Posts: 5476
Location: UK
|
| Posted: Mon Aug 31, 2009 4:27 pm Post subject: |
|
|
and yet the tag configures the retry setting for all relays.
karl. |
|
| Back to top |
|
|
JohnnyOh
Joined: 10 Feb 2009
Posts: 50
Location: Germany
|
| Posted: Mon Aug 31, 2009 4:40 pm Post subject: |
|
|
Thank you Karlh,
does it matter when the following parameter is commented out:
<!--
<master-server>ip-adress</master-server>
<master-server-port>80</master-server-port>
<master-update-interval>120</master-update-interval>
<master-password>hackme</master-password>
-->
is it an global parameter? i am relaying the streams like this:
<relay>
<server>source-ip</server>
<port>80</port>
<mount>/mountpoint.mp3</mount>
<local-mount>/mountpoint.mp3</local-mount>
<relay-shoutcast-metadata>1</relay-shoutcast-metadata>
</relay>
I am looking forward to hear from you. |
|
| Back to top |
|
|
karlH
Code Warrior
Joined: 13 Jun 2005
Posts: 5476
Location: UK
|
| Posted: Mon Aug 31, 2009 6:18 pm Post subject: |
|
|
no, should default to 120 seconds
karl. |
|
| Back to top |
|
|
JohnnyOh
Joined: 10 Feb 2009
Posts: 50
Location: Germany
|
| Posted: Tue Sep 01, 2009 8:46 am Post subject: |
|
|
I am sorry for my next request/misunderstanding.
Do I understand right, that the <master-update-interval>-parameter is activated, even when it is commented out? this would be weird.
in this case:
when I reduce the interval to 30 seconds, the stream should be available earlier?
If the parameter is not activated when it is commented out, where do I have to reduce the interval? |
|
| Back to top |
|
|
karlH
Code Warrior
Joined: 13 Jun 2005
Posts: 5476
Location: UK
|
| Posted: Tue Sep 01, 2009 1:52 pm Post subject: |
|
|
I think I just said the default is 120, unless you override it with the tag I mentioned. If you lower the value then the relay will be restarted more often. Whether the relay will start streaming is another matter and is typically why people need to get used to the idea of looking at log files.
karl. |
|
| Back to top |
|
|
JohnnyOh
Joined: 10 Feb 2009
Posts: 50
Location: Germany
|
| Posted: Tue Sep 01, 2009 2:41 pm Post subject: |
|
|
many thanks for your eefort and patience.
I do not understand, why I have to set the <master-update-interval>, even when I do not use a master-server (master-slave-infrastructure).
this is my icecast.xml:
| Code: |
<icecast>
<limits>
<clients>2000</clients>
<sources>200</sources>
<threadpool>250</threadpool>
<queue-size>524288</queue-size>
<client-timeout>30</client-timeout>
<header-timeout>15</header-timeout>
<source-timeout>10</source-timeout>
<!-- 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. -->
<burst-on-connect>1</burst-on-connect>
<!-- 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 -->
<burst-size>65535</burst-size>
</limits>
<authentication>
<!-- Sources log in with username 'source' -->
<source-password>hackme</source-password>
<!-- Relays log in username 'relay' -->
<relay-password>hackme</relay-password>
<!-- Admin logs in with the username given below -->
<admin-user>admin</admin-user>
<admin-password>hackme</admin-password>
</authentication>
<!-- Uncomment this if you want directory listings -->
<!--
<directory>
<yp-url-timeout>15</yp-url-timeout>
<yp-url>http://dir.xiph.org/cgi-bin/yp-cgi</yp-url>
</directory>
<directory>
<yp-url-timeout>15</yp-url-timeout>
<yp-url>http://www.oddsock.org/cgi-bin/yp-cgi</yp-url>
</directory>
-->
<!-- 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. -->
<hostname>localhost</hostname>
<!-- You can use these two if you only want a single listener -->
<!--<port>8000</port> -->
<!--<bind-address>127.0.0.1</bind-address>-->
<!-- You may have multiple <listener> elements -->
<listen-socket>
<port>80</port>
<!-- <bind-address>127.0.0.1</bind-address> -->
</listen-socket>
<!--
<listen-socket>
<port>8001</port>
</listen-socket>
-->
<!--<master-server>127.0.0.1</master-server>-->
<!--<master-server-port>8001</master-server-port>-->
<!--<master-update-interval>120</master-update-interval>-->
<!--<master-password>hackme</master-password>-->
<!-- setting this makes all relays on-demand unless overridden, this is
useful for master relays which do not have <relay> definitions here.
The default is 0 -->
<!--<relays-on-demand>1</relays-on-demand>-->
<relay>
<server>entry-IP</server>
<port>80</port>
<mount>/test.mp3</mount>
<local-mount>/test.mp3</local-mount>
<relay-shoutcast-metadata>1</relay-shoutcast-metadata>
</relay>
<!-- Only define a <mount> section if you want to use advanced options,
like alternative usernames or passwords
<mount>
<mount-name>/example-complex.ogg</mount-name>
<username>othersource</username>
<password>hackmemore</password>
<max-listeners>1</max-listeners>
<dump-file>/tmp/dump-example1.ogg</dump-file>
<burst-size>65536</burst-size>
<fallback-mount>/example2.ogg</fallback-mount>
<fallback-override>1</fallback-override>
<fallback-when-full>1</fallback-when-full>
<intro>/example_intro.ogg</intro>
<hidden>1</hidden>
<no-yp>1</no-yp>
<authentication type="htpasswd">
<option name="filename" value="myauth"/>
<option name="allow_duplicate_users" value="0"/>
</authentication>
<on-connect>/home/icecast/bin/stream-start</on-connect>
<on-disconnect>/home/icecast/bin/stream-stop</on-disconnect>
</mount>
<mount>
<mount-name>/auth_example.ogg</mount-name>
<authentication type="url">
<option name="mount_add" value="http://myauthserver.net/notify_mount.php"/>
<option name="mount_remove" value="http://myauthserver.net/notify_mount.php"/>
<option name="listener_add" value="http://myauthserver.net/notify_listener.php"/>
<option name="listener_remove" value="http://myauthserver.net/notify_listener.php"/>
</authentication>
</mount>
-->
<fileserve>1</fileserve>
<!-- set the mountpoint for a shoutcast source to use, the default if not
specified is /stream but you can change it here if an alternative is
wanted or an extension is required
<shoutcast-mount>/live.nsv</shoutcast-mount>
-->
<paths>
<!-- basedir is only used if chroot is enabled -->
<basedir>/usr/local/share/icecast</basedir>
<!-- Note that if <chroot> is turned on below, these paths must both
be relative to the new root, not the original root -->
<logdir>/var/log/icecast</logdir>
<webroot>/usr/local/share/icecast/web</webroot>
<adminroot>/usr/local/share/icecast/admin</adminroot>
<!-- <pidfile>/usr/local/share/icecast/icecast.pid</pidfile> -->
<!-- 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="/status.xsl"/>
</paths>
<logging>
<accesslog>icecast2new.log</accesslog>
<errorlog>error.log</errorlog>
<!-- <playlistlog>playlist.log</playlistlog> -->
<loglevel>2</loglevel> <!-- 4 Debug, 3 Info, 2 Warn, 1 Error -->
<aggregation>1</aggregation> <!-- 0 NO_AGGREGATION, 1 DAILY, 2 MONTHLY -->
<logsize>10000</logsize>
<logarchive>1</logarchive>
</logging>
<security>
<chroot>0</chroot>
<changeowner>
<user>icecast</user>
<group>icecast</group>
</changeowner>
</security>
</icecast>
|
may be this could help you, to solve my misunderstanding.
Many thanks for your effort.
Best regards
Johnny |
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
