<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Thanks for all of the replies, glad there is interest. Here come some
replies to some stuff:<br>
<br>
John R. Dennison wrote:<br>
<blockquote cite="mid:20100312214724.GG6989@frodo.gerdesas.com"
type="cite">
<pre wrap="">
Rich,
Have you investigated bandwidth utilization requirements
for this? Assuming full 16 slots of players and lets
say 4 observer slots, with a lot of chatter.
</pre>
</blockquote>
Here's what the Mumble FAQ has to say on that:<br>
<h2><span class="mw-headline">What are the bandwidth requirements? </span></h2>
<p>From 0.9.1, this is highly variable, and mostly up to the user. With
top quality, minimum latency and positional information sent, it is
133.6 kbit/s including the IP and UDP overhead. With 60 ms transmission
delay, the lowest quality speech and no positional information, it is
17.4 kbit/s (again with IP and UDP overhead). The default quality
setting uses 58.8 kbit/s. When comparing with other products, remember
to compare the total bandwidth use and not just the bitrate of the
audio encoding. </p>
<p>There are two parts to tuning the bandwidth; the audio bitrate per
audio frame (e.g. 10ms) and the amount of frames to put in each packet.
Each transmitted packet has a overhead of 28 bytes from IP and UDP
alone, so at the highest transmission rate (100 packets per second),
that is 2800 bytes of data for raw network overhead alone. You should
try to find a balance that works well for you, but we generally
recommend sacrificing high audio bitrate for lower latency; Mumble
sounds quite good even on the lowest quality setting. </p>
<p>There is no way to adjust the amount of incoming bandwidth; you will
have to have enough to sustain the total amount of speaking players.
This should be a minor issue; most players these days are on asymmetric
lines and hence it is only upload that is a bottleneck.<br>
</p>
<h2><span class="mw-headline">What sort of bandwidth will I need for
the server? </span></h2>
<p>Worst case scenario: Number of users × Number of talking users ×
133,6 kbit/s. With less aggressive quality settings, it's ~60 kbit/s,
and the bare minimum is 17.4kbit/s. Note that Mumble is geared towards
social gaming; its quality enables people to talk naturally to each
other instead of just barking short commands, so the amount of "users
talking at the same time" can be somewhat higher than expected. </p>
<p>This means that a server with 20 players and 2 players talking at
once requires 1-3 Mbit/s, depending on quality settings. In the
server's .ini file, you can specify the maximum allowed bitrate for
users as well as the maximum number of clients to allow.<br>
</p>
<p>From <a class="moz-txt-link-freetext" href="http://mumble.sourceforge.net/FAQ">http://mumble.sourceforge.net/FAQ</a><br>
</p>
<p>Rich<br>
</p>
</body>
</html>