https://wiki.mumble.info/api.php?action=feedcontributions&user=Arrai&feedformat=atomMumble Wiki - User contributions [en]2024-03-19T13:06:14ZUser contributionsMediaWiki 1.31.0https://wiki.mumble.info/index.php?title=BuildingLinux&diff=2857BuildingLinux2009-03-02T15:33:46Z<p>Arrai: replaced svn by git</p>
<hr />
<div>This guide is based (but not only) on this article [http://www.linux-gamers.net/modules/newbb/viewtopic.php?topic_id=2896&forum=6] found at www.linux-gamers.net.<br />
<br />
== Install the dependencies ==<br />
<br />
For Mumble/Murmur 1.1.0 and greater (including SVN), Qt 4.3 is required.<br />
<br />
=== For Debian / Ubuntu ===<br />
The following command makes sure you have the needed libraries and dependencies installed to build Mumble and Murmur from source!<br />
<br />
apt-get install qt4-dev-tools libqt4-dev libspeex1 libspeex-dev libboost-dev libasound2-dev libxevie-dev libxevie1 libssl-dev g++ libspeechd-dev libzeroc-ice-dev libpulse-dev slice2cpp libcap-dev<br />
<br />
It's recommended to remove the package qt3-dev-tools if installed.<br />
<br />
You can also install the libg15-dev libraries for Logitech G15 Keyboard serie.<br />
<br />
Now go on to the section [[#Installing_from_source]].<br />
<br />
== Installing from source ==<br />
<br />
The most generic approach to install mumble under any Linux is to install from source.<br />
Either get the current mumble source over git or get the latest tarball release from sourceforge.net.<br />
<br />
=== GIT ===<br />
For compiling from git make sure you've installed git-core (includes git-clone)<br />
<br />
apt-get install git-core<br />
<br />
git-clone git://mumble.git.sourceforge.net/gitroot/mumble mumble<br />
cd mumble/<br />
git-clone http://git.xiph.org/speex.git/ speex<br />
<br />
=== tarball release ===<br />
Download the latest tarball release from sf.net http://sourceforge.net/project/showfiles.php?group_id=147372 and extract it:<br />
<br />
tar xzfv mumble-x.x.x.tar.gz # (whereas the X are the version numbers of mumble)<br />
cd mumble-x.x.x<br />
<br />
=== Compile Mumble and Murmur ===<br />
For more configuration options on the qmake command read the supplied INSTALL file.<br />
<br />
Be sure to have the pre-requisites installed and in place for your linux distribution (see the sections above) before you begin compiling it.<br />
<br />
qmake main.pro<br />
make<br />
<br />
If you want to compile Murmur (Mumble server) only, then type<br />
<br />
qmake main.pro CONFIG+=no-client<br />
make<br />
<br />
Note: If you are using Debian/Ubuntu with both Qt3 and Qt4 installed use the command "qmake-qt4" instead of "qmake"<br />
<br />
==Text to Speech==<br />
<br />
For text-to-speech voices you will need to install speech dispatcher and at least a voice. Most distros ship packages for that in their repositories.<br />
<br />
== Run Mumble ==<br />
<br />
cd release<br />
./mumble<br />
<br />
== Run Murmur ==<br />
<br />
* see [[Running Murmur]]<br />
<br />
[[Category:Development]]</div>Arraihttps://wiki.mumble.info/index.php?title=BuildingLinux&diff=2852BuildingLinux2009-02-28T19:29:50Z<p>Arrai: added libcap-dev, required for /usr/include/sys/capability.h</p>
<hr />
<div>This guide is based (but not only) on this article [http://www.linux-gamers.net/modules/newbb/viewtopic.php?topic_id=2896&forum=6] found at www.linux-gamers.net.<br />
<br />
== Install the dependencies ==<br />
<br />
For Mumble/Murmur 1.1.0 and greater (including SVN), Qt 4.3 is required.<br />
<br />
=== For Debian / Ubuntu ===<br />
The following command makes sure you have the needed libraries and dependencies installed to build Mumble and Murmur from source!<br />
<br />
apt-get install qt4-dev-tools libqt4-dev libspeex1 libspeex-dev libboost-dev libasound2-dev libxevie-dev libxevie1 libssl-dev g++ libspeechd-dev libzeroc-ice-dev libpulse-dev slice2cpp libcap-dev<br />
<br />
It's recommended to remove the package qt3-dev-tools if installed.<br />
<br />
You can also install the libg15-dev libraries for Logitech G15 Keyboard serie.<br />
<br />
Now go on to the section [[#Installing_from_source]].<br />
<br />
== Installing from source ==<br />
<br />
The most generic approach to install mumble under any Linux is to install from source.<br />
Either get the current mumble source over svn or get the latest tarball release from sourceforge.net.<br />
<br />
=== SVN ===<br />
For compiling from svn make sure you've installed subversion and git-core (includes git-clone)<br />
<br />
apt-get install subversion git-core<br />
<br />
svn co https://mumble.svn.sourceforge.net/svnroot/mumble/trunk mumble<br />
cd mumble/<br />
git-clone http://git.xiph.org/speex.git/ speex<br />
<br />
=== tarball release ===<br />
Download the latest tarball release from sf.net http://sourceforge.net/project/showfiles.php?group_id=147372 and extract it:<br />
<br />
tar xzfv mumble-x.x.x.tar.gz # (whereas the X are the version numbers of mumble)<br />
cd mumble-x.x.x<br />
<br />
=== Compile Mumble and Murmur ===<br />
For more configuration options on the qmake command read the supplied INSTALL file.<br />
<br />
Be sure to have the pre-requisites installed and in place for your linux distribution (see the sections above) before you begin compiling it.<br />
<br />
qmake main.pro<br />
make<br />
<br />
If you want to compile Murmur (Mumble server) only, then type<br />
<br />
qmake main.pro CONFIG+=no-client<br />
make<br />
<br />
Note: If you are using Debian/Ubuntu with both Qt3 and Qt4 installed use the command "qmake-qt4" instead of "qmake"<br />
<br />
==Text to Speech==<br />
<br />
For text-to-speech voices you will need to install speech dispatcher and at least a voice. Most distros ship packages for that in their repositories.<br />
<br />
== Run Mumble ==<br />
<br />
cd release<br />
./mumble<br />
<br />
== Run Murmur ==<br />
<br />
* see [[Running Murmur]]<br />
<br />
[[Category:Development]]</div>Arraihttps://wiki.mumble.info/index.php?title=BuildingLinux&diff=2537BuildingLinux2009-01-18T21:13:06Z<p>Arrai: added required slice2cpp packet</p>
<hr />
<div>This guide is based (but not only) on this article [http://www.linux-gamers.net/modules/newbb/viewtopic.php?topic_id=2896&forum=6] found at www.linux-gamers.net.<br />
<br />
== Install the dependencies ==<br />
<br />
For Mumble/Murmur 1.1.0 and greater (including SVN), Qt 4.3 is required.<br />
<br />
=== For Gentoo ===<br />
These instructions for Gentoo don't make use of the Mumble ebuild in the portage tree! Here, you install the needed dependencies to build Mumble and Murmur from the source package! <br />
==== Mumble (client) dependencies ==== <br />
Dependencies: Qt4, speex, alsa-lib, boost, libXevie, speed-dispatcher<br />
<br />
Qt4 needs to be built with certain use flags: sqlite3, ssl. If your Qt4 is not built with those flags yet, then re-install Qt4 like that:<br />
echo x11-libs/qt ssl dbus sqlite3 >> /etc/portage/package.use<br />
emerge -av ">=x11-libs/qt-4.3" <br />
<br />
Get the other dependencies together:<br />
emerge -av --oneshot ">=media-libs/speex-1.2_beta3" media-libs/alsa-lib dev-libs/boost x11-libs/libXevie app-accessibility/speech-dispatcher<br />
Now stop being root and get and compile the mumble tarball as written in the section "Installing from source".<br />
<br />
==== Murmur (server) dependencies ==== <br />
Dependencies: Qt4, speex<br />
<br />
Qt4 needs to be built with certain use flags: sqlite3, ssl. If your Qt4 is not built with those flags yet, then re-install Qt4 like that:<br />
echo x11-libs/qt ssl dbus sqlite3 >> /etc/portage/package.use<br />
emerge -av ">=x11-libs/qt-4.3" <br />
<br />
Get the other dependencies together:<br />
emerge -av --oneshot ">=media-libs/speex-1.2_beta3"<br />
Now stop being root and get and compile the mumble tarball as written in the section "Installing from source".<br />
<br />
=== For Debian / Ubuntu ===<br />
<br />
apt-get install qt4-dev-tools libqt4-dev libqt-opengl-dev libspeex1 libspeex-dev libboost-dev libasound2-dev libxevie-dev libxevie1 libssl-dev g++ libspeechd-dev libzeroc-ice-dev libpulse-dev slice2cpp<br />
<br />
It's recommended to remove the package qt3-dev-tools if installed.<br />
<br />
== Installing from source ==<br />
<br />
The most generic approach to install mumble under any Linux is to install from source.<br />
Either get the current mumble source over svn or get the latest tarball release from sourceforge.net.<br />
<br />
=== SVN ===<br />
If compiling from svn you're also going to need git to download speex.<br />
<br />
svn co https://mumble.svn.sourceforge.net/svnroot/mumble/trunk mumble<br />
cd mumble/<br />
git-clone http://git.xiph.org/speex.git/ speex<br />
<br />
=== tarball release ===<br />
Download the latest tarball release from sf.net http://sourceforge.net/project/showfiles.php?group_id=147372 and extract it:<br />
<br />
tar xzfv mumble-x.x.x.tar.gz # (whereas the X are the version numbers of mumble)<br />
cd mumble-x.x.x<br />
<br />
=== Compile Mumble and Murmur (Mumble server) ===<br />
Be sure to have the pre-requisites installed and in place for your linux distribution (see the sections above) before you begin compiling it:<br />
<br />
qmake main.pro<br />
make<br />
<br />
If you want to compile Murmur (Mumble server) only type<br />
<br />
qmake main.pro CONFIG+=no-client<br />
make<br />
<br />
Note: If you are using Debian/Ubuntu with both Qt3 and Qt4 installed use the command "qmake-qt4" instead of "qmake"<br />
<br />
==Text to Speech==<br />
<br />
For text-to-speech voices you will need to install speech dispatcher and at least a voice. Most distros ship packages for that in their repositories.<br />
<br />
== Run Mumble ==<br />
<br />
cd release<br />
./mumble<br />
<br />
== Run Murmur ==<br />
<br />
* see [[Running Murmur]]<br />
<br />
[[Category:Development]]</div>Arraihttps://wiki.mumble.info/index.php?title=BuildingLinux&diff=1963BuildingLinux2008-03-20T12:56:54Z<p>Arrai: added missing packet</p>
<hr />
<div>This guide is based on this article [http://www.linux-gamers.net/modules/newbb/viewtopic.php?topic_id=2896&forum=6] found at www.linux-gamers.net.<br />
<br />
== Install the dependencies ==<br />
<br />
For Mumble/Murmur 1.1.0 and greater (including SVN), Qt 4.3 is required. For the 1.0.0 release, Qt 4.2 is sufficient.<br />
<br />
=== For Gentoo ===<br />
<br />
Note: Make sure you have sqlite and/ or sqlite3 in your USE flags in /etc/make.conf, if you haven't emerged qt4 with these before, you need to reemerge it.<br />
<br />
emerge dev-libs/boost media-libs/speex x11-libs/libXevie x11-libs/qt (See Note)<br />
<br />
=== For Debian / Ubuntu ===<br />
<br />
apt-get install qt4-dev-tools libqt4-dev libspeex1 libspeex-dev libboost-dev libasound2-dev libxevie-dev libxevie1 libssl-dev g++ libspeechd-dev<br />
<br />
It's recommended to remove the package qt3-dev-tools if installed.<br />
<br />
If you want to use versions of Mumble greater greater than 1.0, you'll need to use Debian lenny or Ubuntu Gutsy, as they are the only versions supporting Qt 4.3.<br />
<br />
== Download the source ==<br />
<br />
Get the mumble source<br />
<br />
svn co https://mumble.svn.sourceforge.net/svnroot/mumble/trunk mumble<br />
cd mumble/<br />
<br />
== Compile Mumble and Murmur (Mumble server) ==<br />
<br />
qmake main.pro<br />
make<br />
<br />
Alternatively, if you are using Debian:<br />
<br />
qmake-qt4 main.pro<br />
make<br />
<br />
===Push to talk===<br />
<br />
For using push to talk, edit /etc/X11/xorg.conf:<br />
<br />
Section "Extensions"<br />
Option "XEVIE" "Enable"<br />
EndSection<br />
<br />
Restart the Xserver.<br />
<br />
'''Note''': If you use Mumble 1.1.0 or newer, you don't need to enable Xevie, if you run mumble as an user with read access to /dev/input<br />
<br />
===Text to Speech===<br />
<br />
For text-to-speech voices you will need to install festival and at least a voice. Most distros ship packages for that in their repositories.<br />
<br />
== Run Mumble ==<br />
<br />
cd release<br />
./mumble<br />
<br />
== Run Murmur ==<br />
<br />
* see [[Running Murmur]]<br />
<br />
[[Category:Development]]</div>Arraihttps://wiki.mumble.info/index.php?title=Talk:DBus_Methods&diff=1962Talk:DBus Methods2008-03-17T21:35:39Z<p>Arrai: </p>
<hr />
<div>Hi, i've just created this page by using that script I've posted [[DBus#Documentation|here]]. I'm not that happy with the hierarchical structure, but i couldn't think of any better approach. Feel free to edit the page if you have a better idea --[[User:Arrai|Arrai]] 14:35, 17 March 2008 (PDT)</div>Arraihttps://wiki.mumble.info/index.php?title=DBus_Methods&diff=1961DBus Methods2008-03-17T21:31:54Z<p>Arrai: </p>
<hr />
<div>This is a documentation of the DBus interface. Mostly useful for creating scripts for interacting with murmur.<br />
<br />
= net.sourceforge.mumble.Meta =<br />
<br />
== start ==<br />
Starts a virtual server<br />
=== input parameters ===<br />
* [int] server_id The specific server<br />
<br />
== stop ==<br />
Stops a virtual server<br />
=== input parameters ===<br />
* [int] server_id The specific server<br />
<br />
== newServer ==<br />
Creates a new virtual server<br />
=== output parameters ===<br />
* [int] server_id The id of the new created server<br />
<br />
== deleteServer ==<br />
deletes a virtual server<br />
=== input parameters ===<br />
* [int] server_id The specific server<br />
<br />
== getBootedServers ==<br />
Returns a list of all active servers<br />
=== output parameters ===<br />
* [int]* server_id<br />
<br />
== getAllServers ==<br />
Returns a list of all servers<br />
=== output parameters ===<br />
* [int]* server_id<br />
<br />
== isBooted ==<br />
check, whether a server is booted<br />
=== input parameters ===<br />
* [int] server_id<br />
=== output parameters ===<br />
* [boolean] is_booted<br />
<br />
== getConf ==<br />
receive the configuration of a server by key<br />
=== input parameters ===<br />
* [int] server_id<br />
* [string] key<br />
=== output parameters ===<br />
* [string] value<br />
<br />
== getAllConf ==<br />
receive the whole configuration of a server<br />
=== input parameters ===<br />
* [int] server_id<br />
=== output parameters ===<br />
* [string|string]* key->value map<br />
<br />
== getDefaultConf ==<br />
receive the default configuration<br />
=== output parameters ===<br />
* [string|string]* key->value map<br />
<br />
== setConf ==<br />
set the value of a specific key on a specific server<br />
=== input parameters ===<br />
* [int] server_id<br />
* [string] key<br />
* [string] value<br />
<br />
== setSuperUserPassword ==<br />
set the superuser password on a specific server<br />
=== input parameters ===<br />
* [int] server_id<br />
* [string] password<br />
<br />
== rotateLogs ==<br />
rotate the logs<br />
<br />
== getLog ==<br />
get the log of a specific server in a specific time frame<br />
=== input parameters ===<br />
* [int] server_id<br />
* [int] min_seconds<br />
* [int] max_seconds<br />
<br />
== quit ==<br />
shutdown the server</div>Arraihttps://wiki.mumble.info/index.php?title=DBus_Methods&diff=1960DBus Methods2008-03-17T21:25:35Z<p>Arrai: </p>
<hr />
<div>This is a documentation of the DBus interface. Mostly useful for creating scripts for interacting with murmur.<br />
<br />
= net.sourceforge.mumble.Meta =<br />
<br />
== start ==<br />
Starts a virtual server<br />
=== input parameters ===<br />
* [int] server_id The specific server<br />
<br />
== stop ==<br />
Stops a virtual server<br />
=== input parameters ===<br />
* [int] server_id The specific server<br />
<br />
== newServer ==<br />
Creates a new virtual server<br />
=== output parameters ===<br />
* [int] server_id The id of the new created server<br />
<br />
== deleteServer ==<br />
deletes a virtual server<br />
=== input parameters ===<br />
* [int] server_id The specific server<br />
<br />
== getBootedServers ==<br />
Returns a list of all active servers<br />
=== output parameters ===<br />
* [int]* server_id<br />
<br />
== getAllServers ==<br />
Returns a list of all servers<br />
=== output parameters ===<br />
* [int]* server_id<br />
<br />
== isBooted ==<br />
check, whether a server is booted<br />
=== input parameters ===<br />
* [int] server_id<br />
=== output parameters ===<br />
* [boolean] is_booted<br />
<br />
== getConf ==<br />
receive the configuration of a server by key<br />
=== input parameters ===<br />
* [int] server_id<br />
* [string] key<br />
=== output parameters ===<br />
* [string] value<br />
<br />
== getAllConf ==<br />
receive the whole configuration of a server<br />
=== input parameters ===<br />
* [int] server_id<br />
=== output parameters ===<br />
* [string|string]* key->value map<br />
<br />
== getDefaultConf ==<br />
receive the default configuration<br />
=== output parameters ===<br />
* [string|string]* key->value map</div>Arraihttps://wiki.mumble.info/index.php?title=DBus_Methods&diff=1959DBus Methods2008-03-17T21:16:37Z<p>Arrai: </p>
<hr />
<div>This is a documentation of the DBus interface. Mostly useful for creating scripts for interacting with murmur.<br />
<br />
= net.sourceforge.mumble.Meta =<br />
<br />
== start ==<br />
Starts a virtual server<br />
=== input parameters ===<br />
* [int] server_id The specific server<br />
<br />
== stop ==<br />
Stops a virtual server<br />
=== input parameters ===<br />
* [int] server_id The specific server<br />
<br />
== newServer ==<br />
Creates a new virtual server<br />
=== output parameters ===<br />
* [int] server_id The id of the new created server<br />
<br />
== deleteServer ==<br />
deletes a virtual server<br />
=== input parameters ===<br />
* [int] server_id The specific server</div>Arraihttps://wiki.mumble.info/index.php?title=DBus&diff=1958DBus2008-03-17T20:51:15Z<p>Arrai: time to do some documentation ;)</p>
<hr />
<div>= Configuring DBus for Murmur =<br />
<br />
Since point-to-point DBus connections don't work in Qt yet, you have two options to configure Murmur for dbus use.<br />
<br />
== A Windows machine ==<br />
<br />
Since Murmur can't run without an active desktop on windows, you can safely ignore this setup. Just make sure your murmur.ini says<br />
<pre><br />
dbus=session<br />
</pre><br />
<br />
== Your own machine with root access ==<br />
<br />
If you own the box you're running murmur on, and you have only one murmur process, you'll want to use the system dbus. The first step is creating a new file called ''/etc/dbus-1/system.d/murmurd.conf''<br />
<pre><br />
<!DOCTYPE busconfig PUBLIC<br />
"-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN"<br />
"http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd"><br />
<busconfig><br />
<br />
<policy user="mumble"><br />
<allow own="net.sourceforge.mumble.murmur"/><br />
</policy><br />
<policy user="root"><br />
<allow own="net.sourceforge.mumble.murmur"/><br />
</policy><br />
<br />
<policy context="default"><br />
<allow send_destination="net.sourceforge.mumble.murmur"/><br />
<allow receive_sender="net.sourceforge.mumble.murmur"/><br />
</policy><br />
</busconfig><br />
</pre><br />
<br />
Then restart the system dbus daemon. Please note that this configuration allows anyone with a user on your machine to control the murmur process, so you might want to tighten security slightly.<br />
<br />
In your murmur.ini, make sure it says<br />
<pre><br />
dbus=system<br />
</pre><br />
<br />
== A shared machine ==<br />
<br />
First, we'll have to start a dbus daemon and place the session info somewhere.<br />
<br />
<pre><br />
dbus-launch --sh-syntax > ~/.dbus.sh<br />
source ~/.dbus.sh<br />
</pre><br />
<br />
Make sure your murmur.ini has <br />
<pre><br />
dbus=session<br />
</pre><br />
<br />
Since there can be many session busses on a system, you'll always need to specify which one to use. So for every new shell you open, you should always<br />
<pre><br />
source ~/.dbus.sh<br />
</pre><br />
<br />
You should not put the above into your ''.bashrc'' or similar, as most X sessions will have their own and separate session dbus.<br />
<br />
When using the session bus, only the userid who created the bus can use it. Hence, you have to make sure that any scripts you write run with the same user ID.<br />
<br />
= Making sure it works =<br />
<br />
Start murmur with the options ''-fg -v'', which will run it in the foreground with full debugging. You should see the line "DBus registration succeeded".<br />
<br />
If your distribution includes the full Qt4 tools package, you'll have a program called ''qdbus'' which can be used to inspect the dbus system. Try running<br />
<pre><br />
qdbus --system net.sourceforge.mumble.murmur /<br />
</pre><br />
or if you're using the session bus:<br />
<pre><br />
qdbus --session net.sourceforge.mumble.murmur /<br />
</pre><br />
<br />
You should see a long list of function names. You can actually use the simpler functions directly from qdbus. For example, you can set a new superuser password with<br />
<pre><br />
qdbus --system net.sourceforge.mumble.murmur / net.sourceforge.mumble.Meta.setSuperUserPassword 1 supahsecret<br />
</pre><br />
<br />
= Documentation =<br />
You can use the Introspect method for receiving a list of all available commands. A simple script to create an output can look like this:<br />
<pre><br />
#!/usr/bin/python<br />
import dbus<br />
<br />
dbus_base = 'net.sourceforge.mumble.murmur'<br />
bus = dbus.SystemBus()<br />
murmur = bus.get_object(dbus_base, '/')<br />
print murmur.Introspect()<br />
</pre><br />
For a documentation of all dbus methods have a look at [[DBus Methods]].<br />
= Showing the list of users on a webpage =<br />
<br />
There is a small perl example called ''scripts/weblist.pl'' in the mumble distribution. It works as a CGI for most systems.<br />
<br />
= Using a PhpBB3 as authentication source =<br />
<br />
There is an extended example of how to use the authenticator called ''scripts/dbusauth.pl''. You'll need to configure where your phpBB3 database resides, but once that is done you'll simply have to run the script after starting murmur to allow authentication to be done through the phpBB3 database.<br />
<br />
Any group associations the user has on phpBB3 is copied to a temporary group on a root channel (and by default inherited to all subchannels). Please note that this is a temporary group membership and as such will not show up in the Edit ACL dialogs.</div>Arraihttps://wiki.mumble.info/index.php?title=FAQ/English&diff=1932FAQ/English2008-03-10T12:28:31Z<p>Arrai: added linux sound issue using tts and mumble</p>
<hr />
<div>= This Document in other Languages =<br />
<br />
This Document is available in following Languages:<br><br />
[[FAQ_(English)|English]]&nbsp;&nbsp; [[FAQ_(Deutsch)|Deutsch]]<br />
<br />
<br />
= About Mumble =<br />
<br />
<br />
== What is Mumble? ==<br />
<br />
Mumble is a voice chat application for groups. While it can be used for any kind of activity, it is primarily intended for gaming.<br />
<br />
== What platforms does it run on? ==<br />
<br />
The client, Mumble, runs on Windows XP and Linux. The server component, Murmur, should run on anything you can compile Qt 4.0 on.<br />
<br />
== What are the system requirements? ==<br />
<br />
The client runs on any Linux or Windows XP machine, and you also need a microphone. The server is mostly bandwidth bound, so as long as your network hardware is sufficient it should run on pretty much anything.<br />
<br />
Please note that the binaries distributed from SourceForge are compiled for SSE (Pentium 3 or Athlon-XP). Mumble is a VOIP solution for gaming, and as most modern games require at least that good a CPU it makes little sense for us not to optimize for it.<br />
<br />
== Installing Mumble ==<br />
Prebuilt binary packages can be downloaded from SourceForge[http://sourceforge.net/projects/mumble/] if you're running Windows or an i386 Linux distribution with the Debian package manager installed.<br />
Installation sources:<br />
*Windows: [http://sourceforge.net/project/showfiles.php?group_id=147372 SourceForge]<br />
*Linux:<br />
**Debian, Ubuntu, etc: [http://sourceforge.net/project/showfiles.php?group_id=147372 SourceForge] (.deb) or TreviƱo repository ([http://3v1n0.tuxfamily.org/])<br />
**RPM based distro's: You could try [http://sourceforge.net/forum/forum.php?thread_id=1782689&forum_id=492606 a rpm found in the forum]. <br />
**Gentoo: ''emerge mumble'' should do it (You'll need sqlite and/or sqlite3 flags enabled, and reemerge qt4 if it was emerged without them)<br />
**Archlinux: You can find a PKGBUILD in the AUR: [http://aur.archlinux.org/packages.php?do_Details=1&ID=10221]<br />
<br />
'''Disclaimer''': Only the files are SourceForge are official. Be careful with the other ones.<br />
<br />
For those who need to (or want to), here are two good tutorials for compiling Mumble/Murmur for your system:<br />
*Linux - [[Building_from_Source]]<br />
*Windows - [[BuildingWindows]]<br />
<br />
== What makes Mumble better? ==<br />
<br />
Mumble has very low latency combined with good sound quality; it uses Speex extensively, not just the voice compression technology, but also the voice preprocessing to remove noise and improve clarity. Mumble also has positional audio for supported games, meaning the other players' voice will come from the direction their character is in game.<br />
<br />
== What are the bandwidth requirements? ==<br />
<br />
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 64.6 kbit/s including the IP and UDP overhead. With 80 ms transmission delay, the lowest quality speech and no positional information, it is 11.0 kbit/s (again with IP and UDP overhead). The default uses 45.4 kbit/s; we did not hear any noticable improvement in quality from the last 20 kbit/s. When comparing with other products, remember to compare the total bandwidth use and not just the bitrate of the audio encoding.<br />
<br />
There are two parts to tuning the bandwidth; the audio bitrate per audio frame (20ms) 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 (50 packets per second), that is 1400 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.<br />
<br />
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 asymetric lines and hence it is only upload that is a bottleneck.<br />
<br />
== What tools did you use to make this? ==<br />
<br />
See [[Development Tools]].<br />
<br />
== How can I help? ==<br />
<br />
A good start would be just using Mumble. If you like it, tell all your friends. If you do not like it, tell us what is wrong so we can fix it.<br />
<br />
= Audio Features = <br />
<br />
== How does the positional sound work? ==<br />
<br />
Your position ingame is transmitted along with every audio packet, and Mumble uses standard DirectSound 3D to position the audio on the receiver side. Only games for which a plug-in has been written get positional audio. All other games will work as well, you just will not get 3D sound.<br />
<br />
== Why does Mumble sound so much better than other voice products? ==<br />
<br />
One word: Denoising. This is a standard part of Speex 1.1 and above, and any voice product already implementing speex should be able to trivially include the same filtering. <br />
Removing the noise from the input means that the audio will be clearer and that the needed bitrate will decrease. It takes fewer bits to model clear voice than it does to accurately represent the noise, so in any noisy transmission a large share of the bits will be noise modelling.<br />
<br />
== Where is the volume control? ==<br />
<br />
Mumble uses the default volume you have configured in your operating system. There is no support for amplifying incoming voices, and there probably will not be, as this will decrease audio quality, something we are very reluctant to do.<br />
<br />
== The text-to-speech quality is horrible! ==<br />
<br />
We use the standard MS Speech API, and the included voices are not all that good. If you have installed either MS Office or the Speech SDK, you will get more voices which can be configured from the Speech control panel. You can also buy a commercial Text-To-Speech engine; as long as it's SAPI5 compatible it can be used by Mumble. The main developers are currently using NeoSpeech Kate (buyable standalone from [http://www.nextup.com NextUp]).<br />
<br />
== Why do some voices sound metallic? ==<br />
<br />
Mumble uses Speex noise filtering, and if the environment of the sender is especially noisy, some parts of the voice will be filtered as well. The alternative would be noisy sound, meaning precious bandwidth would be used to encode noise and the clarity of the voice would also decrease.<br />
<br />
== Why doesn't the voice activity detect my voice any more? ==<br />
<br />
If you change your audio environment suddenly and drastically, by for example disconnecting and reconnecting your microphone or dragging a piece of paper directly over the microphone, you will throw the voice preprocessor off balance. It will recover, but it will take time. <br />
<br />
To reset the preprocessor, choose 'Reset' from the 'Audio' menu.<br />
<br />
== What is this weird echo I hear of myself from other users? ==<br />
<br />
Unfortunately, a lot of popular headsets produce tiny traces of echo. In other VOIP products, you will not notice it because the echo is lower than the noise level, but as Mumble dutifully removes all noise, the echo suddenly becomes clear. There is little the person hearing the echo can do, but there are a few things the person producing the echo can do. The easy solution is to use ASIO and enable echo cancellation, however this requires that the headset is of the analog type (no USB) and a very high quality soundcard.<br />
<br />
The more troublesome solution is to modify the headset. If it is possible to pry the arm with the microphone from the headphones, do so and reattach it with a thick piece of rubber tape; this should insulate it from vibrations. If your headset is open (no large earmuffs), there exists an echo path through air from the headphones to the microphone. You can fix this by attaching anything foam-like to the front of the headphones to muffle the sound heard outside them, but this will most likely ruin the ergonomics of the headset as well as look somewhat odd.<br />
<br />
We might put up a page of "tested headsets" if anyone wants it.<br />
<br />
= Server =<br />
<br />
== What sort of bandwidth will I need for the server? ==<br />
<br />
Worst case scenario: Number of users &times; Number of talking users &times; 60 kbit/s. With less aggressive quality settings, it's ~20 kbit/s, and the bare minimum is 12kbit/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.<br />
<br />
This means that a server with 20 players and 2 players talking at once requires 0.8-2.4 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 />
<br />
== Where do I configure the welcome message, listen port and so on? ==<br />
<br />
murmur.ini, it is self-documenting.<br />
<br />
== How do the ACLs work? ==<br />
<br />
See [[ACL and Groups]]<br />
<br />
== mumble.pri:8: Unknown test function: CONFIG ==<br />
<br />
Mumble requires Qt version 4.3 or better; you are running qmake from Qt 3<br />
<br />
== Where is the administrator account? ==<br />
<br />
The topmost user in the Mumble hierarchy is the useraccount "SuperUser", which bypasses all permission checks and is always allowed to do anything. SuperUser can't be used as a normal user account (it can't talk) and should only be used for initial configuration or to recover from misconfiguration.<br />
<br />
To set the superuser password, start murmur with<br />
murmur.exe -supw supersecretpw<br />
or<br />
murmurd -supw supersecretpw<br />
<br />
== How can I reset the database? ==<br />
<br />
Delete the murmur.sqlite file.<br /><br />
Rerun the command:<br /><br /><br />
<br />
<code><br />
murmur -supw <password><br />
</code><br /><br />
<br />
== How can I add an user? ==<br />
See [[Registering_users]]<br />
<br />
== How can I change a users password? ==<br />
<code><br />
$ '''sqlite3 murmur.sqlite'''<br /><br />
sqlite> '''UPDATE players SET pw = 'newpassword' WHERE name = 'playername';'''<br /><br />
sqlite> <Ctrl-D><br /><br />
</code><br />
<br />
== How do I backup the database? ==<br />
<br />
Shut down the server (kill the process), and make a copy of murmur.sqlite. That file is the database.<br />
<br />
<br />
== How do I run Murmur as a Linux/Unix Sys V service? ==<br />
<br />
See [[Murmur Init Script]]<br />
<br />
<br />
== How can I use an external database for Murmur? ==<br />
<br />
See [[Murmur and PostgreSQL]]<br />
<br />
= Common Problems and Resolutions =<br />
<br />
Problem: Webserver not able to write to DB when using murmur.cgi. <br />
<br />
Solution: Make sure both DB and directory that DB is in is writing be the webserver user.<br />
<br />
Problem: Error message in murmur.cgi line 118<br />
<br />
Solution: You need an MTA on localhost unless you have defined a different SMTP server.<br />
<br />
Problem: Connecting, but not able to create/join channels<br />
<br />
Solution: You currently cannot use the 0.9.1 client with the CVS version of the server (0.9.2).<br />
<br />
Problem: Can't find Push to Talk button<br />
<br />
Solution: When you set Push to talk in Configure > Settings > Basic Audio, you then need to also bind a key to PTT. You do this in Configure > Settings > Shortcuts.<br />
<br />
== Failure to load mumble_ol.dll ==<br />
<br />
If you are running Win XP with SP2, this is due to a outdated DirectX. DirectX is actually updated each and every month, which is why you see every game trying to update your DirectX. So while the version may be 9.0c, what you want to look at is the release date. The latest version may be found at<br />
http://www.microsoft.com/windows/directx/default.mspx<br />
<br />
Downloaded, extracted and installed this package and it fixed this problem for me: [http://www.microsoft.com/downloads/details.aspx?FamilyID=b406cf67-d926-463b-99e8-27199d6626b5&DisplayLang=en DirectX End-User Runtimes (June 2007)] --[[User:Iam8up|Iam8up]] 08:01, 10 July 2007 (PDT)<br />
<br />
== Can't hear other users/users can't hear me ==<br />
<br />
This seems to be fixable by experimenting with the "Use TCP mode" checkbox in "Basic Audio" settings.<br />
<br />
Also this problem can happen if you have server with multible IP's, you need to use server PRIMARY IP or you will experience random "can't hear you, but you can hear me" issues. Not sure is it possible to bind murmur just use one IP from box.<br />
<br />
== Shortcuts don't work on Linux ==<br />
There are two alternatives:<br />
Either use native input or Xevie.<br />
<br />
For native input make sure that the user running Mumble has read permissions on the /dev/input/eventX files of the input devices you want to use for shortcuts.<br />
Be aware that too weak permissions may be a security risk, because malicious processes may log all your input.<br />
<br />
If Mumble can not read from any input device it falls back to Xevie.<br />
<br />
You need to have Xevie enabled in your xorg.conf. To do this you will have to add the following line to xorg.conf, in the extensions section:<br />
<br />
Option "XEVIE" "Enable"<br />
<br />
That should like something like this:<br />
<br />
Section "Extensions"<br />
...<br />
Option "XEVIE" "Enable"<br />
...<br />
EndSection<br />
<br />
Then restart the X server (Ctrl+Alt+Backspace) and try again.<br />
<br />
== Keys seem to lock when using Shortcuts on Linux ==<br />
<br />
Sometimes, keys get "locked" when using Xevie. For example, you press two keys at the same time, but when you release them, only of them is detected as released. This is better seen on games, when you start moving diagonally, and when you stop, it keeps moving.<br />
This can be fixed by playing around with the key repetition settings which can be found:<br />
* Gnome: System->Preferences->Keyboard<br />
* KDE: K menu->Control Center->Peripherals->Keyboard<br />
<br />
You can try changing the Speed/Rate slider and disabling the key repetition (first checkbox)<br />
<br />
== Sound issue on Linux ==<br />
I want to have festival and mumble on the same soundcard, but either i don't hear festival, or mumble puts out this error:<br />
ALSA lib pcm_dmix.c:864:(snd_pcm_dmix_open) unable to open slave<br />
I tried every alsa device listed in mumble, but it makes no difference<br />
<br />
Solution:<br />
You have to use the dmix plugin, which allows simultaneous access on this device from different applications. Open ~/.config/Mumble/Mumble.conf and replace the output entry by<br />
output="plug:\"dmix:CARD=2\""<br />
(please adept the cardnumber according to your system configuration)<br />
<br />
After this you have to edit/create your festival configruation, which is located at ~/.festivalrc.<br />
(Parameter.set 'Audio_Command "aplay -D plug:dmix:2 $FILE")<br />
(Parameter.set 'Audio_Required_Format "snd")<br />
(Parameter.set 'Audio_Method 'Audio_Command)<br />
(again, adept the cardnumber)</div>Arrai