- 1 Getting and Installing Mumble
- 2 Post-installation tips
- 2.1 Common tips
- 2.2 Windows
- 2.3 Linux
Getting and Installing Mumble
Just head to SourceForge downloads page, get the Windows executable and run it. Follow the installer instructions and you are done.
Also, you can build Mumble yourself from source as described in BuildingWindows.
If you want to compile your own version of Mumble, you can read some help in Building_from_Source.
In hardy, the 1.1.X series is included, so just
apt-get install mumble mumble-server
If you are running gutsy, or want a newer version than what is available in the official repository, you can download the .deb package avalaible at SourceForge and install it with your package manager.
Alternately you can use the PPA for mumble builds, which can be found at launchpad. The PPA builds are not signed, but they include builds for both i386 and amd64. Add the PPA to your list of sources, and you can apt-get install it and it will automatically track new releases of Mumble.
Install them via double click.
PCLinuxOS and other RPM based distros
You can find a rpm package in the forum. Note that it is not officially supported, but it should work. You can install it with your rpm package manager or typing (as root):
rpm -i mumble-1.0.0-2.i386.rpm
That should do it. You will need Qt4 compiled with the sqlite and sqlite3 flags. Note that the ebuild in the repository is a little outdated, you can find newer versions in the forums.
A PKGBUILD is avalaible in the AUR. Download the tarball and then run:
tar xfv mumble.tar.gz cd mumble makepkg
That should create a package for you. Of course, you need to install all the dependencies listed before. To do it in a single command:
pacman -S alsa-lib qt4 libxevie sqlite3 boost
Finally, install the package:
pacman -A mumble-1.0.0-1.pkg.tar.gz
Of course, replace the package name as appropriate.
Mac OS X
There are currently no precompiled Mac OS X binaries. But you can build Mumble yourself from source as described in BuildingMacOsX.
Initializing/Resetting Murmur password
murmur -supw <password>
That will change the password for SuperUser, a special user that has all rights. If you want to reset the entire database, just delete murmur.sqlite and the recreate it with the command above.
The Text-To-Speech voices that ship by default with Windows are not all that good (and if you are not English, its even worse as it will try to speak english even when the text is not). 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 NextUp).
Creating a server connection shortcut
You can right click on your desktop and choose "New" and pick "Shortcut" from the sub-menu. In the box that says "Type the location of the item" put "mumble://username:password@servername/channel" replacing the "username" with the name you log into the murmur server with (or omitting it and mumble will ask you for a user name), replacing "servername" with the DNS name or IP address of the murmur server. "Channel" may be omitted if you want to connect to the root channel. If a password is not specified mumble will request one from you when it attempts to connect. The bare minimum required for the shortcut would be "mumble://servername" with mumble requesting a username and a password upon attempting to connect to "servername". This format would also be used to embed a link to your murmur server in a web page, perhaps in the members section of a clan home page.
It complains about mumble_ol.dll / Problems with Overlay
Murmur dies when I log out! How can I get Murmur to stay on all the time?
If you've noticed that the Murmur server dies when you log out of Windows, this is expected. If you want Murmur to run all the time, it'll need to be ran as a service. Fortunately, this is really easy to do! For the purposes of this write-up, the service we are creating is Murmur Demo. You may call it something else if you so choose.
Some references you'll see int his write-up:
instsrv.exe - A program that adds services to the Windows registry.
srvany.exe - A program that allows any Windows application and some Windows 16-bit applications to run as a service.
Step 1: Gain Administrator access on the machine running Murmur.
Step 2: Download and install the following collection of tools from Microsoft to the default directory (C:\Program Files\Windows Resource Kits):
Step 3: Open a command console (Start >> Accessories >> Command Prompt).
Step 4: If you have installed to the default directory, type the following:
"C:\Program Files\Windows Resource Kits\Tools\instsrv.exe" "Murmur" "C:\Program Files\Windows Resource Kits\Tools\srvany.exe"
Below is an example of what you should see:
The result of this step is a new service in the Services console (Start >> Control Panel >> Administrative Tools >> Services).
Be sure to close the Services console before proceeding.
Step 5: Open the registry editor (Start >> Run and enter "regedit") and navigate to the following key:
Regedit should look something like this:
Step 6: Right click on the key name ("Murmur Demo") in the left panel of regedit, and from the menu that pops up, select New >> Key.
Step 7: Name this new key "Parameters"
Step 8: Right click on the key name ("Parameters") in the left panel of regedit, and from the menu that pops up, select New >> String value.
Step 9: Name this new String value "Application".
Step 10: Right click on the String value ("Application) in the right panel of regedit, and from the menu that pops up, select Modify. Change the value from blank to the full path to your murmur.exe file.
Repeat steps 8 through 10, making a second String value called "AppDirectory" and set its value to the full directory path of your murmur.exe file. When you're done making your registry changes, your edits should produce something like this:
Step 11: Close Regedit
Step 12: Open the Services console. Navigate to your service, and right click it and select Properties.
Step 13: Make sure the Startup Type value is Automatic, and then press the Start button.
At this point, the server should launch, although you probably won't see it. You can test to see if it's working by trying to connect to it using your client.
If your server did start, congratulations, you're done. You should be able to logoff and reboot the machine if you want, with Murmur pesisting through both.
If your server did not start, recheck your settings. Most problems are related to typos in configuration settings.
Getting the Shortcuts to work
There are two alternatives: Either use native input or Xevie.
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. Be aware that too weak permissions may be a security risk, because malicious processes may log all your input.
If Mumble can not read from any input device it falls back to Xevie.
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:
Option "XEVIE" "Enable"
That should like something like this:
Section "Extensions" ... Option "XEVIE" "Enable" ... EndSection
Then restart the X server (Ctrl+Alt+Backspace) and try again.
Running murmur as a SysV service
You can use Murmur_Init_Script.