https://wiki.mumble.info/api.php?action=feedcontributions&user=Haudrauf&feedformat=atomMumble Wiki - User contributions [en]2024-03-28T18:39:01ZUser contributionsMediaWiki 1.31.0https://wiki.mumble.info/index.php?title=BuildingLinux&diff=2600BuildingLinux2009-02-02T09:41:32Z<p>Haudrauf: /* Compile Mumble and Murmur (Mumble server) */</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 />
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 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 />
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 />
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 ===<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>Haudraufhttps://wiki.mumble.info/index.php?title=BuildingLinux&diff=2599BuildingLinux2009-02-01T23:55:10Z<p>Haudrauf: /* Murmur (server) dependencies */</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 />
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 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 />
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 />
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>Haudraufhttps://wiki.mumble.info/index.php?title=BuildingLinux&diff=2598BuildingLinux2009-02-01T23:53:14Z<p>Haudrauf: /* Mumble (client) dependencies */</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 />
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 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 />
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 />
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>Haudraufhttps://wiki.mumble.info/index.php?title=BuildingLinux&diff=2597BuildingLinux2009-02-01T23:49:31Z<p>Haudrauf: /* For Debian / Ubuntu */</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 />
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 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 />
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 />
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>Haudraufhttps://wiki.mumble.info/index.php?title=Installing_Mumble&diff=2596Installing Mumble2009-02-01T23:45:37Z<p>Haudrauf: /* Gentoo */</p>
<hr />
<div>=Getting and Installing Mumble=<br />
This page shows you directions on how to install Mumble (client) as well as Murmur (server).<br />
<br />
==Windows==<br />
Just head to [http://sourceforge.net/project/showfiles.php?group_id=147372 SourceForge downloads page], get the Windows executable and run it. Follow the installer instructions and you are done.<br />
<br />
Also, you can build Mumble yourself from source as described in [[BuildingWindows]].<br />
<br />
==Linux==<br />
Some Linux distributions already have Mumble packaged so that an easy installation is possible. Check your package manager of your distribution for Mumble. But sometimes those packages are not up to date. So if you want more in-depth information about installing Mumble for Linux read up on [[BuildingLinux]]. Installation from source (svn and tarball) is described there.<br />
<br />
<br />
=== Debian ===<br />
<br />
Debian Testing (lenny) includes the latest official Mumble packages, and is the officially maintained version. New packaging efforts are encouraged to base their file layout and usernames on what is used here, to make third-party packages easier to port. To install:<br />
<br />
'''Client'''<br />
sudo aptitude install mumble<br />
<br />
<br />
'''Server and web applications'''<br />
sudo aptitude install mumble-server mumble-server-web<br />
sudo dpkg-reconfigure mumble-server<br />
<br />
''People who are connected to your Mumble server can go to <nowiki>http://</nowiki><your IP or domain>/mumble/register.cgi to register with the server through a web interface.<br />
''They can also upload a custom texture that will be displayed in the Mumble game overlay from this page. <br />
''Any 600x60 PNG image will work, but if you have an alpha channel on in, it will have transparency.<br />
''<nowiki>http://</nowiki><your IP or domain>/mumble/ shows the list of users in your Mumble server.<br />
<br />
Mumble v1.1.6-x86 for Debian Stable ('Etch', 4.0r5) is available at http://Vocis.K1T.NET/<br />
<br />
=== Ubuntu ===<br />
<br />
==== Official Repository ====<br />
<br />
'''This is the easy way, but you won't always get the latest version.'''<br />
<br />
Ubuntu Hardy Heron (8.04) includes the Mumble 1.1.x series in it's official repository. It's cloned from Debian testing before every Ubuntu release, so while it will lag slightly behind, it won't be by much. Just follow the directions for installing under Debian.<br />
<br />
==== PPA Repository ====<br />
<br />
'''This is a bit more to type, but should always be up-to-date.'''<br />
<br />
As the packages in the official Ubuntu repository aren't always up-to-date, you can add an external PPA repository to your package manager. It should always include the newest stable version of Mumble and Murmur for i386 and amd64 architectures.<br />
<br />
You will have to manually add the repositories for the PPA repository. Go to a command prompt and type <br />
sudo gedit /etc/apt/sources.list<br />
then add the following two lines to the bottom of the file<br />
deb http://ppa.launchpad.net/slicer/ubuntu hardy main<br />
deb-src http://ppa.launchpad.net/slicer/ubuntu hardy main<br />
sudo aptitude update <br />
(replace ''hardy'' with ''gutsy'' or ''intrepid'' if you are on those distributions)<br />
<br />
Afterwards you can use the same command as for installing under Debian (see above).<br />
<br />
More information about the PPA repository can be found at [https://edge.launchpad.net/~slicer/+archive Launchpad]<br />
<br />
===RPM-based distributions===<br />
Fedora, openSUSE, PCLinuxOS, etc. are RPM-based distributions. If their own official package repository doesn't have an up to date version or even no version at all of Mumble, then have a look at openSUSE's Build Service (http://software.opensuse.org). <br />
<br />
There you can find many different RPM-builds for different distributions and architectures of Mumble. '''Note''' that these packages are not officially supported, but it should work. <br />
<br />
Follow this link to see search results for "mumble": http://software.opensuse.org/search?q=mumble<br />
<br />
Often you can install it with the RPM tool of your distribution or by typing (as root):<br />
rpm -i mumble-1.1.7-i386.rpm<br />
<br />
<br />
<br />
===Gentoo===<br />
'''Client'''<br />
<br />
Depending on what other features you want compiled into it, check up on the possible USE-flags: http://www.gentoo-portage.com/media-sound/mumble/USE#ptabs<br />
<br />
For most users it's useful to use the USE-flags alsa, dbus and speech - so we go with it.<br />
It's well possible that the Mumble ebuild is masked by the ~x86 keyword. Here, we make sure it will install anyways.<br />
<br />
Become root and do:<br />
echo media-sound/mumble alsa dbus speech >> /etc/portage/package.use<br />
echo media-sound/mumble ~x86 >> /etc/portage/package.keywords<br />
emerge -av mumble<br />
That should do the magic. If something fails though, check up on [[BuildingLinux]]<br />
<br />
<br />
'''Server'''<br />
<br />
Depending on what other features you want compiled into it, check up on the possible USE-flags: http://www.gentoo-portage.com/media-sound/murmur/USE#ptabs<br />
<br />
It's well possible that the Murmur ebuild is masked by the ~x86 keyword. Here, we make sure it will install anyways.<br />
<br />
Become root and do:<br />
echo media-sound/murmur ~x86 >> /etc/portage/package.keywords<br />
emerge -av murmur<br />
That should do the magic. If something fails though, check up on [[BuildingLinux]]<br />
<br />
===ArchLinux===<br />
A stable PKGBUILD is avalaible in the [http://aur.archlinux.org/packages.php?do_Details=1&ID=10221&K=mumble AUR]. Download the tarball and then run:<br />
tar xzfv mumble*.tar.gz<br />
cd mumble*<br />
makepkg<br />
<br />
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:<br />
<br />
pacman -S alsa-lib qt4 libxevie sqlite3 boost<br />
<br />
Finally, install the package:<br />
<br />
pacman -A mumble-1.0.0-1.pkg.tar.gz<br />
<br />
Of course, replace the package name as appropriate.<br />
<br />
If you want to test a SVN Snapshoth, use this [http://aur.archlinux.org/packages.php?ID=23369 PKGBUILD] in the [http://aur.archlinux.org/packages.php?ID=23369 AUR]. Use [http://wiki.archlinux.org/index.php/Yaourt Yaourt] or the instructions above.<br />
<br />
==Mac OS X==<br />
<br />
Precompiled Mac OS X universal binaries are available from the [http://sourceforge.net/project/showfiles.php?group_id=147372 SourceForge downloads page].<br />
<br />
You can also build it from source yourself if you wish. See [[BuildingMacOsX]] for more information.<br />
<br />
==Snapshots==<br />
<br />
If you want to get the latest snapshots for Mumble and Murmur, you can find those [http://mumble.info/snapshot/ here]. These include the latest builds of Mumble and Murmur for Windows, and static builds of Murmur for Linux.<br />
<br />
=Post-installation tips=<br />
==Common tips==<br />
===Initializing/Resetting Murmur password===<br />
Type:<br />
murmur -supw <password><br />
That will change the password for SuperUser, a special user that has all rights.<br />
If you want to reset the entire database, just delete murmur.sqlite and the recreate it with the command above.<br />
<br />
==Windows==<br />
===Text-to-Speech===<br />
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 [http://www.nextup.com NextUp]).<br />
<br />
===Creating a server connection shortcut===<br />
You can right click on your desktop and choose "New" and pick "Shortcut" from the sub-menu.<br />
In the box that says "Type the location of the item" put "mumble://username:password@servername/channel"<br />
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. <br />
<br />
===It complains about mumble_ol.dll / Problems with Overlay===<br />
If you are running XP you will need to update it to SP2.<br />
<br />
=== Murmur dies when I log out! How can I get Murmur to stay on all the time? ===<br />
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.<br />
<br />
Some references you'll see int his write-up:<br />
<br />
instsrv.exe - A program that adds services to the Windows registry.<br />
<br />
srvany.exe - A program that allows any Windows application and some Windows 16-bit applications to run as a service.<br />
<br />
'''The HOW-TO'''<br />
<br />
Step 1: Gain Administrator access on the machine running Murmur.<br />
<br />
Step 2: Download and install the following collection of tools from Microsoft to the default directory (C:\Program Files\Windows Resource Kits):<br />
<br />
[http://www.microsoft.com/downloads/details.aspx?FamilyID=9d467a69-57ff-4ae7-96ee-b18c4790cffd&displaylang=en Windows 2003 Server Resource Kit].<br />
<br />
Step 3: Open a command console (Start >> Accessories >> Command Prompt).<br />
<br />
Step 4: If you have installed to the default directory, type the following:<br />
<br />
"C:\Program Files\Windows Resource Kits\Tools\instsrv.exe" "Murmur" "C:\Program Files\Windows Resource Kits\Tools\srvany.exe"<br />
<br />
The result of this step is a new service in the Services console (Start >> Control Panel >> Administrative Tools >> Services).<br />
<br />
'''Be sure to close the Services console before proceeding.'''<br />
<br />
Step 5: Open the registry editor (Start >> Run and enter "regedit") and navigate to the following key:<br />
<br />
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Murmur Demo<br />
<br />
<br />
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.<br />
<br />
Step 7: Name this new key "Parameters"<br />
<br />
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.<br />
<br />
Step 9: Name this new String value "Application".<br />
<br />
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.<br />
<br />
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.<br />
<br />
Step 11: Close Regedit<br />
<br />
Step 12: Open the Services console. Navigate to your service, and right click it and select Properties.<br />
<br />
Step 13: Make sure the Startup Type value is Automatic, and then press the Start button.<br />
<br />
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.<br />
<br />
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.<br />
<br />
If your server did not start, recheck your settings. Most problems are related to typos in configuration settings.<br />
<br />
==Linux==<br />
===Getting the Shortcuts Suppression to work===<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 />
=Uninstalling=<br />
[[UninstallingMumble | Instructions for completely removing Mumble, including user created settings and entries.]]</div>Haudraufhttps://wiki.mumble.info/index.php?title=Installing_Mumble&diff=2595Installing Mumble2009-02-01T23:40:51Z<p>Haudrauf: /* Gentoo */</p>
<hr />
<div>=Getting and Installing Mumble=<br />
This page shows you directions on how to install Mumble (client) as well as Murmur (server).<br />
<br />
==Windows==<br />
Just head to [http://sourceforge.net/project/showfiles.php?group_id=147372 SourceForge downloads page], get the Windows executable and run it. Follow the installer instructions and you are done.<br />
<br />
Also, you can build Mumble yourself from source as described in [[BuildingWindows]].<br />
<br />
==Linux==<br />
Some Linux distributions already have Mumble packaged so that an easy installation is possible. Check your package manager of your distribution for Mumble. But sometimes those packages are not up to date. So if you want more in-depth information about installing Mumble for Linux read up on [[BuildingLinux]]. Installation from source (svn and tarball) is described there.<br />
<br />
<br />
=== Debian ===<br />
<br />
Debian Testing (lenny) includes the latest official Mumble packages, and is the officially maintained version. New packaging efforts are encouraged to base their file layout and usernames on what is used here, to make third-party packages easier to port. To install:<br />
<br />
'''Client'''<br />
sudo aptitude install mumble<br />
<br />
<br />
'''Server and web applications'''<br />
sudo aptitude install mumble-server mumble-server-web<br />
sudo dpkg-reconfigure mumble-server<br />
<br />
''People who are connected to your Mumble server can go to <nowiki>http://</nowiki><your IP or domain>/mumble/register.cgi to register with the server through a web interface.<br />
''They can also upload a custom texture that will be displayed in the Mumble game overlay from this page. <br />
''Any 600x60 PNG image will work, but if you have an alpha channel on in, it will have transparency.<br />
''<nowiki>http://</nowiki><your IP or domain>/mumble/ shows the list of users in your Mumble server.<br />
<br />
Mumble v1.1.6-x86 for Debian Stable ('Etch', 4.0r5) is available at http://Vocis.K1T.NET/<br />
<br />
=== Ubuntu ===<br />
<br />
==== Official Repository ====<br />
<br />
'''This is the easy way, but you won't always get the latest version.'''<br />
<br />
Ubuntu Hardy Heron (8.04) includes the Mumble 1.1.x series in it's official repository. It's cloned from Debian testing before every Ubuntu release, so while it will lag slightly behind, it won't be by much. Just follow the directions for installing under Debian.<br />
<br />
==== PPA Repository ====<br />
<br />
'''This is a bit more to type, but should always be up-to-date.'''<br />
<br />
As the packages in the official Ubuntu repository aren't always up-to-date, you can add an external PPA repository to your package manager. It should always include the newest stable version of Mumble and Murmur for i386 and amd64 architectures.<br />
<br />
You will have to manually add the repositories for the PPA repository. Go to a command prompt and type <br />
sudo gedit /etc/apt/sources.list<br />
then add the following two lines to the bottom of the file<br />
deb http://ppa.launchpad.net/slicer/ubuntu hardy main<br />
deb-src http://ppa.launchpad.net/slicer/ubuntu hardy main<br />
sudo aptitude update <br />
(replace ''hardy'' with ''gutsy'' or ''intrepid'' if you are on those distributions)<br />
<br />
Afterwards you can use the same command as for installing under Debian (see above).<br />
<br />
More information about the PPA repository can be found at [https://edge.launchpad.net/~slicer/+archive Launchpad]<br />
<br />
===RPM-based distributions===<br />
Fedora, openSUSE, PCLinuxOS, etc. are RPM-based distributions. If their own official package repository doesn't have an up to date version or even no version at all of Mumble, then have a look at openSUSE's Build Service (http://software.opensuse.org). <br />
<br />
There you can find many different RPM-builds for different distributions and architectures of Mumble. '''Note''' that these packages are not officially supported, but it should work. <br />
<br />
Follow this link to see search results for "mumble": http://software.opensuse.org/search?q=mumble<br />
<br />
Often you can install it with the RPM tool of your distribution or by typing (as root):<br />
rpm -i mumble-1.1.7-i386.rpm<br />
<br />
<br />
<br />
===Gentoo===<br />
'''Client'''<br />
<br />
Depending on what other features you want compiled into it, check up on the possible USE-flags: http://www.gentoo-portage.com/media-sound/mumble/USE#ptabs<br />
For most users it's useful to use the USE-flags alsa, dbus and speech - so we go with it.<br />
It's well possible that the Mumble ebuild is "masked". Here, we make sure it will install anyways.<br />
Become root and do:<br />
echo media-sound/mumble alsa dbus speech >> /etc/portage/package.use<br />
echo media-sound/mumble ~x86 >> /etc/portage/package.keywords<br />
emerge -av mumble<br />
That should do the magic. If something fails though, check up on [[BuildingLinux]]<br />
<br />
<br />
'''Server'''<br />
<br />
Depending on what other features you want compiled into it, check up on the possible USE-flags: http://www.gentoo-portage.com/media-sound/murmur/USE#ptabs<br />
For most users it's useful to use the USE-flag ice - so we go with it.<br />
It's well possible that the Murmur ebuild is "masked". Here, we make sure it will install anyways.<br />
Become root and do:<br />
echo media-sound/murmur ice >> /etc/portage/package.use<br />
echo media-sound/murmur ~x86 >> /etc/portage/package.keywords<br />
emerge -av murmur<br />
That should do the magic. If something fails though, check up on [[BuildingLinux]]<br />
<br />
===ArchLinux===<br />
A stable PKGBUILD is avalaible in the [http://aur.archlinux.org/packages.php?do_Details=1&ID=10221&K=mumble AUR]. Download the tarball and then run:<br />
tar xzfv mumble*.tar.gz<br />
cd mumble*<br />
makepkg<br />
<br />
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:<br />
<br />
pacman -S alsa-lib qt4 libxevie sqlite3 boost<br />
<br />
Finally, install the package:<br />
<br />
pacman -A mumble-1.0.0-1.pkg.tar.gz<br />
<br />
Of course, replace the package name as appropriate.<br />
<br />
If you want to test a SVN Snapshoth, use this [http://aur.archlinux.org/packages.php?ID=23369 PKGBUILD] in the [http://aur.archlinux.org/packages.php?ID=23369 AUR]. Use [http://wiki.archlinux.org/index.php/Yaourt Yaourt] or the instructions above.<br />
<br />
==Mac OS X==<br />
<br />
Precompiled Mac OS X universal binaries are available from the [http://sourceforge.net/project/showfiles.php?group_id=147372 SourceForge downloads page].<br />
<br />
You can also build it from source yourself if you wish. See [[BuildingMacOsX]] for more information.<br />
<br />
==Snapshots==<br />
<br />
If you want to get the latest snapshots for Mumble and Murmur, you can find those [http://mumble.info/snapshot/ here]. These include the latest builds of Mumble and Murmur for Windows, and static builds of Murmur for Linux.<br />
<br />
=Post-installation tips=<br />
==Common tips==<br />
===Initializing/Resetting Murmur password===<br />
Type:<br />
murmur -supw <password><br />
That will change the password for SuperUser, a special user that has all rights.<br />
If you want to reset the entire database, just delete murmur.sqlite and the recreate it with the command above.<br />
<br />
==Windows==<br />
===Text-to-Speech===<br />
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 [http://www.nextup.com NextUp]).<br />
<br />
===Creating a server connection shortcut===<br />
You can right click on your desktop and choose "New" and pick "Shortcut" from the sub-menu.<br />
In the box that says "Type the location of the item" put "mumble://username:password@servername/channel"<br />
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. <br />
<br />
===It complains about mumble_ol.dll / Problems with Overlay===<br />
If you are running XP you will need to update it to SP2.<br />
<br />
=== Murmur dies when I log out! How can I get Murmur to stay on all the time? ===<br />
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.<br />
<br />
Some references you'll see int his write-up:<br />
<br />
instsrv.exe - A program that adds services to the Windows registry.<br />
<br />
srvany.exe - A program that allows any Windows application and some Windows 16-bit applications to run as a service.<br />
<br />
'''The HOW-TO'''<br />
<br />
Step 1: Gain Administrator access on the machine running Murmur.<br />
<br />
Step 2: Download and install the following collection of tools from Microsoft to the default directory (C:\Program Files\Windows Resource Kits):<br />
<br />
[http://www.microsoft.com/downloads/details.aspx?FamilyID=9d467a69-57ff-4ae7-96ee-b18c4790cffd&displaylang=en Windows 2003 Server Resource Kit].<br />
<br />
Step 3: Open a command console (Start >> Accessories >> Command Prompt).<br />
<br />
Step 4: If you have installed to the default directory, type the following:<br />
<br />
"C:\Program Files\Windows Resource Kits\Tools\instsrv.exe" "Murmur" "C:\Program Files\Windows Resource Kits\Tools\srvany.exe"<br />
<br />
The result of this step is a new service in the Services console (Start >> Control Panel >> Administrative Tools >> Services).<br />
<br />
'''Be sure to close the Services console before proceeding.'''<br />
<br />
Step 5: Open the registry editor (Start >> Run and enter "regedit") and navigate to the following key:<br />
<br />
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Murmur Demo<br />
<br />
<br />
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.<br />
<br />
Step 7: Name this new key "Parameters"<br />
<br />
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.<br />
<br />
Step 9: Name this new String value "Application".<br />
<br />
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.<br />
<br />
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.<br />
<br />
Step 11: Close Regedit<br />
<br />
Step 12: Open the Services console. Navigate to your service, and right click it and select Properties.<br />
<br />
Step 13: Make sure the Startup Type value is Automatic, and then press the Start button.<br />
<br />
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.<br />
<br />
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.<br />
<br />
If your server did not start, recheck your settings. Most problems are related to typos in configuration settings.<br />
<br />
==Linux==<br />
===Getting the Shortcuts Suppression to work===<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 />
=Uninstalling=<br />
[[UninstallingMumble | Instructions for completely removing Mumble, including user created settings and entries.]]</div>Haudraufhttps://wiki.mumble.info/index.php?title=Installing_Mumble&diff=2594Installing Mumble2009-02-01T23:40:35Z<p>Haudrauf: /* Gentoo */</p>
<hr />
<div>=Getting and Installing Mumble=<br />
This page shows you directions on how to install Mumble (client) as well as Murmur (server).<br />
<br />
==Windows==<br />
Just head to [http://sourceforge.net/project/showfiles.php?group_id=147372 SourceForge downloads page], get the Windows executable and run it. Follow the installer instructions and you are done.<br />
<br />
Also, you can build Mumble yourself from source as described in [[BuildingWindows]].<br />
<br />
==Linux==<br />
Some Linux distributions already have Mumble packaged so that an easy installation is possible. Check your package manager of your distribution for Mumble. But sometimes those packages are not up to date. So if you want more in-depth information about installing Mumble for Linux read up on [[BuildingLinux]]. Installation from source (svn and tarball) is described there.<br />
<br />
<br />
=== Debian ===<br />
<br />
Debian Testing (lenny) includes the latest official Mumble packages, and is the officially maintained version. New packaging efforts are encouraged to base their file layout and usernames on what is used here, to make third-party packages easier to port. To install:<br />
<br />
'''Client'''<br />
sudo aptitude install mumble<br />
<br />
<br />
'''Server and web applications'''<br />
sudo aptitude install mumble-server mumble-server-web<br />
sudo dpkg-reconfigure mumble-server<br />
<br />
''People who are connected to your Mumble server can go to <nowiki>http://</nowiki><your IP or domain>/mumble/register.cgi to register with the server through a web interface.<br />
''They can also upload a custom texture that will be displayed in the Mumble game overlay from this page. <br />
''Any 600x60 PNG image will work, but if you have an alpha channel on in, it will have transparency.<br />
''<nowiki>http://</nowiki><your IP or domain>/mumble/ shows the list of users in your Mumble server.<br />
<br />
Mumble v1.1.6-x86 for Debian Stable ('Etch', 4.0r5) is available at http://Vocis.K1T.NET/<br />
<br />
=== Ubuntu ===<br />
<br />
==== Official Repository ====<br />
<br />
'''This is the easy way, but you won't always get the latest version.'''<br />
<br />
Ubuntu Hardy Heron (8.04) includes the Mumble 1.1.x series in it's official repository. It's cloned from Debian testing before every Ubuntu release, so while it will lag slightly behind, it won't be by much. Just follow the directions for installing under Debian.<br />
<br />
==== PPA Repository ====<br />
<br />
'''This is a bit more to type, but should always be up-to-date.'''<br />
<br />
As the packages in the official Ubuntu repository aren't always up-to-date, you can add an external PPA repository to your package manager. It should always include the newest stable version of Mumble and Murmur for i386 and amd64 architectures.<br />
<br />
You will have to manually add the repositories for the PPA repository. Go to a command prompt and type <br />
sudo gedit /etc/apt/sources.list<br />
then add the following two lines to the bottom of the file<br />
deb http://ppa.launchpad.net/slicer/ubuntu hardy main<br />
deb-src http://ppa.launchpad.net/slicer/ubuntu hardy main<br />
sudo aptitude update <br />
(replace ''hardy'' with ''gutsy'' or ''intrepid'' if you are on those distributions)<br />
<br />
Afterwards you can use the same command as for installing under Debian (see above).<br />
<br />
More information about the PPA repository can be found at [https://edge.launchpad.net/~slicer/+archive Launchpad]<br />
<br />
===RPM-based distributions===<br />
Fedora, openSUSE, PCLinuxOS, etc. are RPM-based distributions. If their own official package repository doesn't have an up to date version or even no version at all of Mumble, then have a look at openSUSE's Build Service (http://software.opensuse.org). <br />
<br />
There you can find many different RPM-builds for different distributions and architectures of Mumble. '''Note''' that these packages are not officially supported, but it should work. <br />
<br />
Follow this link to see search results for "mumble": http://software.opensuse.org/search?q=mumble<br />
<br />
Often you can install it with the RPM tool of your distribution or by typing (as root):<br />
rpm -i mumble-1.1.7-i386.rpm<br />
<br />
<br />
<br />
===Gentoo===<br />
'''Client'''<br />
Depending on what other features you want compiled into it, check up on the possible USE-flags: http://www.gentoo-portage.com/media-sound/mumble/USE#ptabs<br />
For most users it's useful to use the USE-flags alsa, dbus and speech - so we go with it.<br />
It's well possible that the Mumble ebuild is "masked". Here, we make sure it will install anyways.<br />
Become root and do:<br />
echo media-sound/mumble alsa dbus speech >> /etc/portage/package.use<br />
echo media-sound/mumble ~x86 >> /etc/portage/package.keywords<br />
emerge -av mumble<br />
That should do the magic. If something fails though, check up on [[BuildingLinux]]<br />
<br />
'''Server'''<br />
Depending on what other features you want compiled into it, check up on the possible USE-flags: http://www.gentoo-portage.com/media-sound/murmur/USE#ptabs<br />
For most users it's useful to use the USE-flag ice - so we go with it.<br />
It's well possible that the Murmur ebuild is "masked". Here, we make sure it will install anyways.<br />
Become root and do:<br />
echo media-sound/murmur ice >> /etc/portage/package.use<br />
echo media-sound/murmur ~x86 >> /etc/portage/package.keywords<br />
emerge -av murmur<br />
That should do the magic. If something fails though, check up on [[BuildingLinux]]<br />
<br />
===ArchLinux===<br />
A stable PKGBUILD is avalaible in the [http://aur.archlinux.org/packages.php?do_Details=1&ID=10221&K=mumble AUR]. Download the tarball and then run:<br />
tar xzfv mumble*.tar.gz<br />
cd mumble*<br />
makepkg<br />
<br />
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:<br />
<br />
pacman -S alsa-lib qt4 libxevie sqlite3 boost<br />
<br />
Finally, install the package:<br />
<br />
pacman -A mumble-1.0.0-1.pkg.tar.gz<br />
<br />
Of course, replace the package name as appropriate.<br />
<br />
If you want to test a SVN Snapshoth, use this [http://aur.archlinux.org/packages.php?ID=23369 PKGBUILD] in the [http://aur.archlinux.org/packages.php?ID=23369 AUR]. Use [http://wiki.archlinux.org/index.php/Yaourt Yaourt] or the instructions above.<br />
<br />
==Mac OS X==<br />
<br />
Precompiled Mac OS X universal binaries are available from the [http://sourceforge.net/project/showfiles.php?group_id=147372 SourceForge downloads page].<br />
<br />
You can also build it from source yourself if you wish. See [[BuildingMacOsX]] for more information.<br />
<br />
==Snapshots==<br />
<br />
If you want to get the latest snapshots for Mumble and Murmur, you can find those [http://mumble.info/snapshot/ here]. These include the latest builds of Mumble and Murmur for Windows, and static builds of Murmur for Linux.<br />
<br />
=Post-installation tips=<br />
==Common tips==<br />
===Initializing/Resetting Murmur password===<br />
Type:<br />
murmur -supw <password><br />
That will change the password for SuperUser, a special user that has all rights.<br />
If you want to reset the entire database, just delete murmur.sqlite and the recreate it with the command above.<br />
<br />
==Windows==<br />
===Text-to-Speech===<br />
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 [http://www.nextup.com NextUp]).<br />
<br />
===Creating a server connection shortcut===<br />
You can right click on your desktop and choose "New" and pick "Shortcut" from the sub-menu.<br />
In the box that says "Type the location of the item" put "mumble://username:password@servername/channel"<br />
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. <br />
<br />
===It complains about mumble_ol.dll / Problems with Overlay===<br />
If you are running XP you will need to update it to SP2.<br />
<br />
=== Murmur dies when I log out! How can I get Murmur to stay on all the time? ===<br />
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.<br />
<br />
Some references you'll see int his write-up:<br />
<br />
instsrv.exe - A program that adds services to the Windows registry.<br />
<br />
srvany.exe - A program that allows any Windows application and some Windows 16-bit applications to run as a service.<br />
<br />
'''The HOW-TO'''<br />
<br />
Step 1: Gain Administrator access on the machine running Murmur.<br />
<br />
Step 2: Download and install the following collection of tools from Microsoft to the default directory (C:\Program Files\Windows Resource Kits):<br />
<br />
[http://www.microsoft.com/downloads/details.aspx?FamilyID=9d467a69-57ff-4ae7-96ee-b18c4790cffd&displaylang=en Windows 2003 Server Resource Kit].<br />
<br />
Step 3: Open a command console (Start >> Accessories >> Command Prompt).<br />
<br />
Step 4: If you have installed to the default directory, type the following:<br />
<br />
"C:\Program Files\Windows Resource Kits\Tools\instsrv.exe" "Murmur" "C:\Program Files\Windows Resource Kits\Tools\srvany.exe"<br />
<br />
The result of this step is a new service in the Services console (Start >> Control Panel >> Administrative Tools >> Services).<br />
<br />
'''Be sure to close the Services console before proceeding.'''<br />
<br />
Step 5: Open the registry editor (Start >> Run and enter "regedit") and navigate to the following key:<br />
<br />
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Murmur Demo<br />
<br />
<br />
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.<br />
<br />
Step 7: Name this new key "Parameters"<br />
<br />
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.<br />
<br />
Step 9: Name this new String value "Application".<br />
<br />
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.<br />
<br />
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.<br />
<br />
Step 11: Close Regedit<br />
<br />
Step 12: Open the Services console. Navigate to your service, and right click it and select Properties.<br />
<br />
Step 13: Make sure the Startup Type value is Automatic, and then press the Start button.<br />
<br />
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.<br />
<br />
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.<br />
<br />
If your server did not start, recheck your settings. Most problems are related to typos in configuration settings.<br />
<br />
==Linux==<br />
===Getting the Shortcuts Suppression to work===<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 />
=Uninstalling=<br />
[[UninstallingMumble | Instructions for completely removing Mumble, including user created settings and entries.]]</div>Haudraufhttps://wiki.mumble.info/index.php?title=Installing_Mumble&diff=2593Installing Mumble2009-02-01T23:36:52Z<p>Haudrauf: /* Debian */ version and some wiki markup updated</p>
<hr />
<div>=Getting and Installing Mumble=<br />
This page shows you directions on how to install Mumble (client) as well as Murmur (server).<br />
<br />
==Windows==<br />
Just head to [http://sourceforge.net/project/showfiles.php?group_id=147372 SourceForge downloads page], get the Windows executable and run it. Follow the installer instructions and you are done.<br />
<br />
Also, you can build Mumble yourself from source as described in [[BuildingWindows]].<br />
<br />
==Linux==<br />
Some Linux distributions already have Mumble packaged so that an easy installation is possible. Check your package manager of your distribution for Mumble. But sometimes those packages are not up to date. So if you want more in-depth information about installing Mumble for Linux read up on [[BuildingLinux]]. Installation from source (svn and tarball) is described there.<br />
<br />
<br />
=== Debian ===<br />
<br />
Debian Testing (lenny) includes the latest official Mumble packages, and is the officially maintained version. New packaging efforts are encouraged to base their file layout and usernames on what is used here, to make third-party packages easier to port. To install:<br />
<br />
'''Client'''<br />
sudo aptitude install mumble<br />
<br />
<br />
'''Server and web applications'''<br />
sudo aptitude install mumble-server mumble-server-web<br />
sudo dpkg-reconfigure mumble-server<br />
<br />
''People who are connected to your Mumble server can go to <nowiki>http://</nowiki><your IP or domain>/mumble/register.cgi to register with the server through a web interface.<br />
''They can also upload a custom texture that will be displayed in the Mumble game overlay from this page. <br />
''Any 600x60 PNG image will work, but if you have an alpha channel on in, it will have transparency.<br />
''<nowiki>http://</nowiki><your IP or domain>/mumble/ shows the list of users in your Mumble server.<br />
<br />
Mumble v1.1.6-x86 for Debian Stable ('Etch', 4.0r5) is available at http://Vocis.K1T.NET/<br />
<br />
=== Ubuntu ===<br />
<br />
==== Official Repository ====<br />
<br />
'''This is the easy way, but you won't always get the latest version.'''<br />
<br />
Ubuntu Hardy Heron (8.04) includes the Mumble 1.1.x series in it's official repository. It's cloned from Debian testing before every Ubuntu release, so while it will lag slightly behind, it won't be by much. Just follow the directions for installing under Debian.<br />
<br />
==== PPA Repository ====<br />
<br />
'''This is a bit more to type, but should always be up-to-date.'''<br />
<br />
As the packages in the official Ubuntu repository aren't always up-to-date, you can add an external PPA repository to your package manager. It should always include the newest stable version of Mumble and Murmur for i386 and amd64 architectures.<br />
<br />
You will have to manually add the repositories for the PPA repository. Go to a command prompt and type <br />
sudo gedit /etc/apt/sources.list<br />
then add the following two lines to the bottom of the file<br />
deb http://ppa.launchpad.net/slicer/ubuntu hardy main<br />
deb-src http://ppa.launchpad.net/slicer/ubuntu hardy main<br />
sudo aptitude update <br />
(replace ''hardy'' with ''gutsy'' or ''intrepid'' if you are on those distributions)<br />
<br />
Afterwards you can use the same command as for installing under Debian (see above).<br />
<br />
More information about the PPA repository can be found at [https://edge.launchpad.net/~slicer/+archive Launchpad]<br />
<br />
===RPM-based distributions===<br />
Fedora, openSUSE, PCLinuxOS, etc. are RPM-based distributions. If their own official package repository doesn't have an up to date version or even no version at all of Mumble, then have a look at openSUSE's Build Service (http://software.opensuse.org). <br />
<br />
There you can find many different RPM-builds for different distributions and architectures of Mumble. '''Note''' that these packages are not officially supported, but it should work. <br />
<br />
Follow this link to see search results for "mumble": http://software.opensuse.org/search?q=mumble<br />
<br />
Often you can install it with the RPM tool of your distribution or by typing (as root):<br />
rpm -i mumble-1.1.7-i386.rpm<br />
<br />
<br />
<br />
===Gentoo===<br />
Depending on what other features you want compiled into it, check up on the possible USE-flags: http://www.gentoo-portage.com/media-sound/mumble/USE#ptabs<br />
For most users it's useful to use the USE-flags alsa, dbus and speech - so we go with it.<br />
It's well possible that the Mumble ebuild is "masked". Here, we make sure it will install anyways.<br />
Become root and do:<br />
echo media-sound/mumble alsa dbus speech >> /etc/portage/package.use<br />
echo media-sound/mumble ~x86 >> /etc/portage/package.keywords<br />
emerge -av mumble<br />
That should do the magic. If something fails though, check up on [[BuildingLinux]]<br />
<br />
===ArchLinux===<br />
A stable PKGBUILD is avalaible in the [http://aur.archlinux.org/packages.php?do_Details=1&ID=10221&K=mumble AUR]. Download the tarball and then run:<br />
tar xzfv mumble*.tar.gz<br />
cd mumble*<br />
makepkg<br />
<br />
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:<br />
<br />
pacman -S alsa-lib qt4 libxevie sqlite3 boost<br />
<br />
Finally, install the package:<br />
<br />
pacman -A mumble-1.0.0-1.pkg.tar.gz<br />
<br />
Of course, replace the package name as appropriate.<br />
<br />
If you want to test a SVN Snapshoth, use this [http://aur.archlinux.org/packages.php?ID=23369 PKGBUILD] in the [http://aur.archlinux.org/packages.php?ID=23369 AUR]. Use [http://wiki.archlinux.org/index.php/Yaourt Yaourt] or the instructions above.<br />
<br />
==Mac OS X==<br />
<br />
Precompiled Mac OS X universal binaries are available from the [http://sourceforge.net/project/showfiles.php?group_id=147372 SourceForge downloads page].<br />
<br />
You can also build it from source yourself if you wish. See [[BuildingMacOsX]] for more information.<br />
<br />
==Snapshots==<br />
<br />
If you want to get the latest snapshots for Mumble and Murmur, you can find those [http://mumble.info/snapshot/ here]. These include the latest builds of Mumble and Murmur for Windows, and static builds of Murmur for Linux.<br />
<br />
=Post-installation tips=<br />
==Common tips==<br />
===Initializing/Resetting Murmur password===<br />
Type:<br />
murmur -supw <password><br />
That will change the password for SuperUser, a special user that has all rights.<br />
If you want to reset the entire database, just delete murmur.sqlite and the recreate it with the command above.<br />
<br />
==Windows==<br />
===Text-to-Speech===<br />
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 [http://www.nextup.com NextUp]).<br />
<br />
===Creating a server connection shortcut===<br />
You can right click on your desktop and choose "New" and pick "Shortcut" from the sub-menu.<br />
In the box that says "Type the location of the item" put "mumble://username:password@servername/channel"<br />
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. <br />
<br />
===It complains about mumble_ol.dll / Problems with Overlay===<br />
If you are running XP you will need to update it to SP2.<br />
<br />
=== Murmur dies when I log out! How can I get Murmur to stay on all the time? ===<br />
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.<br />
<br />
Some references you'll see int his write-up:<br />
<br />
instsrv.exe - A program that adds services to the Windows registry.<br />
<br />
srvany.exe - A program that allows any Windows application and some Windows 16-bit applications to run as a service.<br />
<br />
'''The HOW-TO'''<br />
<br />
Step 1: Gain Administrator access on the machine running Murmur.<br />
<br />
Step 2: Download and install the following collection of tools from Microsoft to the default directory (C:\Program Files\Windows Resource Kits):<br />
<br />
[http://www.microsoft.com/downloads/details.aspx?FamilyID=9d467a69-57ff-4ae7-96ee-b18c4790cffd&displaylang=en Windows 2003 Server Resource Kit].<br />
<br />
Step 3: Open a command console (Start >> Accessories >> Command Prompt).<br />
<br />
Step 4: If you have installed to the default directory, type the following:<br />
<br />
"C:\Program Files\Windows Resource Kits\Tools\instsrv.exe" "Murmur" "C:\Program Files\Windows Resource Kits\Tools\srvany.exe"<br />
<br />
The result of this step is a new service in the Services console (Start >> Control Panel >> Administrative Tools >> Services).<br />
<br />
'''Be sure to close the Services console before proceeding.'''<br />
<br />
Step 5: Open the registry editor (Start >> Run and enter "regedit") and navigate to the following key:<br />
<br />
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Murmur Demo<br />
<br />
<br />
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.<br />
<br />
Step 7: Name this new key "Parameters"<br />
<br />
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.<br />
<br />
Step 9: Name this new String value "Application".<br />
<br />
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.<br />
<br />
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.<br />
<br />
Step 11: Close Regedit<br />
<br />
Step 12: Open the Services console. Navigate to your service, and right click it and select Properties.<br />
<br />
Step 13: Make sure the Startup Type value is Automatic, and then press the Start button.<br />
<br />
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.<br />
<br />
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.<br />
<br />
If your server did not start, recheck your settings. Most problems are related to typos in configuration settings.<br />
<br />
==Linux==<br />
===Getting the Shortcuts Suppression to work===<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 />
=Uninstalling=<br />
[[UninstallingMumble | Instructions for completely removing Mumble, including user created settings and entries.]]</div>Haudraufhttps://wiki.mumble.info/index.php?title=Installing_Mumble&diff=2592Installing Mumble2009-02-01T23:34:12Z<p>Haudrauf: /* PCLinuxOS and other RPM based distros */ not needed anymore</p>
<hr />
<div>=Getting and Installing Mumble=<br />
This page shows you directions on how to install Mumble (client) as well as Murmur (server).<br />
<br />
==Windows==<br />
Just head to [http://sourceforge.net/project/showfiles.php?group_id=147372 SourceForge downloads page], get the Windows executable and run it. Follow the installer instructions and you are done.<br />
<br />
Also, you can build Mumble yourself from source as described in [[BuildingWindows]].<br />
<br />
==Linux==<br />
Some Linux distributions already have Mumble packaged so that an easy installation is possible. Check your package manager of your distribution for Mumble. But sometimes those packages are not up to date. So if you want more in-depth information about installing Mumble for Linux read up on [[BuildingLinux]]. Installation from source (svn and tarball) is described there.<br />
<br />
<br />
=== Debian ===<br />
<br />
Debian Testing (lenny) includes the latest official Mumble packages, and is the officially maintained version. New packaging efforts are encouraged to base their file layout and usernames on what is used here, to make third-party packages easier to port. To install:<br />
<br />
'''Client'''<br />
sudo aptitude install mumble<br />
<br />
<br />
'''Server and web applications'''<br />
sudo aptitude install mumble-server mumble-server-web<br />
sudo dpkg-reconfigure mumble-server<br />
<br />
''People who are connected to your Mumble server can go to http://<your IP or domain>/mumble/register.cgi to register with the server through a web interface.<br />
''They can also upload a custom texture that will be displayed in the Mumble game overlay from this page. <br />
''Any 600x60 PNG image will work, but if you have an alpha channel on in, it will have transparency.<br />
''http://<your IP or domain>/mumble/ shows the list of users in your Mumble server.<br />
<br />
v1.1.4-x86 Mumble for Debian Stable ('Etch', 4.0r5) is available at http://Vocis.K1T.NET/<br />
<br />
=== Ubuntu ===<br />
<br />
==== Official Repository ====<br />
<br />
'''This is the easy way, but you won't always get the latest version.'''<br />
<br />
Ubuntu Hardy Heron (8.04) includes the Mumble 1.1.x series in it's official repository. It's cloned from Debian testing before every Ubuntu release, so while it will lag slightly behind, it won't be by much. Just follow the directions for installing under Debian.<br />
<br />
==== PPA Repository ====<br />
<br />
'''This is a bit more to type, but should always be up-to-date.'''<br />
<br />
As the packages in the official Ubuntu repository aren't always up-to-date, you can add an external PPA repository to your package manager. It should always include the newest stable version of Mumble and Murmur for i386 and amd64 architectures.<br />
<br />
You will have to manually add the repositories for the PPA repository. Go to a command prompt and type <br />
sudo gedit /etc/apt/sources.list<br />
then add the following two lines to the bottom of the file<br />
deb http://ppa.launchpad.net/slicer/ubuntu hardy main<br />
deb-src http://ppa.launchpad.net/slicer/ubuntu hardy main<br />
sudo aptitude update <br />
(replace ''hardy'' with ''gutsy'' or ''intrepid'' if you are on those distributions)<br />
<br />
Afterwards you can use the same command as for installing under Debian (see above).<br />
<br />
More information about the PPA repository can be found at [https://edge.launchpad.net/~slicer/+archive Launchpad]<br />
<br />
===RPM-based distributions===<br />
Fedora, openSUSE, PCLinuxOS, etc. are RPM-based distributions. If their own official package repository doesn't have an up to date version or even no version at all of Mumble, then have a look at openSUSE's Build Service (http://software.opensuse.org). <br />
<br />
There you can find many different RPM-builds for different distributions and architectures of Mumble. '''Note''' that these packages are not officially supported, but it should work. <br />
<br />
Follow this link to see search results for "mumble": http://software.opensuse.org/search?q=mumble<br />
<br />
Often you can install it with the RPM tool of your distribution or by typing (as root):<br />
rpm -i mumble-1.1.7-i386.rpm<br />
<br />
<br />
<br />
===Gentoo===<br />
Depending on what other features you want compiled into it, check up on the possible USE-flags: http://www.gentoo-portage.com/media-sound/mumble/USE#ptabs<br />
For most users it's useful to use the USE-flags alsa, dbus and speech - so we go with it.<br />
It's well possible that the Mumble ebuild is "masked". Here, we make sure it will install anyways.<br />
Become root and do:<br />
echo media-sound/mumble alsa dbus speech >> /etc/portage/package.use<br />
echo media-sound/mumble ~x86 >> /etc/portage/package.keywords<br />
emerge -av mumble<br />
That should do the magic. If something fails though, check up on [[BuildingLinux]]<br />
<br />
===ArchLinux===<br />
A stable PKGBUILD is avalaible in the [http://aur.archlinux.org/packages.php?do_Details=1&ID=10221&K=mumble AUR]. Download the tarball and then run:<br />
tar xzfv mumble*.tar.gz<br />
cd mumble*<br />
makepkg<br />
<br />
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:<br />
<br />
pacman -S alsa-lib qt4 libxevie sqlite3 boost<br />
<br />
Finally, install the package:<br />
<br />
pacman -A mumble-1.0.0-1.pkg.tar.gz<br />
<br />
Of course, replace the package name as appropriate.<br />
<br />
If you want to test a SVN Snapshoth, use this [http://aur.archlinux.org/packages.php?ID=23369 PKGBUILD] in the [http://aur.archlinux.org/packages.php?ID=23369 AUR]. Use [http://wiki.archlinux.org/index.php/Yaourt Yaourt] or the instructions above.<br />
<br />
==Mac OS X==<br />
<br />
Precompiled Mac OS X universal binaries are available from the [http://sourceforge.net/project/showfiles.php?group_id=147372 SourceForge downloads page].<br />
<br />
You can also build it from source yourself if you wish. See [[BuildingMacOsX]] for more information.<br />
<br />
==Snapshots==<br />
<br />
If you want to get the latest snapshots for Mumble and Murmur, you can find those [http://mumble.info/snapshot/ here]. These include the latest builds of Mumble and Murmur for Windows, and static builds of Murmur for Linux.<br />
<br />
=Post-installation tips=<br />
==Common tips==<br />
===Initializing/Resetting Murmur password===<br />
Type:<br />
murmur -supw <password><br />
That will change the password for SuperUser, a special user that has all rights.<br />
If you want to reset the entire database, just delete murmur.sqlite and the recreate it with the command above.<br />
<br />
==Windows==<br />
===Text-to-Speech===<br />
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 [http://www.nextup.com NextUp]).<br />
<br />
===Creating a server connection shortcut===<br />
You can right click on your desktop and choose "New" and pick "Shortcut" from the sub-menu.<br />
In the box that says "Type the location of the item" put "mumble://username:password@servername/channel"<br />
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. <br />
<br />
===It complains about mumble_ol.dll / Problems with Overlay===<br />
If you are running XP you will need to update it to SP2.<br />
<br />
=== Murmur dies when I log out! How can I get Murmur to stay on all the time? ===<br />
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.<br />
<br />
Some references you'll see int his write-up:<br />
<br />
instsrv.exe - A program that adds services to the Windows registry.<br />
<br />
srvany.exe - A program that allows any Windows application and some Windows 16-bit applications to run as a service.<br />
<br />
'''The HOW-TO'''<br />
<br />
Step 1: Gain Administrator access on the machine running Murmur.<br />
<br />
Step 2: Download and install the following collection of tools from Microsoft to the default directory (C:\Program Files\Windows Resource Kits):<br />
<br />
[http://www.microsoft.com/downloads/details.aspx?FamilyID=9d467a69-57ff-4ae7-96ee-b18c4790cffd&displaylang=en Windows 2003 Server Resource Kit].<br />
<br />
Step 3: Open a command console (Start >> Accessories >> Command Prompt).<br />
<br />
Step 4: If you have installed to the default directory, type the following:<br />
<br />
"C:\Program Files\Windows Resource Kits\Tools\instsrv.exe" "Murmur" "C:\Program Files\Windows Resource Kits\Tools\srvany.exe"<br />
<br />
The result of this step is a new service in the Services console (Start >> Control Panel >> Administrative Tools >> Services).<br />
<br />
'''Be sure to close the Services console before proceeding.'''<br />
<br />
Step 5: Open the registry editor (Start >> Run and enter "regedit") and navigate to the following key:<br />
<br />
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Murmur Demo<br />
<br />
<br />
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.<br />
<br />
Step 7: Name this new key "Parameters"<br />
<br />
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.<br />
<br />
Step 9: Name this new String value "Application".<br />
<br />
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.<br />
<br />
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.<br />
<br />
Step 11: Close Regedit<br />
<br />
Step 12: Open the Services console. Navigate to your service, and right click it and select Properties.<br />
<br />
Step 13: Make sure the Startup Type value is Automatic, and then press the Start button.<br />
<br />
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.<br />
<br />
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.<br />
<br />
If your server did not start, recheck your settings. Most problems are related to typos in configuration settings.<br />
<br />
==Linux==<br />
===Getting the Shortcuts Suppression to work===<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 />
=Uninstalling=<br />
[[UninstallingMumble | Instructions for completely removing Mumble, including user created settings and entries.]]</div>Haudraufhttps://wiki.mumble.info/index.php?title=Installing_Mumble&diff=2591Installing Mumble2009-02-01T23:33:37Z<p>Haudrauf: /* Fedora */</p>
<hr />
<div>=Getting and Installing Mumble=<br />
This page shows you directions on how to install Mumble (client) as well as Murmur (server).<br />
<br />
==Windows==<br />
Just head to [http://sourceforge.net/project/showfiles.php?group_id=147372 SourceForge downloads page], get the Windows executable and run it. Follow the installer instructions and you are done.<br />
<br />
Also, you can build Mumble yourself from source as described in [[BuildingWindows]].<br />
<br />
==Linux==<br />
Some Linux distributions already have Mumble packaged so that an easy installation is possible. Check your package manager of your distribution for Mumble. But sometimes those packages are not up to date. So if you want more in-depth information about installing Mumble for Linux read up on [[BuildingLinux]]. Installation from source (svn and tarball) is described there.<br />
<br />
<br />
=== Debian ===<br />
<br />
Debian Testing (lenny) includes the latest official Mumble packages, and is the officially maintained version. New packaging efforts are encouraged to base their file layout and usernames on what is used here, to make third-party packages easier to port. To install:<br />
<br />
'''Client'''<br />
sudo aptitude install mumble<br />
<br />
<br />
'''Server and web applications'''<br />
sudo aptitude install mumble-server mumble-server-web<br />
sudo dpkg-reconfigure mumble-server<br />
<br />
''People who are connected to your Mumble server can go to http://<your IP or domain>/mumble/register.cgi to register with the server through a web interface.<br />
''They can also upload a custom texture that will be displayed in the Mumble game overlay from this page. <br />
''Any 600x60 PNG image will work, but if you have an alpha channel on in, it will have transparency.<br />
''http://<your IP or domain>/mumble/ shows the list of users in your Mumble server.<br />
<br />
v1.1.4-x86 Mumble for Debian Stable ('Etch', 4.0r5) is available at http://Vocis.K1T.NET/<br />
<br />
=== Ubuntu ===<br />
<br />
==== Official Repository ====<br />
<br />
'''This is the easy way, but you won't always get the latest version.'''<br />
<br />
Ubuntu Hardy Heron (8.04) includes the Mumble 1.1.x series in it's official repository. It's cloned from Debian testing before every Ubuntu release, so while it will lag slightly behind, it won't be by much. Just follow the directions for installing under Debian.<br />
<br />
==== PPA Repository ====<br />
<br />
'''This is a bit more to type, but should always be up-to-date.'''<br />
<br />
As the packages in the official Ubuntu repository aren't always up-to-date, you can add an external PPA repository to your package manager. It should always include the newest stable version of Mumble and Murmur for i386 and amd64 architectures.<br />
<br />
You will have to manually add the repositories for the PPA repository. Go to a command prompt and type <br />
sudo gedit /etc/apt/sources.list<br />
then add the following two lines to the bottom of the file<br />
deb http://ppa.launchpad.net/slicer/ubuntu hardy main<br />
deb-src http://ppa.launchpad.net/slicer/ubuntu hardy main<br />
sudo aptitude update <br />
(replace ''hardy'' with ''gutsy'' or ''intrepid'' if you are on those distributions)<br />
<br />
Afterwards you can use the same command as for installing under Debian (see above).<br />
<br />
More information about the PPA repository can be found at [https://edge.launchpad.net/~slicer/+archive Launchpad]<br />
<br />
===RPM-based distributions===<br />
Fedora, openSUSE, PCLinuxOS, etc. are RPM-based distributions. If their own official package repository doesn't have an up to date version or even no version at all of Mumble, then have a look at openSUSE's Build Service (http://software.opensuse.org). <br />
<br />
There you can find many different RPM-builds for different distributions and architectures of Mumble. '''Note''' that these packages are not officially supported, but it should work. <br />
<br />
Follow this link to see search results for "mumble": http://software.opensuse.org/search?q=mumble<br />
<br />
Often you can install it with the RPM tool of your distribution or by typing (as root):<br />
rpm -i mumble-1.1.7-i386.rpm<br />
<br />
===PCLinuxOS and other RPM based distros===<br />
You can find a rpm package in the [http://sourceforge.net/forum/forum.php?thread_id=1782689&forum_id=492606 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):<br />
<br />
rpm -i mumble-1.0.0-2.i386.rpm<br />
<br />
===Gentoo===<br />
Depending on what other features you want compiled into it, check up on the possible USE-flags: http://www.gentoo-portage.com/media-sound/mumble/USE#ptabs<br />
For most users it's useful to use the USE-flags alsa, dbus and speech - so we go with it.<br />
It's well possible that the Mumble ebuild is "masked". Here, we make sure it will install anyways.<br />
Become root and do:<br />
echo media-sound/mumble alsa dbus speech >> /etc/portage/package.use<br />
echo media-sound/mumble ~x86 >> /etc/portage/package.keywords<br />
emerge -av mumble<br />
That should do the magic. If something fails though, check up on [[BuildingLinux]]<br />
<br />
===ArchLinux===<br />
A stable PKGBUILD is avalaible in the [http://aur.archlinux.org/packages.php?do_Details=1&ID=10221&K=mumble AUR]. Download the tarball and then run:<br />
tar xzfv mumble*.tar.gz<br />
cd mumble*<br />
makepkg<br />
<br />
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:<br />
<br />
pacman -S alsa-lib qt4 libxevie sqlite3 boost<br />
<br />
Finally, install the package:<br />
<br />
pacman -A mumble-1.0.0-1.pkg.tar.gz<br />
<br />
Of course, replace the package name as appropriate.<br />
<br />
If you want to test a SVN Snapshoth, use this [http://aur.archlinux.org/packages.php?ID=23369 PKGBUILD] in the [http://aur.archlinux.org/packages.php?ID=23369 AUR]. Use [http://wiki.archlinux.org/index.php/Yaourt Yaourt] or the instructions above.<br />
<br />
==Mac OS X==<br />
<br />
Precompiled Mac OS X universal binaries are available from the [http://sourceforge.net/project/showfiles.php?group_id=147372 SourceForge downloads page].<br />
<br />
You can also build it from source yourself if you wish. See [[BuildingMacOsX]] for more information.<br />
<br />
==Snapshots==<br />
<br />
If you want to get the latest snapshots for Mumble and Murmur, you can find those [http://mumble.info/snapshot/ here]. These include the latest builds of Mumble and Murmur for Windows, and static builds of Murmur for Linux.<br />
<br />
=Post-installation tips=<br />
==Common tips==<br />
===Initializing/Resetting Murmur password===<br />
Type:<br />
murmur -supw <password><br />
That will change the password for SuperUser, a special user that has all rights.<br />
If you want to reset the entire database, just delete murmur.sqlite and the recreate it with the command above.<br />
<br />
==Windows==<br />
===Text-to-Speech===<br />
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 [http://www.nextup.com NextUp]).<br />
<br />
===Creating a server connection shortcut===<br />
You can right click on your desktop and choose "New" and pick "Shortcut" from the sub-menu.<br />
In the box that says "Type the location of the item" put "mumble://username:password@servername/channel"<br />
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. <br />
<br />
===It complains about mumble_ol.dll / Problems with Overlay===<br />
If you are running XP you will need to update it to SP2.<br />
<br />
=== Murmur dies when I log out! How can I get Murmur to stay on all the time? ===<br />
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.<br />
<br />
Some references you'll see int his write-up:<br />
<br />
instsrv.exe - A program that adds services to the Windows registry.<br />
<br />
srvany.exe - A program that allows any Windows application and some Windows 16-bit applications to run as a service.<br />
<br />
'''The HOW-TO'''<br />
<br />
Step 1: Gain Administrator access on the machine running Murmur.<br />
<br />
Step 2: Download and install the following collection of tools from Microsoft to the default directory (C:\Program Files\Windows Resource Kits):<br />
<br />
[http://www.microsoft.com/downloads/details.aspx?FamilyID=9d467a69-57ff-4ae7-96ee-b18c4790cffd&displaylang=en Windows 2003 Server Resource Kit].<br />
<br />
Step 3: Open a command console (Start >> Accessories >> Command Prompt).<br />
<br />
Step 4: If you have installed to the default directory, type the following:<br />
<br />
"C:\Program Files\Windows Resource Kits\Tools\instsrv.exe" "Murmur" "C:\Program Files\Windows Resource Kits\Tools\srvany.exe"<br />
<br />
The result of this step is a new service in the Services console (Start >> Control Panel >> Administrative Tools >> Services).<br />
<br />
'''Be sure to close the Services console before proceeding.'''<br />
<br />
Step 5: Open the registry editor (Start >> Run and enter "regedit") and navigate to the following key:<br />
<br />
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Murmur Demo<br />
<br />
<br />
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.<br />
<br />
Step 7: Name this new key "Parameters"<br />
<br />
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.<br />
<br />
Step 9: Name this new String value "Application".<br />
<br />
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.<br />
<br />
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.<br />
<br />
Step 11: Close Regedit<br />
<br />
Step 12: Open the Services console. Navigate to your service, and right click it and select Properties.<br />
<br />
Step 13: Make sure the Startup Type value is Automatic, and then press the Start button.<br />
<br />
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.<br />
<br />
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.<br />
<br />
If your server did not start, recheck your settings. Most problems are related to typos in configuration settings.<br />
<br />
==Linux==<br />
===Getting the Shortcuts Suppression to work===<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 />
=Uninstalling=<br />
[[UninstallingMumble | Instructions for completely removing Mumble, including user created settings and entries.]]</div>Haudraufhttps://wiki.mumble.info/index.php?title=Installing_Mumble&diff=2590Installing Mumble2009-02-01T23:27:27Z<p>Haudrauf: /* Fedora */</p>
<hr />
<div>=Getting and Installing Mumble=<br />
This page shows you directions on how to install Mumble (client) as well as Murmur (server).<br />
<br />
==Windows==<br />
Just head to [http://sourceforge.net/project/showfiles.php?group_id=147372 SourceForge downloads page], get the Windows executable and run it. Follow the installer instructions and you are done.<br />
<br />
Also, you can build Mumble yourself from source as described in [[BuildingWindows]].<br />
<br />
==Linux==<br />
Some Linux distributions already have Mumble packaged so that an easy installation is possible. Check your package manager of your distribution for Mumble. But sometimes those packages are not up to date. So if you want more in-depth information about installing Mumble for Linux read up on [[BuildingLinux]]. Installation from source (svn and tarball) is described there.<br />
<br />
<br />
=== Debian ===<br />
<br />
Debian Testing (lenny) includes the latest official Mumble packages, and is the officially maintained version. New packaging efforts are encouraged to base their file layout and usernames on what is used here, to make third-party packages easier to port. To install:<br />
<br />
'''Client'''<br />
sudo aptitude install mumble<br />
<br />
<br />
'''Server and web applications'''<br />
sudo aptitude install mumble-server mumble-server-web<br />
sudo dpkg-reconfigure mumble-server<br />
<br />
''People who are connected to your Mumble server can go to http://<your IP or domain>/mumble/register.cgi to register with the server through a web interface.<br />
''They can also upload a custom texture that will be displayed in the Mumble game overlay from this page. <br />
''Any 600x60 PNG image will work, but if you have an alpha channel on in, it will have transparency.<br />
''http://<your IP or domain>/mumble/ shows the list of users in your Mumble server.<br />
<br />
v1.1.4-x86 Mumble for Debian Stable ('Etch', 4.0r5) is available at http://Vocis.K1T.NET/<br />
<br />
=== Ubuntu ===<br />
<br />
==== Official Repository ====<br />
<br />
'''This is the easy way, but you won't always get the latest version.'''<br />
<br />
Ubuntu Hardy Heron (8.04) includes the Mumble 1.1.x series in it's official repository. It's cloned from Debian testing before every Ubuntu release, so while it will lag slightly behind, it won't be by much. Just follow the directions for installing under Debian.<br />
<br />
==== PPA Repository ====<br />
<br />
'''This is a bit more to type, but should always be up-to-date.'''<br />
<br />
As the packages in the official Ubuntu repository aren't always up-to-date, you can add an external PPA repository to your package manager. It should always include the newest stable version of Mumble and Murmur for i386 and amd64 architectures.<br />
<br />
You will have to manually add the repositories for the PPA repository. Go to a command prompt and type <br />
sudo gedit /etc/apt/sources.list<br />
then add the following two lines to the bottom of the file<br />
deb http://ppa.launchpad.net/slicer/ubuntu hardy main<br />
deb-src http://ppa.launchpad.net/slicer/ubuntu hardy main<br />
sudo aptitude update <br />
(replace ''hardy'' with ''gutsy'' or ''intrepid'' if you are on those distributions)<br />
<br />
Afterwards you can use the same command as for installing under Debian (see above).<br />
<br />
More information about the PPA repository can be found at [https://edge.launchpad.net/~slicer/+archive Launchpad]<br />
<br />
===Fedora===<br />
You can find many different RPM-builds for different distributions and architectures in the openSUSE Build Service (http://software.opensuse.org). <br />
<br />
Follow this link to see search results for "mumble": http://software.opensuse.org/search?q=mumble<br />
<br />
===PCLinuxOS and other RPM based distros===<br />
You can find a rpm package in the [http://sourceforge.net/forum/forum.php?thread_id=1782689&forum_id=492606 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):<br />
<br />
rpm -i mumble-1.0.0-2.i386.rpm<br />
<br />
===Gentoo===<br />
Depending on what other features you want compiled into it, check up on the possible USE-flags: http://www.gentoo-portage.com/media-sound/mumble/USE#ptabs<br />
For most users it's useful to use the USE-flags alsa, dbus and speech - so we go with it.<br />
It's well possible that the Mumble ebuild is "masked". Here, we make sure it will install anyways.<br />
Become root and do:<br />
echo media-sound/mumble alsa dbus speech >> /etc/portage/package.use<br />
echo media-sound/mumble ~x86 >> /etc/portage/package.keywords<br />
emerge -av mumble<br />
That should do the magic. If something fails though, check up on [[BuildingLinux]]<br />
<br />
===ArchLinux===<br />
A stable PKGBUILD is avalaible in the [http://aur.archlinux.org/packages.php?do_Details=1&ID=10221&K=mumble AUR]. Download the tarball and then run:<br />
tar xzfv mumble*.tar.gz<br />
cd mumble*<br />
makepkg<br />
<br />
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:<br />
<br />
pacman -S alsa-lib qt4 libxevie sqlite3 boost<br />
<br />
Finally, install the package:<br />
<br />
pacman -A mumble-1.0.0-1.pkg.tar.gz<br />
<br />
Of course, replace the package name as appropriate.<br />
<br />
If you want to test a SVN Snapshoth, use this [http://aur.archlinux.org/packages.php?ID=23369 PKGBUILD] in the [http://aur.archlinux.org/packages.php?ID=23369 AUR]. Use [http://wiki.archlinux.org/index.php/Yaourt Yaourt] or the instructions above.<br />
<br />
==Mac OS X==<br />
<br />
Precompiled Mac OS X universal binaries are available from the [http://sourceforge.net/project/showfiles.php?group_id=147372 SourceForge downloads page].<br />
<br />
You can also build it from source yourself if you wish. See [[BuildingMacOsX]] for more information.<br />
<br />
==Snapshots==<br />
<br />
If you want to get the latest snapshots for Mumble and Murmur, you can find those [http://mumble.info/snapshot/ here]. These include the latest builds of Mumble and Murmur for Windows, and static builds of Murmur for Linux.<br />
<br />
=Post-installation tips=<br />
==Common tips==<br />
===Initializing/Resetting Murmur password===<br />
Type:<br />
murmur -supw <password><br />
That will change the password for SuperUser, a special user that has all rights.<br />
If you want to reset the entire database, just delete murmur.sqlite and the recreate it with the command above.<br />
<br />
==Windows==<br />
===Text-to-Speech===<br />
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 [http://www.nextup.com NextUp]).<br />
<br />
===Creating a server connection shortcut===<br />
You can right click on your desktop and choose "New" and pick "Shortcut" from the sub-menu.<br />
In the box that says "Type the location of the item" put "mumble://username:password@servername/channel"<br />
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. <br />
<br />
===It complains about mumble_ol.dll / Problems with Overlay===<br />
If you are running XP you will need to update it to SP2.<br />
<br />
=== Murmur dies when I log out! How can I get Murmur to stay on all the time? ===<br />
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.<br />
<br />
Some references you'll see int his write-up:<br />
<br />
instsrv.exe - A program that adds services to the Windows registry.<br />
<br />
srvany.exe - A program that allows any Windows application and some Windows 16-bit applications to run as a service.<br />
<br />
'''The HOW-TO'''<br />
<br />
Step 1: Gain Administrator access on the machine running Murmur.<br />
<br />
Step 2: Download and install the following collection of tools from Microsoft to the default directory (C:\Program Files\Windows Resource Kits):<br />
<br />
[http://www.microsoft.com/downloads/details.aspx?FamilyID=9d467a69-57ff-4ae7-96ee-b18c4790cffd&displaylang=en Windows 2003 Server Resource Kit].<br />
<br />
Step 3: Open a command console (Start >> Accessories >> Command Prompt).<br />
<br />
Step 4: If you have installed to the default directory, type the following:<br />
<br />
"C:\Program Files\Windows Resource Kits\Tools\instsrv.exe" "Murmur" "C:\Program Files\Windows Resource Kits\Tools\srvany.exe"<br />
<br />
The result of this step is a new service in the Services console (Start >> Control Panel >> Administrative Tools >> Services).<br />
<br />
'''Be sure to close the Services console before proceeding.'''<br />
<br />
Step 5: Open the registry editor (Start >> Run and enter "regedit") and navigate to the following key:<br />
<br />
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Murmur Demo<br />
<br />
<br />
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.<br />
<br />
Step 7: Name this new key "Parameters"<br />
<br />
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.<br />
<br />
Step 9: Name this new String value "Application".<br />
<br />
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.<br />
<br />
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.<br />
<br />
Step 11: Close Regedit<br />
<br />
Step 12: Open the Services console. Navigate to your service, and right click it and select Properties.<br />
<br />
Step 13: Make sure the Startup Type value is Automatic, and then press the Start button.<br />
<br />
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.<br />
<br />
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.<br />
<br />
If your server did not start, recheck your settings. Most problems are related to typos in configuration settings.<br />
<br />
==Linux==<br />
===Getting the Shortcuts Suppression to work===<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 />
=Uninstalling=<br />
[[UninstallingMumble | Instructions for completely removing Mumble, including user created settings and entries.]]</div>Haudraufhttps://wiki.mumble.info/index.php?title=Installing_Mumble&diff=2589Installing Mumble2009-02-01T23:25:23Z<p>Haudrauf: /* Fedora */</p>
<hr />
<div>=Getting and Installing Mumble=<br />
This page shows you directions on how to install Mumble (client) as well as Murmur (server).<br />
<br />
==Windows==<br />
Just head to [http://sourceforge.net/project/showfiles.php?group_id=147372 SourceForge downloads page], get the Windows executable and run it. Follow the installer instructions and you are done.<br />
<br />
Also, you can build Mumble yourself from source as described in [[BuildingWindows]].<br />
<br />
==Linux==<br />
Some Linux distributions already have Mumble packaged so that an easy installation is possible. Check your package manager of your distribution for Mumble. But sometimes those packages are not up to date. So if you want more in-depth information about installing Mumble for Linux read up on [[BuildingLinux]]. Installation from source (svn and tarball) is described there.<br />
<br />
<br />
=== Debian ===<br />
<br />
Debian Testing (lenny) includes the latest official Mumble packages, and is the officially maintained version. New packaging efforts are encouraged to base their file layout and usernames on what is used here, to make third-party packages easier to port. To install:<br />
<br />
'''Client'''<br />
sudo aptitude install mumble<br />
<br />
<br />
'''Server and web applications'''<br />
sudo aptitude install mumble-server mumble-server-web<br />
sudo dpkg-reconfigure mumble-server<br />
<br />
''People who are connected to your Mumble server can go to http://<your IP or domain>/mumble/register.cgi to register with the server through a web interface.<br />
''They can also upload a custom texture that will be displayed in the Mumble game overlay from this page. <br />
''Any 600x60 PNG image will work, but if you have an alpha channel on in, it will have transparency.<br />
''http://<your IP or domain>/mumble/ shows the list of users in your Mumble server.<br />
<br />
v1.1.4-x86 Mumble for Debian Stable ('Etch', 4.0r5) is available at http://Vocis.K1T.NET/<br />
<br />
=== Ubuntu ===<br />
<br />
==== Official Repository ====<br />
<br />
'''This is the easy way, but you won't always get the latest version.'''<br />
<br />
Ubuntu Hardy Heron (8.04) includes the Mumble 1.1.x series in it's official repository. It's cloned from Debian testing before every Ubuntu release, so while it will lag slightly behind, it won't be by much. Just follow the directions for installing under Debian.<br />
<br />
==== PPA Repository ====<br />
<br />
'''This is a bit more to type, but should always be up-to-date.'''<br />
<br />
As the packages in the official Ubuntu repository aren't always up-to-date, you can add an external PPA repository to your package manager. It should always include the newest stable version of Mumble and Murmur for i386 and amd64 architectures.<br />
<br />
You will have to manually add the repositories for the PPA repository. Go to a command prompt and type <br />
sudo gedit /etc/apt/sources.list<br />
then add the following two lines to the bottom of the file<br />
deb http://ppa.launchpad.net/slicer/ubuntu hardy main<br />
deb-src http://ppa.launchpad.net/slicer/ubuntu hardy main<br />
sudo aptitude update <br />
(replace ''hardy'' with ''gutsy'' or ''intrepid'' if you are on those distributions)<br />
<br />
Afterwards you can use the same command as for installing under Debian (see above).<br />
<br />
More information about the PPA repository can be found at [https://edge.launchpad.net/~slicer/+archive Launchpad]<br />
<br />
===Fedora===<br />
You can find many different RPM-builds for different distributions and architectures in the [openSUSE Build Service database|http://software.opensuse.org]. Follow this link to see search results for "mumble": http://software.opensuse.org/search?q=mumble<br />
<br />
===PCLinuxOS and other RPM based distros===<br />
You can find a rpm package in the [http://sourceforge.net/forum/forum.php?thread_id=1782689&forum_id=492606 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):<br />
<br />
rpm -i mumble-1.0.0-2.i386.rpm<br />
<br />
===Gentoo===<br />
Depending on what other features you want compiled into it, check up on the possible USE-flags: http://www.gentoo-portage.com/media-sound/mumble/USE#ptabs<br />
For most users it's useful to use the USE-flags alsa, dbus and speech - so we go with it.<br />
It's well possible that the Mumble ebuild is "masked". Here, we make sure it will install anyways.<br />
Become root and do:<br />
echo media-sound/mumble alsa dbus speech >> /etc/portage/package.use<br />
echo media-sound/mumble ~x86 >> /etc/portage/package.keywords<br />
emerge -av mumble<br />
That should do the magic. If something fails though, check up on [[BuildingLinux]]<br />
<br />
===ArchLinux===<br />
A stable PKGBUILD is avalaible in the [http://aur.archlinux.org/packages.php?do_Details=1&ID=10221&K=mumble AUR]. Download the tarball and then run:<br />
tar xzfv mumble*.tar.gz<br />
cd mumble*<br />
makepkg<br />
<br />
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:<br />
<br />
pacman -S alsa-lib qt4 libxevie sqlite3 boost<br />
<br />
Finally, install the package:<br />
<br />
pacman -A mumble-1.0.0-1.pkg.tar.gz<br />
<br />
Of course, replace the package name as appropriate.<br />
<br />
If you want to test a SVN Snapshoth, use this [http://aur.archlinux.org/packages.php?ID=23369 PKGBUILD] in the [http://aur.archlinux.org/packages.php?ID=23369 AUR]. Use [http://wiki.archlinux.org/index.php/Yaourt Yaourt] or the instructions above.<br />
<br />
==Mac OS X==<br />
<br />
Precompiled Mac OS X universal binaries are available from the [http://sourceforge.net/project/showfiles.php?group_id=147372 SourceForge downloads page].<br />
<br />
You can also build it from source yourself if you wish. See [[BuildingMacOsX]] for more information.<br />
<br />
==Snapshots==<br />
<br />
If you want to get the latest snapshots for Mumble and Murmur, you can find those [http://mumble.info/snapshot/ here]. These include the latest builds of Mumble and Murmur for Windows, and static builds of Murmur for Linux.<br />
<br />
=Post-installation tips=<br />
==Common tips==<br />
===Initializing/Resetting Murmur password===<br />
Type:<br />
murmur -supw <password><br />
That will change the password for SuperUser, a special user that has all rights.<br />
If you want to reset the entire database, just delete murmur.sqlite and the recreate it with the command above.<br />
<br />
==Windows==<br />
===Text-to-Speech===<br />
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 [http://www.nextup.com NextUp]).<br />
<br />
===Creating a server connection shortcut===<br />
You can right click on your desktop and choose "New" and pick "Shortcut" from the sub-menu.<br />
In the box that says "Type the location of the item" put "mumble://username:password@servername/channel"<br />
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. <br />
<br />
===It complains about mumble_ol.dll / Problems with Overlay===<br />
If you are running XP you will need to update it to SP2.<br />
<br />
=== Murmur dies when I log out! How can I get Murmur to stay on all the time? ===<br />
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.<br />
<br />
Some references you'll see int his write-up:<br />
<br />
instsrv.exe - A program that adds services to the Windows registry.<br />
<br />
srvany.exe - A program that allows any Windows application and some Windows 16-bit applications to run as a service.<br />
<br />
'''The HOW-TO'''<br />
<br />
Step 1: Gain Administrator access on the machine running Murmur.<br />
<br />
Step 2: Download and install the following collection of tools from Microsoft to the default directory (C:\Program Files\Windows Resource Kits):<br />
<br />
[http://www.microsoft.com/downloads/details.aspx?FamilyID=9d467a69-57ff-4ae7-96ee-b18c4790cffd&displaylang=en Windows 2003 Server Resource Kit].<br />
<br />
Step 3: Open a command console (Start >> Accessories >> Command Prompt).<br />
<br />
Step 4: If you have installed to the default directory, type the following:<br />
<br />
"C:\Program Files\Windows Resource Kits\Tools\instsrv.exe" "Murmur" "C:\Program Files\Windows Resource Kits\Tools\srvany.exe"<br />
<br />
The result of this step is a new service in the Services console (Start >> Control Panel >> Administrative Tools >> Services).<br />
<br />
'''Be sure to close the Services console before proceeding.'''<br />
<br />
Step 5: Open the registry editor (Start >> Run and enter "regedit") and navigate to the following key:<br />
<br />
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Murmur Demo<br />
<br />
<br />
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.<br />
<br />
Step 7: Name this new key "Parameters"<br />
<br />
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.<br />
<br />
Step 9: Name this new String value "Application".<br />
<br />
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.<br />
<br />
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.<br />
<br />
Step 11: Close Regedit<br />
<br />
Step 12: Open the Services console. Navigate to your service, and right click it and select Properties.<br />
<br />
Step 13: Make sure the Startup Type value is Automatic, and then press the Start button.<br />
<br />
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.<br />
<br />
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.<br />
<br />
If your server did not start, recheck your settings. Most problems are related to typos in configuration settings.<br />
<br />
==Linux==<br />
===Getting the Shortcuts Suppression to work===<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 />
=Uninstalling=<br />
[[UninstallingMumble | Instructions for completely removing Mumble, including user created settings and entries.]]</div>Haudraufhttps://wiki.mumble.info/index.php?title=Installing_Mumble&diff=2588Installing Mumble2009-02-01T22:02:59Z<p>Haudrauf: /* Debian */</p>
<hr />
<div>=Getting and Installing Mumble=<br />
This page shows you directions on how to install Mumble (client) as well as Murmur (server).<br />
<br />
==Windows==<br />
Just head to [http://sourceforge.net/project/showfiles.php?group_id=147372 SourceForge downloads page], get the Windows executable and run it. Follow the installer instructions and you are done.<br />
<br />
Also, you can build Mumble yourself from source as described in [[BuildingWindows]].<br />
<br />
==Linux==<br />
Some Linux distributions already have Mumble packaged so that an easy installation is possible. Check your package manager of your distribution for Mumble. But sometimes those packages are not up to date. So if you want more in-depth information about installing Mumble for Linux read up on [[BuildingLinux]]. Installation from source (svn and tarball) is described there.<br />
<br />
<br />
=== Debian ===<br />
<br />
Debian Testing (lenny) includes the latest official Mumble packages, and is the officially maintained version. New packaging efforts are encouraged to base their file layout and usernames on what is used here, to make third-party packages easier to port. To install:<br />
<br />
'''Client'''<br />
sudo aptitude install mumble<br />
<br />
<br />
'''Server and web applications'''<br />
sudo aptitude install mumble-server mumble-server-web<br />
sudo dpkg-reconfigure mumble-server<br />
<br />
''People who are connected to your Mumble server can go to http://<your IP or domain>/mumble/register.cgi to register with the server through a web interface.<br />
''They can also upload a custom texture that will be displayed in the Mumble game overlay from this page. <br />
''Any 600x60 PNG image will work, but if you have an alpha channel on in, it will have transparency.<br />
''http://<your IP or domain>/mumble/ shows the list of users in your Mumble server.<br />
<br />
v1.1.4-x86 Mumble for Debian Stable ('Etch', 4.0r5) is available at http://Vocis.K1T.NET/<br />
<br />
=== Ubuntu ===<br />
<br />
==== Official Repository ====<br />
<br />
'''This is the easy way, but you won't always get the latest version.'''<br />
<br />
Ubuntu Hardy Heron (8.04) includes the Mumble 1.1.x series in it's official repository. It's cloned from Debian testing before every Ubuntu release, so while it will lag slightly behind, it won't be by much. Just follow the directions for installing under Debian.<br />
<br />
==== PPA Repository ====<br />
<br />
'''This is a bit more to type, but should always be up-to-date.'''<br />
<br />
As the packages in the official Ubuntu repository aren't always up-to-date, you can add an external PPA repository to your package manager. It should always include the newest stable version of Mumble and Murmur for i386 and amd64 architectures.<br />
<br />
You will have to manually add the repositories for the PPA repository. Go to a command prompt and type <br />
sudo gedit /etc/apt/sources.list<br />
then add the following two lines to the bottom of the file<br />
deb http://ppa.launchpad.net/slicer/ubuntu hardy main<br />
deb-src http://ppa.launchpad.net/slicer/ubuntu hardy main<br />
sudo aptitude update <br />
(replace ''hardy'' with ''gutsy'' or ''intrepid'' if you are on those distributions)<br />
<br />
Afterwards you can use the same command as for installing under Debian (see above).<br />
<br />
More information about the PPA repository can be found at [https://edge.launchpad.net/~slicer/+archive Launchpad]<br />
<br />
===Fedora===<br />
Fedora 7 RPMs: [http://koji.fedoraproject.org/koji/getfile?taskID=227582&name=mumble-1.1.0-1.fc7.i386.rpm 1.1.0 i386] [http://koji.fedoraproject.org/koji/getfile?taskID=227581&name=mumble-1.1.0-1.fc7.x86_64.rpm 1.1.0 x86_64]<br />
Fedora 8 RPMs: [http://koji.fedoraproject.org/koji/getfile?taskID=231652&name=mumble-1.1.0-2.fc8.i386.rpm 1.1.0 i386] [http://koji.fedoraproject.org/koji/getfile?taskID=231651&name=mumble-1.1.0-2.fc8.x86_64.rpm 1.1.0 x86_64]<br />
<br />
===PCLinuxOS and other RPM based distros===<br />
You can find a rpm package in the [http://sourceforge.net/forum/forum.php?thread_id=1782689&forum_id=492606 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):<br />
<br />
rpm -i mumble-1.0.0-2.i386.rpm<br />
<br />
===Gentoo===<br />
Depending on what other features you want compiled into it, check up on the possible USE-flags: http://www.gentoo-portage.com/media-sound/mumble/USE#ptabs<br />
For most users it's useful to use the USE-flags alsa, dbus and speech - so we go with it.<br />
It's well possible that the Mumble ebuild is "masked". Here, we make sure it will install anyways.<br />
Become root and do:<br />
echo media-sound/mumble alsa dbus speech >> /etc/portage/package.use<br />
echo media-sound/mumble ~x86 >> /etc/portage/package.keywords<br />
emerge -av mumble<br />
That should do the magic. If something fails though, check up on [[BuildingLinux]]<br />
<br />
===ArchLinux===<br />
A stable PKGBUILD is avalaible in the [http://aur.archlinux.org/packages.php?do_Details=1&ID=10221&K=mumble AUR]. Download the tarball and then run:<br />
tar xzfv mumble*.tar.gz<br />
cd mumble*<br />
makepkg<br />
<br />
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:<br />
<br />
pacman -S alsa-lib qt4 libxevie sqlite3 boost<br />
<br />
Finally, install the package:<br />
<br />
pacman -A mumble-1.0.0-1.pkg.tar.gz<br />
<br />
Of course, replace the package name as appropriate.<br />
<br />
If you want to test a SVN Snapshoth, use this [http://aur.archlinux.org/packages.php?ID=23369 PKGBUILD] in the [http://aur.archlinux.org/packages.php?ID=23369 AUR]. Use [http://wiki.archlinux.org/index.php/Yaourt Yaourt] or the instructions above.<br />
<br />
==Mac OS X==<br />
<br />
Precompiled Mac OS X universal binaries are available from the [http://sourceforge.net/project/showfiles.php?group_id=147372 SourceForge downloads page].<br />
<br />
You can also build it from source yourself if you wish. See [[BuildingMacOsX]] for more information.<br />
<br />
==Snapshots==<br />
<br />
If you want to get the latest snapshots for Mumble and Murmur, you can find those [http://mumble.info/snapshot/ here]. These include the latest builds of Mumble and Murmur for Windows, and static builds of Murmur for Linux.<br />
<br />
=Post-installation tips=<br />
==Common tips==<br />
===Initializing/Resetting Murmur password===<br />
Type:<br />
murmur -supw <password><br />
That will change the password for SuperUser, a special user that has all rights.<br />
If you want to reset the entire database, just delete murmur.sqlite and the recreate it with the command above.<br />
<br />
==Windows==<br />
===Text-to-Speech===<br />
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 [http://www.nextup.com NextUp]).<br />
<br />
===Creating a server connection shortcut===<br />
You can right click on your desktop and choose "New" and pick "Shortcut" from the sub-menu.<br />
In the box that says "Type the location of the item" put "mumble://username:password@servername/channel"<br />
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. <br />
<br />
===It complains about mumble_ol.dll / Problems with Overlay===<br />
If you are running XP you will need to update it to SP2.<br />
<br />
=== Murmur dies when I log out! How can I get Murmur to stay on all the time? ===<br />
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.<br />
<br />
Some references you'll see int his write-up:<br />
<br />
instsrv.exe - A program that adds services to the Windows registry.<br />
<br />
srvany.exe - A program that allows any Windows application and some Windows 16-bit applications to run as a service.<br />
<br />
'''The HOW-TO'''<br />
<br />
Step 1: Gain Administrator access on the machine running Murmur.<br />
<br />
Step 2: Download and install the following collection of tools from Microsoft to the default directory (C:\Program Files\Windows Resource Kits):<br />
<br />
[http://www.microsoft.com/downloads/details.aspx?FamilyID=9d467a69-57ff-4ae7-96ee-b18c4790cffd&displaylang=en Windows 2003 Server Resource Kit].<br />
<br />
Step 3: Open a command console (Start >> Accessories >> Command Prompt).<br />
<br />
Step 4: If you have installed to the default directory, type the following:<br />
<br />
"C:\Program Files\Windows Resource Kits\Tools\instsrv.exe" "Murmur" "C:\Program Files\Windows Resource Kits\Tools\srvany.exe"<br />
<br />
The result of this step is a new service in the Services console (Start >> Control Panel >> Administrative Tools >> Services).<br />
<br />
'''Be sure to close the Services console before proceeding.'''<br />
<br />
Step 5: Open the registry editor (Start >> Run and enter "regedit") and navigate to the following key:<br />
<br />
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Murmur Demo<br />
<br />
<br />
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.<br />
<br />
Step 7: Name this new key "Parameters"<br />
<br />
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.<br />
<br />
Step 9: Name this new String value "Application".<br />
<br />
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.<br />
<br />
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.<br />
<br />
Step 11: Close Regedit<br />
<br />
Step 12: Open the Services console. Navigate to your service, and right click it and select Properties.<br />
<br />
Step 13: Make sure the Startup Type value is Automatic, and then press the Start button.<br />
<br />
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.<br />
<br />
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.<br />
<br />
If your server did not start, recheck your settings. Most problems are related to typos in configuration settings.<br />
<br />
==Linux==<br />
===Getting the Shortcuts Suppression to work===<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 />
=Uninstalling=<br />
[[UninstallingMumble | Instructions for completely removing Mumble, including user created settings and entries.]]</div>Haudraufhttps://wiki.mumble.info/index.php?title=Installing_Mumble&diff=2587Installing Mumble2009-02-01T21:59:09Z<p>Haudrauf: /* Linux */ uppercase for Mumble</p>
<hr />
<div>=Getting and Installing Mumble=<br />
This page shows you directions on how to install Mumble (client) as well as Murmur (server).<br />
<br />
==Windows==<br />
Just head to [http://sourceforge.net/project/showfiles.php?group_id=147372 SourceForge downloads page], get the Windows executable and run it. Follow the installer instructions and you are done.<br />
<br />
Also, you can build Mumble yourself from source as described in [[BuildingWindows]].<br />
<br />
==Linux==<br />
Some Linux distributions already have Mumble packaged so that an easy installation is possible. Check your package manager of your distribution for Mumble. But sometimes those packages are not up to date. So if you want more in-depth information about installing Mumble for Linux read up on [[BuildingLinux]]. Installation from source (svn and tarball) is described there.<br />
<br />
<br />
=== Debian ===<br />
<br />
Debian Testing (lenny) includes the latest official Mumble packages, and is the officially maintained version. New packaging efforts are encouraged to base their file layout and usernames on what is used here, to make third-party packages easier to port. To install:<br />
<br />
sudo aptitude install mumble<br />
''(for the client)''<br />
sudo aptitude install mumble-server mumble-server-web<br />
sudo dpkg-reconfigure mumble-server<br />
''(for the server and web applications)''<br />
<br />
''People who are in your Mumble server can go to http://<your IP or domain>/mumble/register.cgi to register with the server through a web interface.<br />
''They can also upload a custom texture that will be displayed in the Mumble game overlay from this page. <br />
''Any 600x60 PNG image will work, but if you have an alpha channel on in, it will have transparency.<br />
''http://<your IP or domain>/mumble/ shows the list of users in your Mumble server.<br />
<br />
v1.1.4-x86 Mumble for Debian Stable ('Etch', 4.0r5) is available at http://Vocis.K1T.NET/<br />
<br />
=== Ubuntu ===<br />
<br />
==== Official Repository ====<br />
<br />
'''This is the easy way, but you won't always get the latest version.'''<br />
<br />
Ubuntu Hardy Heron (8.04) includes the Mumble 1.1.x series in it's official repository. It's cloned from Debian testing before every Ubuntu release, so while it will lag slightly behind, it won't be by much. Just follow the directions for installing under Debian.<br />
<br />
==== PPA Repository ====<br />
<br />
'''This is a bit more to type, but should always be up-to-date.'''<br />
<br />
As the packages in the official Ubuntu repository aren't always up-to-date, you can add an external PPA repository to your package manager. It should always include the newest stable version of Mumble and Murmur for i386 and amd64 architectures.<br />
<br />
You will have to manually add the repositories for the PPA repository. Go to a command prompt and type <br />
sudo gedit /etc/apt/sources.list<br />
then add the following two lines to the bottom of the file<br />
deb http://ppa.launchpad.net/slicer/ubuntu hardy main<br />
deb-src http://ppa.launchpad.net/slicer/ubuntu hardy main<br />
sudo aptitude update <br />
(replace ''hardy'' with ''gutsy'' or ''intrepid'' if you are on those distributions)<br />
<br />
Afterwards you can use the same command as for installing under Debian (see above).<br />
<br />
More information about the PPA repository can be found at [https://edge.launchpad.net/~slicer/+archive Launchpad]<br />
<br />
===Fedora===<br />
Fedora 7 RPMs: [http://koji.fedoraproject.org/koji/getfile?taskID=227582&name=mumble-1.1.0-1.fc7.i386.rpm 1.1.0 i386] [http://koji.fedoraproject.org/koji/getfile?taskID=227581&name=mumble-1.1.0-1.fc7.x86_64.rpm 1.1.0 x86_64]<br />
Fedora 8 RPMs: [http://koji.fedoraproject.org/koji/getfile?taskID=231652&name=mumble-1.1.0-2.fc8.i386.rpm 1.1.0 i386] [http://koji.fedoraproject.org/koji/getfile?taskID=231651&name=mumble-1.1.0-2.fc8.x86_64.rpm 1.1.0 x86_64]<br />
<br />
===PCLinuxOS and other RPM based distros===<br />
You can find a rpm package in the [http://sourceforge.net/forum/forum.php?thread_id=1782689&forum_id=492606 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):<br />
<br />
rpm -i mumble-1.0.0-2.i386.rpm<br />
<br />
===Gentoo===<br />
Depending on what other features you want compiled into it, check up on the possible USE-flags: http://www.gentoo-portage.com/media-sound/mumble/USE#ptabs<br />
For most users it's useful to use the USE-flags alsa, dbus and speech - so we go with it.<br />
It's well possible that the Mumble ebuild is "masked". Here, we make sure it will install anyways.<br />
Become root and do:<br />
echo media-sound/mumble alsa dbus speech >> /etc/portage/package.use<br />
echo media-sound/mumble ~x86 >> /etc/portage/package.keywords<br />
emerge -av mumble<br />
That should do the magic. If something fails though, check up on [[BuildingLinux]]<br />
<br />
===ArchLinux===<br />
A stable PKGBUILD is avalaible in the [http://aur.archlinux.org/packages.php?do_Details=1&ID=10221&K=mumble AUR]. Download the tarball and then run:<br />
tar xzfv mumble*.tar.gz<br />
cd mumble*<br />
makepkg<br />
<br />
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:<br />
<br />
pacman -S alsa-lib qt4 libxevie sqlite3 boost<br />
<br />
Finally, install the package:<br />
<br />
pacman -A mumble-1.0.0-1.pkg.tar.gz<br />
<br />
Of course, replace the package name as appropriate.<br />
<br />
If you want to test a SVN Snapshoth, use this [http://aur.archlinux.org/packages.php?ID=23369 PKGBUILD] in the [http://aur.archlinux.org/packages.php?ID=23369 AUR]. Use [http://wiki.archlinux.org/index.php/Yaourt Yaourt] or the instructions above.<br />
<br />
==Mac OS X==<br />
<br />
Precompiled Mac OS X universal binaries are available from the [http://sourceforge.net/project/showfiles.php?group_id=147372 SourceForge downloads page].<br />
<br />
You can also build it from source yourself if you wish. See [[BuildingMacOsX]] for more information.<br />
<br />
==Snapshots==<br />
<br />
If you want to get the latest snapshots for Mumble and Murmur, you can find those [http://mumble.info/snapshot/ here]. These include the latest builds of Mumble and Murmur for Windows, and static builds of Murmur for Linux.<br />
<br />
=Post-installation tips=<br />
==Common tips==<br />
===Initializing/Resetting Murmur password===<br />
Type:<br />
murmur -supw <password><br />
That will change the password for SuperUser, a special user that has all rights.<br />
If you want to reset the entire database, just delete murmur.sqlite and the recreate it with the command above.<br />
<br />
==Windows==<br />
===Text-to-Speech===<br />
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 [http://www.nextup.com NextUp]).<br />
<br />
===Creating a server connection shortcut===<br />
You can right click on your desktop and choose "New" and pick "Shortcut" from the sub-menu.<br />
In the box that says "Type the location of the item" put "mumble://username:password@servername/channel"<br />
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. <br />
<br />
===It complains about mumble_ol.dll / Problems with Overlay===<br />
If you are running XP you will need to update it to SP2.<br />
<br />
=== Murmur dies when I log out! How can I get Murmur to stay on all the time? ===<br />
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.<br />
<br />
Some references you'll see int his write-up:<br />
<br />
instsrv.exe - A program that adds services to the Windows registry.<br />
<br />
srvany.exe - A program that allows any Windows application and some Windows 16-bit applications to run as a service.<br />
<br />
'''The HOW-TO'''<br />
<br />
Step 1: Gain Administrator access on the machine running Murmur.<br />
<br />
Step 2: Download and install the following collection of tools from Microsoft to the default directory (C:\Program Files\Windows Resource Kits):<br />
<br />
[http://www.microsoft.com/downloads/details.aspx?FamilyID=9d467a69-57ff-4ae7-96ee-b18c4790cffd&displaylang=en Windows 2003 Server Resource Kit].<br />
<br />
Step 3: Open a command console (Start >> Accessories >> Command Prompt).<br />
<br />
Step 4: If you have installed to the default directory, type the following:<br />
<br />
"C:\Program Files\Windows Resource Kits\Tools\instsrv.exe" "Murmur" "C:\Program Files\Windows Resource Kits\Tools\srvany.exe"<br />
<br />
The result of this step is a new service in the Services console (Start >> Control Panel >> Administrative Tools >> Services).<br />
<br />
'''Be sure to close the Services console before proceeding.'''<br />
<br />
Step 5: Open the registry editor (Start >> Run and enter "regedit") and navigate to the following key:<br />
<br />
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Murmur Demo<br />
<br />
<br />
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.<br />
<br />
Step 7: Name this new key "Parameters"<br />
<br />
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.<br />
<br />
Step 9: Name this new String value "Application".<br />
<br />
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.<br />
<br />
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.<br />
<br />
Step 11: Close Regedit<br />
<br />
Step 12: Open the Services console. Navigate to your service, and right click it and select Properties.<br />
<br />
Step 13: Make sure the Startup Type value is Automatic, and then press the Start button.<br />
<br />
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.<br />
<br />
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.<br />
<br />
If your server did not start, recheck your settings. Most problems are related to typos in configuration settings.<br />
<br />
==Linux==<br />
===Getting the Shortcuts Suppression to work===<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 />
=Uninstalling=<br />
[[UninstallingMumble | Instructions for completely removing Mumble, including user created settings and entries.]]</div>Haudraufhttps://wiki.mumble.info/index.php?title=Installing_Mumble&diff=2586Installing Mumble2009-02-01T21:58:10Z<p>Haudrauf: /* Getting and Installing Mumble */</p>
<hr />
<div>=Getting and Installing Mumble=<br />
This page shows you directions on how to install Mumble (client) as well as Murmur (server).<br />
<br />
==Windows==<br />
Just head to [http://sourceforge.net/project/showfiles.php?group_id=147372 SourceForge downloads page], get the Windows executable and run it. Follow the installer instructions and you are done.<br />
<br />
Also, you can build Mumble yourself from source as described in [[BuildingWindows]].<br />
<br />
==Linux==<br />
Some Linux distributions already have mumble packaged so that an easy installation is possible. Check your package manager of your distribution for mumble. But sometimes those packages are not up to date. So if you want more in-depth information about installing mumble for Linux read up on [[BuildingLinux]]. Installation from source (svn and tarball) is described there.<br />
<br />
<br />
=== Debian ===<br />
<br />
Debian Testing (lenny) includes the latest official Mumble packages, and is the officially maintained version. New packaging efforts are encouraged to base their file layout and usernames on what is used here, to make third-party packages easier to port. To install:<br />
<br />
sudo aptitude install mumble<br />
''(for the client)''<br />
sudo aptitude install mumble-server mumble-server-web<br />
sudo dpkg-reconfigure mumble-server<br />
''(for the server and web applications)''<br />
<br />
''People who are in your Mumble server can go to http://<your IP or domain>/mumble/register.cgi to register with the server through a web interface.<br />
''They can also upload a custom texture that will be displayed in the Mumble game overlay from this page. <br />
''Any 600x60 PNG image will work, but if you have an alpha channel on in, it will have transparency.<br />
''http://<your IP or domain>/mumble/ shows the list of users in your Mumble server.<br />
<br />
v1.1.4-x86 Mumble for Debian Stable ('Etch', 4.0r5) is available at http://Vocis.K1T.NET/<br />
<br />
=== Ubuntu ===<br />
<br />
==== Official Repository ====<br />
<br />
'''This is the easy way, but you won't always get the latest version.'''<br />
<br />
Ubuntu Hardy Heron (8.04) includes the Mumble 1.1.x series in it's official repository. It's cloned from Debian testing before every Ubuntu release, so while it will lag slightly behind, it won't be by much. Just follow the directions for installing under Debian.<br />
<br />
==== PPA Repository ====<br />
<br />
'''This is a bit more to type, but should always be up-to-date.'''<br />
<br />
As the packages in the official Ubuntu repository aren't always up-to-date, you can add an external PPA repository to your package manager. It should always include the newest stable version of Mumble and Murmur for i386 and amd64 architectures.<br />
<br />
You will have to manually add the repositories for the PPA repository. Go to a command prompt and type <br />
sudo gedit /etc/apt/sources.list<br />
then add the following two lines to the bottom of the file<br />
deb http://ppa.launchpad.net/slicer/ubuntu hardy main<br />
deb-src http://ppa.launchpad.net/slicer/ubuntu hardy main<br />
sudo aptitude update <br />
(replace ''hardy'' with ''gutsy'' or ''intrepid'' if you are on those distributions)<br />
<br />
Afterwards you can use the same command as for installing under Debian (see above).<br />
<br />
More information about the PPA repository can be found at [https://edge.launchpad.net/~slicer/+archive Launchpad]<br />
<br />
===Fedora===<br />
Fedora 7 RPMs: [http://koji.fedoraproject.org/koji/getfile?taskID=227582&name=mumble-1.1.0-1.fc7.i386.rpm 1.1.0 i386] [http://koji.fedoraproject.org/koji/getfile?taskID=227581&name=mumble-1.1.0-1.fc7.x86_64.rpm 1.1.0 x86_64]<br />
Fedora 8 RPMs: [http://koji.fedoraproject.org/koji/getfile?taskID=231652&name=mumble-1.1.0-2.fc8.i386.rpm 1.1.0 i386] [http://koji.fedoraproject.org/koji/getfile?taskID=231651&name=mumble-1.1.0-2.fc8.x86_64.rpm 1.1.0 x86_64]<br />
<br />
===PCLinuxOS and other RPM based distros===<br />
You can find a rpm package in the [http://sourceforge.net/forum/forum.php?thread_id=1782689&forum_id=492606 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):<br />
<br />
rpm -i mumble-1.0.0-2.i386.rpm<br />
<br />
===Gentoo===<br />
Depending on what other features you want compiled into it, check up on the possible USE-flags: http://www.gentoo-portage.com/media-sound/mumble/USE#ptabs<br />
For most users it's useful to use the USE-flags alsa, dbus and speech - so we go with it.<br />
It's well possible that the Mumble ebuild is "masked". Here, we make sure it will install anyways.<br />
Become root and do:<br />
echo media-sound/mumble alsa dbus speech >> /etc/portage/package.use<br />
echo media-sound/mumble ~x86 >> /etc/portage/package.keywords<br />
emerge -av mumble<br />
That should do the magic. If something fails though, check up on [[BuildingLinux]]<br />
<br />
===ArchLinux===<br />
A stable PKGBUILD is avalaible in the [http://aur.archlinux.org/packages.php?do_Details=1&ID=10221&K=mumble AUR]. Download the tarball and then run:<br />
tar xzfv mumble*.tar.gz<br />
cd mumble*<br />
makepkg<br />
<br />
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:<br />
<br />
pacman -S alsa-lib qt4 libxevie sqlite3 boost<br />
<br />
Finally, install the package:<br />
<br />
pacman -A mumble-1.0.0-1.pkg.tar.gz<br />
<br />
Of course, replace the package name as appropriate.<br />
<br />
If you want to test a SVN Snapshoth, use this [http://aur.archlinux.org/packages.php?ID=23369 PKGBUILD] in the [http://aur.archlinux.org/packages.php?ID=23369 AUR]. Use [http://wiki.archlinux.org/index.php/Yaourt Yaourt] or the instructions above.<br />
<br />
==Mac OS X==<br />
<br />
Precompiled Mac OS X universal binaries are available from the [http://sourceforge.net/project/showfiles.php?group_id=147372 SourceForge downloads page].<br />
<br />
You can also build it from source yourself if you wish. See [[BuildingMacOsX]] for more information.<br />
<br />
==Snapshots==<br />
<br />
If you want to get the latest snapshots for Mumble and Murmur, you can find those [http://mumble.info/snapshot/ here]. These include the latest builds of Mumble and Murmur for Windows, and static builds of Murmur for Linux.<br />
<br />
=Post-installation tips=<br />
==Common tips==<br />
===Initializing/Resetting Murmur password===<br />
Type:<br />
murmur -supw <password><br />
That will change the password for SuperUser, a special user that has all rights.<br />
If you want to reset the entire database, just delete murmur.sqlite and the recreate it with the command above.<br />
<br />
==Windows==<br />
===Text-to-Speech===<br />
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 [http://www.nextup.com NextUp]).<br />
<br />
===Creating a server connection shortcut===<br />
You can right click on your desktop and choose "New" and pick "Shortcut" from the sub-menu.<br />
In the box that says "Type the location of the item" put "mumble://username:password@servername/channel"<br />
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. <br />
<br />
===It complains about mumble_ol.dll / Problems with Overlay===<br />
If you are running XP you will need to update it to SP2.<br />
<br />
=== Murmur dies when I log out! How can I get Murmur to stay on all the time? ===<br />
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.<br />
<br />
Some references you'll see int his write-up:<br />
<br />
instsrv.exe - A program that adds services to the Windows registry.<br />
<br />
srvany.exe - A program that allows any Windows application and some Windows 16-bit applications to run as a service.<br />
<br />
'''The HOW-TO'''<br />
<br />
Step 1: Gain Administrator access on the machine running Murmur.<br />
<br />
Step 2: Download and install the following collection of tools from Microsoft to the default directory (C:\Program Files\Windows Resource Kits):<br />
<br />
[http://www.microsoft.com/downloads/details.aspx?FamilyID=9d467a69-57ff-4ae7-96ee-b18c4790cffd&displaylang=en Windows 2003 Server Resource Kit].<br />
<br />
Step 3: Open a command console (Start >> Accessories >> Command Prompt).<br />
<br />
Step 4: If you have installed to the default directory, type the following:<br />
<br />
"C:\Program Files\Windows Resource Kits\Tools\instsrv.exe" "Murmur" "C:\Program Files\Windows Resource Kits\Tools\srvany.exe"<br />
<br />
The result of this step is a new service in the Services console (Start >> Control Panel >> Administrative Tools >> Services).<br />
<br />
'''Be sure to close the Services console before proceeding.'''<br />
<br />
Step 5: Open the registry editor (Start >> Run and enter "regedit") and navigate to the following key:<br />
<br />
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Murmur Demo<br />
<br />
<br />
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.<br />
<br />
Step 7: Name this new key "Parameters"<br />
<br />
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.<br />
<br />
Step 9: Name this new String value "Application".<br />
<br />
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.<br />
<br />
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.<br />
<br />
Step 11: Close Regedit<br />
<br />
Step 12: Open the Services console. Navigate to your service, and right click it and select Properties.<br />
<br />
Step 13: Make sure the Startup Type value is Automatic, and then press the Start button.<br />
<br />
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.<br />
<br />
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.<br />
<br />
If your server did not start, recheck your settings. Most problems are related to typos in configuration settings.<br />
<br />
==Linux==<br />
===Getting the Shortcuts Suppression to work===<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 />
=Uninstalling=<br />
[[UninstallingMumble | Instructions for completely removing Mumble, including user created settings and entries.]]</div>Haudraufhttps://wiki.mumble.info/index.php?title=FAQ/English&diff=2585FAQ/English2009-02-01T21:39:46Z<p>Haudrauf: clearing things up, about "mumble" and "murmur"</p>
<hr />
<div>{{Languages|FAQ}}<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. It can be compared to programs like Ventrilo or TeamSpeak.<br />
People tend to simplify things, so when they talk about Mumble they either talk about "Mumble" the client application or about "Mumble & Murmur" the whole voice chat application suite.<br />
<br />
== What is Murmur? ==<br />
"Murmur" is the name of the server application. In any case, if anyone talks about Murmur it is for sure the server part.<br />
<br />
<br />
== What platforms does it run on? ==<br />
<br />
The client, Mumble, runs on Windows, Mac OS X and Linux.<br />
<br />
The server component, Murmur, should run on anything you can compile Qt 4 on.<br />
<br />
== What are the system requirements? ==<br />
<br />
The client runs on any Windows, Linux or Mac OS X machine. 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 Windows 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 />
<br />
[[Installing_Mumble]]<br />
<br />
== Compiling Mumble ==<br />
<br />
[[BuildingLinux]]<br />
<br />
[[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 noticeable 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 asymmetric 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 or contact you? ==<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. You can do so via the [http://sourceforge.net/forum/?group_id=147372 forums] or meet us on IRC at irc://irc.freenode.org/mumble<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. You can find a list of supported games in the [[Games#Positional_audio|Games article]].<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 />
murmur.ini is located in your Mumble Program Files folder on Windows, and in /etc/mumble-server.ini on Ubuntu.<br />
<br />
== What is the default server port for Murmur? ==<br />
<br />
The default server port for Murmur is UDP and TCP 64738.<br />
<br />
== Can I run multiple servers on one host? ==<br />
<br />
Yes, Murmur supports virtual servers. See [[Running_Murmur]]<br />
<br />
== How do the ACLs work? ==<br />
<br />
See [[ACL and Groups]]<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 />
<br />
See [[Running_Murmur]]<br />
<br />
== How can I change a users password? ==<br />
<br />
See [[Running_Murmur]]<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 />
= Common Problems and Resolutions =<br />
<br />
== 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 />
== 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 a 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. See [[FAQ#My server has multiple IP addresses. How can I make Murmur listen on a specific address?|How can I make Murmur listen on a specific address?]] for further information.<br />
<br />
== My server has multiple IP addresses. How can I make Murmur listen on a specific address? ==<br />
<br />
The host= option in murmur.ini lets you do this. If the option is blank (the default), it will listen on all addresses.<br />
<br />
== Server connection rejected: Invalid Password. ==<br />
This simply means the server password was incorrect, next time make sure you type in the password in the password box on the connect window.<br />
<br />
== Server connection failed: Host not found. ==<br />
This means that there is no computer at that ip address, double check this is the right IP<br />
<br />
== Server connection failed: Connection refused. ==<br />
This means there is a computer there but that is the incorrect port, double check the IP to make sure that this is the right computer, if it is then check what port you are supposed to connect on and put that in the port box on the connect screen.<br />
<br />
== I get disconnected from the server as soon as I connect. ==<br />
This can be due to a version mismatch between the server and the client. Ask the server owner about the version that its being used, and get that version.<br />
<br />
== I've Tried the above but it will not connect ==<br />
Are you on a Network make sure the port is open and the same if the host is on a network.<br />
<br />
== I tried but the port is open and it still will not connect ==<br />
Then you should enable port forwarding on your router to your computer for the port. To get your LAN IP address:<br />
*Windows: press run then type "cmd" (no quotes) and type in "ipconfig" and it will display your IP address next to IP Address.<br />
*Linux and other unixes: On a console, type ''ifconfig''. Your IP is next to ''inet addr:''<br />
<br />
== Mumble will not even start - I have a Tablet PC or some sort of touch based input device based on Wacom. ==<br />
Update your Wacom [http://www.wacom.com/productsupport/select.cfm drivers].<br />
<br />
== For some reason my game will crash when I'm running Mumble ==<br />
The Mumble Overlay is a nice feature that many people use, but because of the rendering methods it uses to display the overlay while you're in a game, it can sometimes make the game crash or not work properly. You can find a list of games that are known to have issues with the overlay and how to solve problems experienced in these games in the [[Games#Overlay|Games article]]. You can also find an application incompatibility list on this page as well.<br />
<br />
== I'm running many virtual servers (150+) per physical server and sometimes they crash or get unresponsive ==<br />
A phenomenon experienced mostly by commercial hosters who have a lot of virtual servers running. To fix the issues, you need to recompile Qt with FD_SETSIZE set to a much bigger value (it can be found in typesizes.h) and make sure that Qt runs with glib support.<br />
<br />
You have to experiment with the value of FD_SETSIZE. 8192 has been reported to run well with approximately 200 servers. Your mileage may vary, of course.<br />
<br />
See also http://trolltech.com/developer/task-tracker/index_html?id=240300&method=entry<br />
<br />
= Compilation / installation problems =<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 />
== Error message in murmur.cgi line 118 ==<br />
<br />
You need an MTA on localhost unless you have defined a different SMTP server.<br />
<br />
==Completely uninstalling Mumble on Windows==<br />
See [[UninstallingMumble]].<br />
<br />
= Language Translation =<br />
<br />
See [[LanguageTranslation| here]].<br />
<br />
= Recording =<br />
<br />
Many people use Mumble for podcasting/radio because of it's high quality and low latency, and we realize that some people want to record their conversation on Mumble for these types of purposes. <br />
<br />
On Windows this is fairly simple, there are many different programs that can capture audio. [http://audacity.sourceforge.net/ Audacity] is a good program for doing this. Many people just use a spare computer they have and login to the Murmur server and set Audacity to record "What U Hear".<br />
<br />
If you using PulseAudio, read this [http://files.kral.ws/Tobias/Gentoo/mumble-conference_record_with_pulseaudio_and_gstreamer.txt this guide] on how to record Mumble conversations. The guide is written for Gentoo Linux, but users of other systems should be able to adapt this guide to their system.</div>Haudraufhttps://wiki.mumble.info/index.php?title=FAQ/English&diff=2584FAQ/English2009-02-01T21:36:10Z<p>Haudrauf: /* What is Mumble? */</p>
<hr />
<div>{{Languages|FAQ}}<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. It can be compared to programs like Ventrilo or TeamSpeak.<br />
<br />
== What is Murmur? ==<br />
<br />
"Murmur" is the name of the server application. "Mumble" is merely the name of the client application. People of course tend to simplify things so when they talk about Mumble they either talk the "Mumble & Murmur"-suite or about the client application.<br />
In any case, if anyone talks about Murmur it is for sure the server part.<br />
<br />
== What platforms does it run on? ==<br />
<br />
The client, Mumble, runs on Windows, Mac OS X and Linux.<br />
<br />
The server component, Murmur, should run on anything you can compile Qt 4 on.<br />
<br />
== What are the system requirements? ==<br />
<br />
The client runs on any Windows, Linux or Mac OS X machine. 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 Windows 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 />
<br />
[[Installing_Mumble]]<br />
<br />
== Compiling Mumble ==<br />
<br />
[[BuildingLinux]]<br />
<br />
[[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 noticeable 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 asymmetric 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 or contact you? ==<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. You can do so via the [http://sourceforge.net/forum/?group_id=147372 forums] or meet us on IRC at irc://irc.freenode.org/mumble<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. You can find a list of supported games in the [[Games#Positional_audio|Games article]].<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 />
murmur.ini is located in your Mumble Program Files folder on Windows, and in /etc/mumble-server.ini on Ubuntu.<br />
<br />
== What is the default server port for Murmur? ==<br />
<br />
The default server port for Murmur is UDP and TCP 64738.<br />
<br />
== Can I run multiple servers on one host? ==<br />
<br />
Yes, Murmur supports virtual servers. See [[Running_Murmur]]<br />
<br />
== How do the ACLs work? ==<br />
<br />
See [[ACL and Groups]]<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 />
<br />
See [[Running_Murmur]]<br />
<br />
== How can I change a users password? ==<br />
<br />
See [[Running_Murmur]]<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 />
= Common Problems and Resolutions =<br />
<br />
== 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 />
== 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 a 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. See [[FAQ#My server has multiple IP addresses. How can I make Murmur listen on a specific address?|How can I make Murmur listen on a specific address?]] for further information.<br />
<br />
== My server has multiple IP addresses. How can I make Murmur listen on a specific address? ==<br />
<br />
The host= option in murmur.ini lets you do this. If the option is blank (the default), it will listen on all addresses.<br />
<br />
== Server connection rejected: Invalid Password. ==<br />
This simply means the server password was incorrect, next time make sure you type in the password in the password box on the connect window.<br />
<br />
== Server connection failed: Host not found. ==<br />
This means that there is no computer at that ip address, double check this is the right IP<br />
<br />
== Server connection failed: Connection refused. ==<br />
This means there is a computer there but that is the incorrect port, double check the IP to make sure that this is the right computer, if it is then check what port you are supposed to connect on and put that in the port box on the connect screen.<br />
<br />
== I get disconnected from the server as soon as I connect. ==<br />
This can be due to a version mismatch between the server and the client. Ask the server owner about the version that its being used, and get that version.<br />
<br />
== I've Tried the above but it will not connect ==<br />
Are you on a Network make sure the port is open and the same if the host is on a network.<br />
<br />
== I tried but the port is open and it still will not connect ==<br />
Then you should enable port forwarding on your router to your computer for the port. To get your LAN IP address:<br />
*Windows: press run then type "cmd" (no quotes) and type in "ipconfig" and it will display your IP address next to IP Address.<br />
*Linux and other unixes: On a console, type ''ifconfig''. Your IP is next to ''inet addr:''<br />
<br />
== Mumble will not even start - I have a Tablet PC or some sort of touch based input device based on Wacom. ==<br />
Update your Wacom [http://www.wacom.com/productsupport/select.cfm drivers].<br />
<br />
== For some reason my game will crash when I'm running Mumble ==<br />
The Mumble Overlay is a nice feature that many people use, but because of the rendering methods it uses to display the overlay while you're in a game, it can sometimes make the game crash or not work properly. You can find a list of games that are known to have issues with the overlay and how to solve problems experienced in these games in the [[Games#Overlay|Games article]]. You can also find an application incompatibility list on this page as well.<br />
<br />
== I'm running many virtual servers (150+) per physical server and sometimes they crash or get unresponsive ==<br />
A phenomenon experienced mostly by commercial hosters who have a lot of virtual servers running. To fix the issues, you need to recompile Qt with FD_SETSIZE set to a much bigger value (it can be found in typesizes.h) and make sure that Qt runs with glib support.<br />
<br />
You have to experiment with the value of FD_SETSIZE. 8192 has been reported to run well with approximately 200 servers. Your mileage may vary, of course.<br />
<br />
See also http://trolltech.com/developer/task-tracker/index_html?id=240300&method=entry<br />
<br />
= Compilation / installation problems =<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 />
== Error message in murmur.cgi line 118 ==<br />
<br />
You need an MTA on localhost unless you have defined a different SMTP server.<br />
<br />
==Completely uninstalling Mumble on Windows==<br />
See [[UninstallingMumble]].<br />
<br />
= Language Translation =<br />
<br />
See [[LanguageTranslation| here]].<br />
<br />
= Recording =<br />
<br />
Many people use Mumble for podcasting/radio because of it's high quality and low latency, and we realize that some people want to record their conversation on Mumble for these types of purposes. <br />
<br />
On Windows this is fairly simple, there are many different programs that can capture audio. [http://audacity.sourceforge.net/ Audacity] is a good program for doing this. Many people just use a spare computer they have and login to the Murmur server and set Audacity to record "What U Hear".<br />
<br />
If you using PulseAudio, read this [http://files.kral.ws/Tobias/Gentoo/mumble-conference_record_with_pulseaudio_and_gstreamer.txt this guide] on how to record Mumble conversations. The guide is written for Gentoo Linux, but users of other systems should be able to adapt this guide to their system.</div>Haudraufhttps://wiki.mumble.info/index.php?title=Installing_Mumble&diff=2513Installing Mumble2009-01-16T17:31:33Z<p>Haudrauf: /* Client (Mumble) */</p>
<hr />
<div>=Getting and Installing Mumble=<br />
<br />
==Windows==<br />
Just head to [http://sourceforge.net/project/showfiles.php?group_id=147372 SourceForge downloads page], get the Windows executable and run it. Follow the installer instructions and you are done.<br />
<br />
Also, you can build Mumble yourself from source as described in [[BuildingWindows]].<br />
<br />
==Linux==<br />
Some Linux distributions already have mumble packaged so that an easy installation is possible. Check your package manager of your distribution for mumble. But sometimes those packages are not up to date. So if you want more in-depth information about installing mumble for Linux read up on [[BuildingLinux]]. Installation from source (svn and tarball) is described there.<br />
<br />
<br />
=== Debian ===<br />
<br />
Debian Testing (lenny) includes the latest official Mumble packages, and is the officially maintained version. New packaging efforts are encouraged to base their file layout and usernames on what is used here, to make third-party packages easier to port. To install:<br />
<br />
sudo aptitude install mumble<br />
''(for the client)''<br />
sudo aptitude install mumble-server mumble-server-web<br />
sudo dpkg-reconfigure mumble-server<br />
''(for the server and web applications)''<br />
<br />
''People who are in your Mumble server can go to http://<your IP or domain>/mumble/register.cgi to register with the server through a web interface.<br />
''They can also upload a custom texture that will be displayed in the Mumble game overlay from this page. <br />
''Any 600x60 PNG image will work, but if you have an alpha channel on in, it will have transparency.<br />
''http://<your IP or domain>/mumble/ shows the list of users in your Mumble server.<br />
<br />
v1.1.4-x86 Mumble for Debian Stable ('Etch', 4.0r5) is available at http://Vocis.K1T.NET/<br />
<br />
=== Ubuntu ===<br />
<br />
==== Official Repository ====<br />
<br />
'''This is the easy way, but you won't always get the latest version.'''<br />
<br />
Ubuntu Hardy Heron (8.04) includes the Mumble 1.1.x series in it's official repository. It's cloned from Debian testing before every Ubuntu release, so while it will lag slightly behind, it won't be by much. Just follow the directions for installing under Debian.<br />
<br />
==== PPA Repository ====<br />
<br />
'''This is a bit more to type, but should always be up-to-date.'''<br />
<br />
As the packages in the official Ubuntu repository aren't always up-to-date, you can add an external PPA repository to your package manager. It should always include the newest stable version of Mumble and Murmur for i386 and amd64 architectures.<br />
<br />
You will have to manually add the repositories for the PPA repository. Go to a command prompt and type <br />
sudo gedit /etc/apt/sources.list<br />
then add the following two lines to the bottom of the file<br />
deb http://ppa.launchpad.net/slicer/ubuntu hardy main<br />
deb-src http://ppa.launchpad.net/slicer/ubuntu hardy main<br />
sudo aptitude update <br />
(replace ''hardy'' with ''gutsy'' or ''intrepid'' if you are on those distributions)<br />
<br />
Afterwards you can use the same command as for installing under Debian (see above).<br />
<br />
More information about the PPA repository can be found at [https://edge.launchpad.net/~slicer/+archive Launchpad]<br />
<br />
===Fedora===<br />
Fedora 7 RPMs: [http://koji.fedoraproject.org/koji/getfile?taskID=227582&name=mumble-1.1.0-1.fc7.i386.rpm 1.1.0 i386] [http://koji.fedoraproject.org/koji/getfile?taskID=227581&name=mumble-1.1.0-1.fc7.x86_64.rpm 1.1.0 x86_64]<br />
Fedora 8 RPMs: [http://koji.fedoraproject.org/koji/getfile?taskID=231652&name=mumble-1.1.0-2.fc8.i386.rpm 1.1.0 i386] [http://koji.fedoraproject.org/koji/getfile?taskID=231651&name=mumble-1.1.0-2.fc8.x86_64.rpm 1.1.0 x86_64]<br />
<br />
===PCLinuxOS and other RPM based distros===<br />
You can find a rpm package in the [http://sourceforge.net/forum/forum.php?thread_id=1782689&forum_id=492606 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):<br />
<br />
rpm -i mumble-1.0.0-2.i386.rpm<br />
<br />
===Gentoo===<br />
Depending on what other features you want compiled into it, check up on the possible USE-flags: http://www.gentoo-portage.com/media-sound/mumble/USE#ptabs<br />
For most users it's useful to use the USE-flags alsa, dbus and speech - so we go with it.<br />
It's well possible that the Mumble ebuild is "masked". Here, we make sure it will install anyways.<br />
Become root and do:<br />
echo media-sound/mumble alsa dbus speech >> /etc/portage/package.use<br />
echo media-sound/mumble ~x86 >> /etc/portage/package.keywords<br />
emerge -av mumble<br />
That should do the magic. If something fails though, check up on [[BuildingLinux]]<br />
<br />
===ArchLinux===<br />
A PKGBUILD is avalaible in the [http://aur.archlinux.org/packages.php?do_Details=1&ID=10221&K=mumble AUR]. Download the tarball and then run:<br />
tar xzfv mumble.tar.gz<br />
cd mumble<br />
makepkg<br />
<br />
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:<br />
<br />
pacman -S alsa-lib qt4 libxevie sqlite3 boost<br />
<br />
Finally, install the package:<br />
<br />
pacman -A mumble-1.0.0-1.pkg.tar.gz<br />
<br />
Of course, replace the package name as appropriate.<br />
<br />
==Mac OS X==<br />
<br />
Precompiled Mac OS X universal binaries are available from the [http://sourceforge.net/project/showfiles.php?group_id=147372 SourceForge downloads page].<br />
<br />
You can also build it from source yourself if you wish. See [[BuildingMacOsX]] for more information.<br />
<br />
==Snapshots==<br />
<br />
If you want to get the latest snapshots for Mumble and Murmur, you can find those [http://mumble.info/snapshot/ here]. These include the latest builds of Mumble and Murmur for Windows, and static builds of Murmur for Linux.<br />
<br />
=Post-installation tips=<br />
==Common tips==<br />
===Initializing/Resetting Murmur password===<br />
Type:<br />
murmur -supw <password><br />
That will change the password for SuperUser, a special user that has all rights.<br />
If you want to reset the entire database, just delete murmur.sqlite and the recreate it with the command above.<br />
<br />
==Windows==<br />
===Text-to-Speech===<br />
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 [http://www.nextup.com NextUp]).<br />
<br />
===Creating a server connection shortcut===<br />
You can right click on your desktop and choose "New" and pick "Shortcut" from the sub-menu.<br />
In the box that says "Type the location of the item" put "mumble://username:password@servername/channel"<br />
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. <br />
<br />
===It complains about mumble_ol.dll / Problems with Overlay===<br />
If you are running XP you will need to update it to SP2.<br />
<br />
=== Murmur dies when I log out! How can I get Murmur to stay on all the time? ===<br />
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.<br />
<br />
Some references you'll see int his write-up:<br />
<br />
instsrv.exe - A program that adds services to the Windows registry.<br />
<br />
srvany.exe - A program that allows any Windows application and some Windows 16-bit applications to run as a service.<br />
<br />
'''The HOW-TO'''<br />
<br />
Step 1: Gain Administrator access on the machine running Murmur.<br />
<br />
Step 2: Download and install the following collection of tools from Microsoft to the default directory (C:\Program Files\Windows Resource Kits):<br />
<br />
[http://www.microsoft.com/downloads/details.aspx?FamilyID=9d467a69-57ff-4ae7-96ee-b18c4790cffd&displaylang=en Windows 2003 Server Resource Kit].<br />
<br />
Step 3: Open a command console (Start >> Accessories >> Command Prompt).<br />
<br />
Step 4: If you have installed to the default directory, type the following:<br />
<br />
"C:\Program Files\Windows Resource Kits\Tools\instsrv.exe" "Murmur" "C:\Program Files\Windows Resource Kits\Tools\srvany.exe"<br />
<br />
The result of this step is a new service in the Services console (Start >> Control Panel >> Administrative Tools >> Services).<br />
<br />
'''Be sure to close the Services console before proceeding.'''<br />
<br />
Step 5: Open the registry editor (Start >> Run and enter "regedit") and navigate to the following key:<br />
<br />
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Murmur Demo<br />
<br />
<br />
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.<br />
<br />
Step 7: Name this new key "Parameters"<br />
<br />
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.<br />
<br />
Step 9: Name this new String value "Application".<br />
<br />
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.<br />
<br />
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.<br />
<br />
Step 11: Close Regedit<br />
<br />
Step 12: Open the Services console. Navigate to your service, and right click it and select Properties.<br />
<br />
Step 13: Make sure the Startup Type value is Automatic, and then press the Start button.<br />
<br />
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.<br />
<br />
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.<br />
<br />
If your server did not start, recheck your settings. Most problems are related to typos in configuration settings.<br />
<br />
==Linux==<br />
===Getting the Shortcuts Suppression to work===<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 />
=Uninstalling=<br />
[[UninstallingMumble | Instructions for completely removing Mumble, including user created settings and entries.]]</div>Haudraufhttps://wiki.mumble.info/index.php?title=Installing_Mumble&diff=2512Installing Mumble2009-01-16T17:27:24Z<p>Haudrauf: people can now just use copy and paste :)</p>
<hr />
<div>=Getting and Installing Mumble=<br />
<br />
==Windows==<br />
Just head to [http://sourceforge.net/project/showfiles.php?group_id=147372 SourceForge downloads page], get the Windows executable and run it. Follow the installer instructions and you are done.<br />
<br />
Also, you can build Mumble yourself from source as described in [[BuildingWindows]].<br />
<br />
==Linux==<br />
Some Linux distributions already have mumble packaged so that an easy installation is possible. Check your package manager of your distribution for mumble. But sometimes those packages are not up to date. So if you want more in-depth information about installing mumble for Linux read up on [[BuildingLinux]]. Installation from source (svn and tarball) is described there.<br />
<br />
<br />
=== Debian ===<br />
<br />
Debian Testing (lenny) includes the latest official Mumble packages, and is the officially maintained version. New packaging efforts are encouraged to base their file layout and usernames on what is used here, to make third-party packages easier to port. To install:<br />
<br />
sudo aptitude install mumble<br />
''(for the client)''<br />
sudo aptitude install mumble-server mumble-server-web<br />
sudo dpkg-reconfigure mumble-server<br />
''(for the server and web applications)''<br />
<br />
''People who are in your Mumble server can go to http://<your IP or domain>/mumble/register.cgi to register with the server through a web interface.<br />
''They can also upload a custom texture that will be displayed in the Mumble game overlay from this page. <br />
''Any 600x60 PNG image will work, but if you have an alpha channel on in, it will have transparency.<br />
''http://<your IP or domain>/mumble/ shows the list of users in your Mumble server.<br />
<br />
v1.1.4-x86 Mumble for Debian Stable ('Etch', 4.0r5) is available at http://Vocis.K1T.NET/<br />
<br />
=== Ubuntu ===<br />
<br />
==== Official Repository ====<br />
<br />
'''This is the easy way, but you won't always get the latest version.'''<br />
<br />
Ubuntu Hardy Heron (8.04) includes the Mumble 1.1.x series in it's official repository. It's cloned from Debian testing before every Ubuntu release, so while it will lag slightly behind, it won't be by much. Just follow the directions for installing under Debian.<br />
<br />
==== PPA Repository ====<br />
<br />
'''This is a bit more to type, but should always be up-to-date.'''<br />
<br />
As the packages in the official Ubuntu repository aren't always up-to-date, you can add an external PPA repository to your package manager. It should always include the newest stable version of Mumble and Murmur for i386 and amd64 architectures.<br />
<br />
You will have to manually add the repositories for the PPA repository. Go to a command prompt and type <br />
sudo gedit /etc/apt/sources.list<br />
then add the following two lines to the bottom of the file<br />
deb http://ppa.launchpad.net/slicer/ubuntu hardy main<br />
deb-src http://ppa.launchpad.net/slicer/ubuntu hardy main<br />
sudo aptitude update <br />
(replace ''hardy'' with ''gutsy'' or ''intrepid'' if you are on those distributions)<br />
<br />
Afterwards you can use the same command as for installing under Debian (see above).<br />
<br />
More information about the PPA repository can be found at [https://edge.launchpad.net/~slicer/+archive Launchpad]<br />
<br />
===Fedora===<br />
Fedora 7 RPMs: [http://koji.fedoraproject.org/koji/getfile?taskID=227582&name=mumble-1.1.0-1.fc7.i386.rpm 1.1.0 i386] [http://koji.fedoraproject.org/koji/getfile?taskID=227581&name=mumble-1.1.0-1.fc7.x86_64.rpm 1.1.0 x86_64]<br />
Fedora 8 RPMs: [http://koji.fedoraproject.org/koji/getfile?taskID=231652&name=mumble-1.1.0-2.fc8.i386.rpm 1.1.0 i386] [http://koji.fedoraproject.org/koji/getfile?taskID=231651&name=mumble-1.1.0-2.fc8.x86_64.rpm 1.1.0 x86_64]<br />
<br />
===PCLinuxOS and other RPM based distros===<br />
You can find a rpm package in the [http://sourceforge.net/forum/forum.php?thread_id=1782689&forum_id=492606 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):<br />
<br />
rpm -i mumble-1.0.0-2.i386.rpm<br />
<br />
===Gentoo===<br />
====Client (Mumble)====<br />
Depending on what other features you want compiled into it, check up on the possible USE-flags: http://www.gentoo-portage.com/media-sound/mumble/USE#ptabs<br />
For most users it's useful to use the USE-flags alsa, dbus and speech - so we go with it.<br />
It's well possible that the Mumble ebuild is "masked". Here, we make sure it will install anyways.<br />
Become root and do:<br />
echo media-sound/mumble alsa dbus speech >> /etc/portage/package.use<br />
echo media-sound/mumble ~x86 >> /etc/portage/package.keywords<br />
emerge -av mumble<br />
That should do the magic. If something fails though, check up on [[BuildingLinux]]<br />
<br />
===ArchLinux===<br />
A PKGBUILD is avalaible in the [http://aur.archlinux.org/packages.php?do_Details=1&ID=10221&K=mumble AUR]. Download the tarball and then run:<br />
tar xzfv mumble.tar.gz<br />
cd mumble<br />
makepkg<br />
<br />
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:<br />
<br />
pacman -S alsa-lib qt4 libxevie sqlite3 boost<br />
<br />
Finally, install the package:<br />
<br />
pacman -A mumble-1.0.0-1.pkg.tar.gz<br />
<br />
Of course, replace the package name as appropriate.<br />
<br />
==Mac OS X==<br />
<br />
Precompiled Mac OS X universal binaries are available from the [http://sourceforge.net/project/showfiles.php?group_id=147372 SourceForge downloads page].<br />
<br />
You can also build it from source yourself if you wish. See [[BuildingMacOsX]] for more information.<br />
<br />
==Snapshots==<br />
<br />
If you want to get the latest snapshots for Mumble and Murmur, you can find those [http://mumble.info/snapshot/ here]. These include the latest builds of Mumble and Murmur for Windows, and static builds of Murmur for Linux.<br />
<br />
=Post-installation tips=<br />
==Common tips==<br />
===Initializing/Resetting Murmur password===<br />
Type:<br />
murmur -supw <password><br />
That will change the password for SuperUser, a special user that has all rights.<br />
If you want to reset the entire database, just delete murmur.sqlite and the recreate it with the command above.<br />
<br />
==Windows==<br />
===Text-to-Speech===<br />
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 [http://www.nextup.com NextUp]).<br />
<br />
===Creating a server connection shortcut===<br />
You can right click on your desktop and choose "New" and pick "Shortcut" from the sub-menu.<br />
In the box that says "Type the location of the item" put "mumble://username:password@servername/channel"<br />
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. <br />
<br />
===It complains about mumble_ol.dll / Problems with Overlay===<br />
If you are running XP you will need to update it to SP2.<br />
<br />
=== Murmur dies when I log out! How can I get Murmur to stay on all the time? ===<br />
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.<br />
<br />
Some references you'll see int his write-up:<br />
<br />
instsrv.exe - A program that adds services to the Windows registry.<br />
<br />
srvany.exe - A program that allows any Windows application and some Windows 16-bit applications to run as a service.<br />
<br />
'''The HOW-TO'''<br />
<br />
Step 1: Gain Administrator access on the machine running Murmur.<br />
<br />
Step 2: Download and install the following collection of tools from Microsoft to the default directory (C:\Program Files\Windows Resource Kits):<br />
<br />
[http://www.microsoft.com/downloads/details.aspx?FamilyID=9d467a69-57ff-4ae7-96ee-b18c4790cffd&displaylang=en Windows 2003 Server Resource Kit].<br />
<br />
Step 3: Open a command console (Start >> Accessories >> Command Prompt).<br />
<br />
Step 4: If you have installed to the default directory, type the following:<br />
<br />
"C:\Program Files\Windows Resource Kits\Tools\instsrv.exe" "Murmur" "C:\Program Files\Windows Resource Kits\Tools\srvany.exe"<br />
<br />
The result of this step is a new service in the Services console (Start >> Control Panel >> Administrative Tools >> Services).<br />
<br />
'''Be sure to close the Services console before proceeding.'''<br />
<br />
Step 5: Open the registry editor (Start >> Run and enter "regedit") and navigate to the following key:<br />
<br />
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Murmur Demo<br />
<br />
<br />
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.<br />
<br />
Step 7: Name this new key "Parameters"<br />
<br />
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.<br />
<br />
Step 9: Name this new String value "Application".<br />
<br />
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.<br />
<br />
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.<br />
<br />
Step 11: Close Regedit<br />
<br />
Step 12: Open the Services console. Navigate to your service, and right click it and select Properties.<br />
<br />
Step 13: Make sure the Startup Type value is Automatic, and then press the Start button.<br />
<br />
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.<br />
<br />
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.<br />
<br />
If your server did not start, recheck your settings. Most problems are related to typos in configuration settings.<br />
<br />
==Linux==<br />
===Getting the Shortcuts Suppression to work===<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 />
=Uninstalling=<br />
[[UninstallingMumble | Instructions for completely removing Mumble, including user created settings and entries.]]</div>Haudraufhttps://wiki.mumble.info/index.php?title=Installing_Mumble&diff=2511Installing Mumble2009-01-16T17:26:53Z<p>Haudrauf: /* Gentoo */</p>
<hr />
<div>=Getting and Installing Mumble=<br />
<br />
==Windows==<br />
Just head to [http://sourceforge.net/project/showfiles.php?group_id=147372 SourceForge downloads page], get the Windows executable and run it. Follow the installer instructions and you are done.<br />
<br />
Also, you can build Mumble yourself from source as described in [[BuildingWindows]].<br />
<br />
==Linux==<br />
Some Linux distributions already have mumble packaged so that an easy installation is possible. Check your package manager of your distribution for mumble. But sometimes those packages are not up to date. So if you want more in-depth information about installing mumble for Linux read up on [[BuildingLinux]]. Installation from source (svn and tarball) is described there.<br />
<br />
<br />
=== Debian ===<br />
<br />
Debian Testing (lenny) includes the latest official Mumble packages, and is the officially maintained version. New packaging efforts are encouraged to base their file layout and usernames on what is used here, to make third-party packages easier to port. To install:<br />
<br />
sudo aptitude install mumble<br />
''(for the client)''<br />
sudo aptitude install mumble-server mumble-server-web<br />
sudo dpkg-reconfigure mumble-server<br />
''(for the server and web applications)''<br />
<br />
''People who are in your Mumble server can go to http://<your IP or domain>/mumble/register.cgi to register with the server through a web interface.<br />
''They can also upload a custom texture that will be displayed in the Mumble game overlay from this page. <br />
''Any 600x60 PNG image will work, but if you have an alpha channel on in, it will have transparency.<br />
''http://<your IP or domain>/mumble/ shows the list of users in your Mumble server.<br />
<br />
v1.1.4-x86 Mumble for Debian Stable ('Etch', 4.0r5) is available at http://Vocis.K1T.NET/<br />
<br />
=== Ubuntu ===<br />
<br />
==== Official Repository ====<br />
<br />
'''This is the easy way, but you won't always get the latest version.'''<br />
<br />
Ubuntu Hardy Heron (8.04) includes the Mumble 1.1.x series in it's official repository. It's cloned from Debian testing before every Ubuntu release, so while it will lag slightly behind, it won't be by much. Just follow the directions for installing under Debian.<br />
<br />
==== PPA Repository ====<br />
<br />
'''This is a bit more to type, but should always be up-to-date.'''<br />
<br />
As the packages in the official Ubuntu repository aren't always up-to-date, you can add an external PPA repository to your package manager. It should always include the newest stable version of Mumble and Murmur for i386 and amd64 architectures.<br />
<br />
You will have to manually add the repositories for the PPA repository. Go to a command prompt and type <br />
sudo gedit /etc/apt/sources.list<br />
then add the following two lines to the bottom of the file<br />
deb http://ppa.launchpad.net/slicer/ubuntu hardy main<br />
deb-src http://ppa.launchpad.net/slicer/ubuntu hardy main<br />
sudo aptitude update <br />
(replace ''hardy'' with ''gutsy'' or ''intrepid'' if you are on those distributions)<br />
<br />
Afterwards you can use the same command as for installing under Debian (see above).<br />
<br />
More information about the PPA repository can be found at [https://edge.launchpad.net/~slicer/+archive Launchpad]<br />
<br />
===Fedora===<br />
Fedora 7 RPMs: [http://koji.fedoraproject.org/koji/getfile?taskID=227582&name=mumble-1.1.0-1.fc7.i386.rpm 1.1.0 i386] [http://koji.fedoraproject.org/koji/getfile?taskID=227581&name=mumble-1.1.0-1.fc7.x86_64.rpm 1.1.0 x86_64]<br />
Fedora 8 RPMs: [http://koji.fedoraproject.org/koji/getfile?taskID=231652&name=mumble-1.1.0-2.fc8.i386.rpm 1.1.0 i386] [http://koji.fedoraproject.org/koji/getfile?taskID=231651&name=mumble-1.1.0-2.fc8.x86_64.rpm 1.1.0 x86_64]<br />
<br />
===PCLinuxOS and other RPM based distros===<br />
You can find a rpm package in the [http://sourceforge.net/forum/forum.php?thread_id=1782689&forum_id=492606 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):<br />
<br />
rpm -i mumble-1.0.0-2.i386.rpm<br />
<br />
===Gentoo===<br />
====Client (Mumble)====<br />
Depending on what other features you want compiled into it, check up on the possible USE-flags: http://www.gentoo-portage.com/media-sound/mumble/USE#ptabs<br />
For most users it's useful to use the USE-flags alsa, dbus and speech - so we go with it.<br />
It's well possible that the Mumble ebuild is "masked". Here, we make sure it will install anyways.<br />
Become root and do:<br />
# echo media-sound/mumble alsa dbus speech >> /etc/portage/package.use<br />
# echo media-sound/mumble ~x86 >> /etc/portage/package.keywords<br />
# emerge -av mumble<br />
That should do the magic. If something fails though, check up on [[BuildingLinux]]<br />
<br />
===ArchLinux===<br />
A PKGBUILD is avalaible in the [http://aur.archlinux.org/packages.php?do_Details=1&ID=10221&K=mumble AUR]. Download the tarball and then run:<br />
tar xzfv mumble.tar.gz<br />
cd mumble<br />
makepkg<br />
<br />
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:<br />
<br />
pacman -S alsa-lib qt4 libxevie sqlite3 boost<br />
<br />
Finally, install the package:<br />
<br />
pacman -A mumble-1.0.0-1.pkg.tar.gz<br />
<br />
Of course, replace the package name as appropriate.<br />
<br />
==Mac OS X==<br />
<br />
Precompiled Mac OS X universal binaries are available from the [http://sourceforge.net/project/showfiles.php?group_id=147372 SourceForge downloads page].<br />
<br />
You can also build it from source yourself if you wish. See [[BuildingMacOsX]] for more information.<br />
<br />
==Snapshots==<br />
<br />
If you want to get the latest snapshots for Mumble and Murmur, you can find those [http://mumble.info/snapshot/ here]. These include the latest builds of Mumble and Murmur for Windows, and static builds of Murmur for Linux.<br />
<br />
=Post-installation tips=<br />
==Common tips==<br />
===Initializing/Resetting Murmur password===<br />
Type:<br />
murmur -supw <password><br />
That will change the password for SuperUser, a special user that has all rights.<br />
If you want to reset the entire database, just delete murmur.sqlite and the recreate it with the command above.<br />
<br />
==Windows==<br />
===Text-to-Speech===<br />
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 [http://www.nextup.com NextUp]).<br />
<br />
===Creating a server connection shortcut===<br />
You can right click on your desktop and choose "New" and pick "Shortcut" from the sub-menu.<br />
In the box that says "Type the location of the item" put "mumble://username:password@servername/channel"<br />
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. <br />
<br />
===It complains about mumble_ol.dll / Problems with Overlay===<br />
If you are running XP you will need to update it to SP2.<br />
<br />
=== Murmur dies when I log out! How can I get Murmur to stay on all the time? ===<br />
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.<br />
<br />
Some references you'll see int his write-up:<br />
<br />
instsrv.exe - A program that adds services to the Windows registry.<br />
<br />
srvany.exe - A program that allows any Windows application and some Windows 16-bit applications to run as a service.<br />
<br />
'''The HOW-TO'''<br />
<br />
Step 1: Gain Administrator access on the machine running Murmur.<br />
<br />
Step 2: Download and install the following collection of tools from Microsoft to the default directory (C:\Program Files\Windows Resource Kits):<br />
<br />
[http://www.microsoft.com/downloads/details.aspx?FamilyID=9d467a69-57ff-4ae7-96ee-b18c4790cffd&displaylang=en Windows 2003 Server Resource Kit].<br />
<br />
Step 3: Open a command console (Start >> Accessories >> Command Prompt).<br />
<br />
Step 4: If you have installed to the default directory, type the following:<br />
<br />
"C:\Program Files\Windows Resource Kits\Tools\instsrv.exe" "Murmur" "C:\Program Files\Windows Resource Kits\Tools\srvany.exe"<br />
<br />
The result of this step is a new service in the Services console (Start >> Control Panel >> Administrative Tools >> Services).<br />
<br />
'''Be sure to close the Services console before proceeding.'''<br />
<br />
Step 5: Open the registry editor (Start >> Run and enter "regedit") and navigate to the following key:<br />
<br />
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Murmur Demo<br />
<br />
<br />
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.<br />
<br />
Step 7: Name this new key "Parameters"<br />
<br />
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.<br />
<br />
Step 9: Name this new String value "Application".<br />
<br />
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.<br />
<br />
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.<br />
<br />
Step 11: Close Regedit<br />
<br />
Step 12: Open the Services console. Navigate to your service, and right click it and select Properties.<br />
<br />
Step 13: Make sure the Startup Type value is Automatic, and then press the Start button.<br />
<br />
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.<br />
<br />
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.<br />
<br />
If your server did not start, recheck your settings. Most problems are related to typos in configuration settings.<br />
<br />
==Linux==<br />
===Getting the Shortcuts Suppression to work===<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 />
=Uninstalling=<br />
[[UninstallingMumble | Instructions for completely removing Mumble, including user created settings and entries.]]</div>Haudraufhttps://wiki.mumble.info/index.php?title=BuildingLinux&diff=2510BuildingLinux2009-01-16T17:14:34Z<p>Haudrauf: /* For Gentoo */</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<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>Haudraufhttps://wiki.mumble.info/index.php?title=BuildingLinux&diff=2321BuildingLinux2008-09-04T19:04:06Z<p>Haudrauf: /* Murmur (server) dependencies */</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 />
<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<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>Haudraufhttps://wiki.mumble.info/index.php?title=BuildingLinux&diff=2320BuildingLinux2008-09-04T19:03:43Z<p>Haudrauf: /* For Gentoo */</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 />
<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 />
<br />
<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 />
=== 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<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>Haudraufhttps://wiki.mumble.info/index.php?title=BuildingLinux&diff=2319BuildingLinux2008-09-04T18:58:55Z<p>Haudrauf: /* Compile Mumble and Murmur (Mumble server) */ murmur only..</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 />
<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 />
=== 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<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>Haudraufhttps://wiki.mumble.info/index.php?title=BuildingLinux&diff=2318BuildingLinux2008-09-04T18:56:19Z<p>Haudrauf: /* For Gentoo */ speex version adjustment for latest portage tree</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 />
<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 />
=== 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<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 />
Alternatively, if you are using Debian/Ubuntu with both Qt3 and Qt4 installed:<br />
<br />
qmake-qt4 main.pro<br />
make<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>Haudraufhttps://wiki.mumble.info/index.php?title=Installing_Mumble&diff=2088Installing Mumble2008-05-18T18:18:52Z<p>Haudrauf: /* Linux */</p>
<hr />
<div>=Getting and Installing Mumble=<br />
==Windows==<br />
Just head to [http://sourceforge.net/project/showfiles.php?group_id=147372 SourceForge downloads page], get the Windows executable and run it. Follow the installer instructions and you are done.<br />
<br />
Also, you can build Mumble yourself from source as described in [[BuildingWindows]].<br />
<br />
==Linux==<br />
Some Linux distributions already have mumble packaged so that an easy installation is possible. Check your package manager of your distribution for mumble. But sometimes those packages are not up to date. So if you want more in-depth information about installing mumble for Linux read up on [[BuildingLinux]]. Installation from source (svn and tarball) is described there.<br />
<br />
The following are instructions for installing mumble with the package managers of the various distributions.<br />
<br />
===Ubuntu ===<br />
<br />
In hardy, the 1.1.X series is included, so just<br />
apt-get install mumble mumble-server<br />
<br />
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 [http://sourceforge.net/project/showfiles.php?group_id=147372 SourceForge] and install it with your package manager. <br />
<br />
Alternately you can use the PPA for mumble builds, which can be found at [https://edge.launchpad.net/~slicer/+archive 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.<br />
<br />
===Fedora===<br />
Fedora 7 RPMs: [http://koji.fedoraproject.org/koji/getfile?taskID=227582&name=mumble-1.1.0-1.fc7.i386.rpm 1.1.0 i386] [http://koji.fedoraproject.org/koji/getfile?taskID=227581&name=mumble-1.1.0-1.fc7.x86_64.rpm 1.1.0 x86_64]<br />
Fedora 8 RPMs: [http://koji.fedoraproject.org/koji/getfile?taskID=231652&name=mumble-1.1.0-2.fc8.i386.rpm 1.1.0 i386] [http://koji.fedoraproject.org/koji/getfile?taskID=231651&name=mumble-1.1.0-2.fc8.x86_64.rpm 1.1.0 x86_64]<br />
<br />
Install them via double click.<br />
===PCLinuxOS and other RPM based distros===<br />
You can find a rpm package in the [http://sourceforge.net/forum/forum.php?thread_id=1782689&forum_id=492606 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):<br />
<br />
rpm -i mumble-1.0.0-2.i386.rpm<br />
<br />
===Gentoo===<br />
Become root and do:<br />
emerge -av mumble<br />
That should do the magic. If something fails though, check up on [[BuildingLinux]]<br />
<br />
===ArchLinux===<br />
A PKGBUILD is avalaible in the [http://aur.archlinux.org/packages.php?do_Details=1&ID=10221&K=mumble AUR]. Download the tarball and then run:<br />
tar xzfv mumble.tar.gz<br />
cd mumble<br />
makepkg<br />
<br />
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:<br />
<br />
pacman -S alsa-lib qt4 libxevie sqlite3 boost<br />
<br />
Finally, install the package:<br />
<br />
pacman -A mumble-1.0.0-1.pkg.tar.gz<br />
<br />
Of course, replace the package name as appropriate.<br />
<br />
==Mac OS X==<br />
Precompiled Mac OS X universal binaries are available from the [http://sourceforge.net/project/showfiles.php?group_id=147372 SourceForge downloads page].<br />
<br />
You can also build it from source yourself if you wish. See [[BuildingMacOsX]] for more information.<br />
<br />
=Post-installation tips=<br />
==Common tips==<br />
===Initializing/Resetting Murmur password===<br />
Type:<br />
murmur -supw <password><br />
That will change the password for SuperUser, a special user that has all rights.<br />
If you want to reset the entire database, just delete murmur.sqlite and the recreate it with the command above.<br />
<br />
==Windows==<br />
===Text-to-Speech===<br />
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 [http://www.nextup.com NextUp]).<br />
<br />
===Creating a server connection shortcut===<br />
You can right click on your desktop and choose "New" and pick "Shortcut" from the sub-menu.<br />
In the box that says "Type the location of the item" put "mumble://username:password@servername/channel"<br />
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. <br />
<br />
===It complains about mumble_ol.dll / Problems with Overlay===<br />
If you are running XP you will need to update it to SP2. You also need to update to the latest DirectX9 version that can be downloaded from the [http://www.microsoft.com/downloads/details.aspx?FamilyId=2DA43D38-DB71-4C1B-BC6A-9B6652CD92A3&displaylang=en Microsoft site]. The [http://www.microsoft.com/downloads/details.aspx?FamilyID=b406cf67-d926-463b-99e8-27199d6626b5&DisplayLang=en June 2007 version] should be enough.<br />
<br />
=== Murmur dies when I log out! How can I get Murmur to stay on all the time? ===<br />
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.<br />
<br />
Some references you'll see int his write-up:<br />
<br />
instsrv.exe - A program that adds services to the Windows registry.<br />
<br />
srvany.exe - A program that allows any Windows application and some Windows 16-bit applications to run as a service.<br />
<br />
'''The HOW-TO'''<br />
<br />
Step 1: Gain Administrator access on the machine running Murmur.<br />
<br />
Step 2: Download and install the following collection of tools from Microsoft to the default directory (C:\Program Files\Windows Resource Kits):<br />
<br />
[http://www.microsoft.com/downloads/details.aspx?FamilyID=9d467a69-57ff-4ae7-96ee-b18c4790cffd&displaylang=en Windows 2003 Server Resource Kit].<br />
<br />
Step 3: Open a command console (Start >> Accessories >> Command Prompt).<br />
<br />
Step 4: If you have installed to the default directory, type the following:<br />
<br />
"C:\Program Files\Windows Resource Kits\Tools\instsrv.exe" "Murmur" "C:\Program Files\Windows Resource Kits\Tools\srvany.exe"<br />
<br />
Below is an example of what you should see:<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/command.jpg<br />
<br />
The result of this step is a new service in the Services console (Start >> Control Panel >> Administrative Tools >> Services).<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/service.jpg<br />
<br />
'''Be sure to close the Services console before proceeding.'''<br />
<br />
Step 5: Open the registry editor (Start >> Run and enter "regedit") and navigate to the following key:<br />
<br />
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Murmur Demo<br />
<br />
Regedit should look something like this:<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/regedit.jpg<br />
<br />
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.<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/newkey.jpg<br />
<br />
Step 7: Name this new key "Parameters"<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/parameters.jpg<br />
<br />
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.<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/newstring.jpg<br />
<br />
Step 9: Name this new String value "Application".<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/application.jpg<br />
<br />
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.<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/editapplication.jpg<br />
<br />
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:<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/final.jpg<br />
<br />
Step 11: Close Regedit<br />
<br />
Step 12: Open the Services console. Navigate to your service, and right click it and select Properties.<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/panel.jpg<br />
<br />
Step 13: Make sure the Startup Type value is Automatic, and then press the Start button.<br />
<br />
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.<br />
<br />
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.<br />
<br />
If your server did not start, recheck your settings. Most problems are related to typos in configuration settings.<br />
<br />
==Linux==<br />
===Getting the Shortcuts to work===<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 />
'''Note:''' As of Mumble 1.1.4 neither Xevie nor access to /dev/input is needed anymore. Push To Talk shortcuts will work out of the box.<br />
<br />
===Running murmur as a SysV service===<br />
You can use [[Murmur_Init_Script]].</div>Haudraufhttps://wiki.mumble.info/index.php?title=BuildingLinux&diff=2087BuildingLinux2008-05-18T18:11:36Z<p>Haudrauf: /* For Gentoo */</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. For the 1.0.0 release, Qt 4.2 is sufficient.<br />
<br />
=== For Gentoo ===<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_p2" 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 />
=== 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 />
== Installing from source ==<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 />
<br />
svn co https://mumble.svn.sourceforge.net/svnroot/mumble/trunk mumble<br />
cd mumble/<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 />
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 />
'''Note''': If you use Mumble 1.1.4 or newer, you don't need to enable Xevie or allow access to /dev/input. PushToTalk will work out of the box.<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 />
[[Link title]]<br />
<br />
== Run Mumble ==<br />
<br />
cd release<br />
./mumble<br />
<br />
== Run Murmur ==<br />
<br />
* see [[Running Murmur]]<br />
<br />
[[Category:Development]]</div>Haudraufhttps://wiki.mumble.info/index.php?title=BuildingLinux&diff=2086BuildingLinux2008-05-18T18:10:40Z<p>Haudrauf: /* For Gentoo */</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. For the 1.0.0 release, Qt 4.2 is sufficient.<br />
<br />
=== For Gentoo ===<br />
<br />
Qt4 needs to be built with certain use flags: dbus, 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_p2" 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 />
=== 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 />
== Installing from source ==<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 />
<br />
svn co https://mumble.svn.sourceforge.net/svnroot/mumble/trunk mumble<br />
cd mumble/<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 />
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 />
'''Note''': If you use Mumble 1.1.4 or newer, you don't need to enable Xevie or allow access to /dev/input. PushToTalk will work out of the box.<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 />
[[Link title]]<br />
<br />
== Run Mumble ==<br />
<br />
cd release<br />
./mumble<br />
<br />
== Run Murmur ==<br />
<br />
* see [[Running Murmur]]<br />
<br />
[[Category:Development]]</div>Haudraufhttps://wiki.mumble.info/index.php?title=BuildingLinux&diff=2081BuildingLinux2008-05-18T17:52:19Z<p>Haudrauf: /* Installing from source */</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. For the 1.0.0 release, Qt 4.2 is sufficient.<br />
<br />
=== For Gentoo ===<br />
<br />
If Qt4 is missing the sqlite use flags, then re-install Qt4 with sqlite features:<br />
echo x11-libs/qt dbus sqlite 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_p2" 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 />
<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 />
== Installing from source ==<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 />
<br />
svn co https://mumble.svn.sourceforge.net/svnroot/mumble/trunk mumble<br />
cd mumble/<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 />
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 />
[[Link title]]<br />
<br />
== Run Mumble ==<br />
<br />
cd release<br />
./mumble<br />
<br />
== Run Murmur ==<br />
<br />
* see [[Running Murmur]]<br />
<br />
[[Category:Development]]</div>Haudraufhttps://wiki.mumble.info/index.php?title=BuildingLinux&diff=2080BuildingLinux2008-05-18T17:50:23Z<p>Haudrauf: /* Text to Speech */</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. For the 1.0.0 release, Qt 4.2 is sufficient.<br />
<br />
=== For Gentoo ===<br />
<br />
If Qt4 is missing the sqlite use flags, then re-install Qt4 with sqlite features:<br />
echo x11-libs/qt dbus sqlite 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_p2" 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 />
<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 />
== Installing from source ==<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 />
<br />
svn co https://mumble.svn.sourceforge.net/svnroot/mumble/trunk mumble<br />
cd mumble/<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 />
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 />
[[Link title]]<br />
<br />
== Run Mumble ==<br />
<br />
cd release<br />
./mumble<br />
<br />
== Run Murmur ==<br />
<br />
* see [[Running Murmur]]<br />
<br />
[[Category:Development]]</div>Haudraufhttps://wiki.mumble.info/index.php?title=BuildingLinux&diff=2079BuildingLinux2008-05-18T17:50:13Z<p>Haudrauf: /* Push to talk */</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. For the 1.0.0 release, Qt 4.2 is sufficient.<br />
<br />
=== For Gentoo ===<br />
<br />
If Qt4 is missing the sqlite use flags, then re-install Qt4 with sqlite features:<br />
echo x11-libs/qt dbus sqlite 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_p2" 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 />
<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 />
== Installing from source ==<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 />
<br />
svn co https://mumble.svn.sourceforge.net/svnroot/mumble/trunk mumble<br />
cd mumble/<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 />
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 />
[[Link title]]<br />
<br />
== Run Mumble ==<br />
<br />
cd release<br />
./mumble<br />
<br />
== Run Murmur ==<br />
<br />
* see [[Running Murmur]]<br />
<br />
[[Category:Development]]</div>Haudraufhttps://wiki.mumble.info/index.php?title=BuildingLinux&diff=2078BuildingLinux2008-05-18T17:49:40Z<p>Haudrauf: /* Compiling from source */</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. For the 1.0.0 release, Qt 4.2 is sufficient.<br />
<br />
=== For Gentoo ===<br />
<br />
If Qt4 is missing the sqlite use flags, then re-install Qt4 with sqlite features:<br />
echo x11-libs/qt dbus sqlite 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_p2" 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 />
<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 />
== Installing from source ==<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 />
<br />
svn co https://mumble.svn.sourceforge.net/svnroot/mumble/trunk mumble<br />
cd mumble/<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 />
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 />
[[Link title]]<br />
<br />
== Run Mumble ==<br />
<br />
cd release<br />
./mumble<br />
<br />
== Run Murmur ==<br />
<br />
* see [[Running Murmur]]<br />
<br />
[[Category:Development]]</div>Haudraufhttps://wiki.mumble.info/index.php?title=BuildingLinux&diff=2077BuildingLinux2008-05-18T17:49:24Z<p>Haudrauf: /* Installing from source */</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. For the 1.0.0 release, Qt 4.2 is sufficient.<br />
<br />
=== For Gentoo ===<br />
<br />
If Qt4 is missing the sqlite use flags, then re-install Qt4 with sqlite features:<br />
echo x11-libs/qt dbus sqlite 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_p2" 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 />
<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 />
== Compiling from source ==<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 />
<br />
svn co https://mumble.svn.sourceforge.net/svnroot/mumble/trunk mumble<br />
cd mumble/<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 />
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 />
[[Link title]]<br />
<br />
== Run Mumble ==<br />
<br />
cd release<br />
./mumble<br />
<br />
== Run Murmur ==<br />
<br />
* see [[Running Murmur]]<br />
<br />
[[Category:Development]]</div>Haudraufhttps://wiki.mumble.info/index.php?title=BuildingLinux&diff=2076BuildingLinux2008-05-18T17:47:09Z<p>Haudrauf: /* Compile Mumble and Murmur (Mumble server) */</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. For the 1.0.0 release, Qt 4.2 is sufficient.<br />
<br />
=== For Gentoo ===<br />
<br />
If Qt4 is missing the sqlite use flags, then re-install Qt4 with sqlite features:<br />
echo x11-libs/qt dbus sqlite 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_p2" 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 />
<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 />
== Installing from source ==<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 />
<br />
svn co https://mumble.svn.sourceforge.net/svnroot/mumble/trunk mumble<br />
cd mumble/<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 />
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>Haudraufhttps://wiki.mumble.info/index.php?title=BuildingLinux&diff=2075BuildingLinux2008-05-18T17:46:43Z<p>Haudrauf: /* tarball release */</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. For the 1.0.0 release, Qt 4.2 is sufficient.<br />
<br />
=== For Gentoo ===<br />
<br />
If Qt4 is missing the sqlite use flags, then re-install Qt4 with sqlite features:<br />
echo x11-libs/qt dbus sqlite 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_p2" 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 />
<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 />
== Installing from source ==<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 />
<br />
svn co https://mumble.svn.sourceforge.net/svnroot/mumble/trunk mumble<br />
cd mumble/<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 />
<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>Haudraufhttps://wiki.mumble.info/index.php?title=BuildingLinux&diff=2074BuildingLinux2008-05-18T17:45:47Z<p>Haudrauf: </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. For the 1.0.0 release, Qt 4.2 is sufficient.<br />
<br />
=== For Gentoo ===<br />
<br />
If Qt4 is missing the sqlite use flags, then re-install Qt4 with sqlite features:<br />
echo x11-libs/qt dbus sqlite 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_p2" 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 />
<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 />
== Installing from source ==<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 />
<br />
svn co https://mumble.svn.sourceforge.net/svnroot/mumble/trunk mumble<br />
cd mumble/<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 />
Be sure to have everything installed and in place for your linux distribution (see the sections above)<br />
<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>Haudraufhttps://wiki.mumble.info/index.php?title=BuildingLinux&diff=2073BuildingLinux2008-05-18T17:45:28Z<p>Haudrauf: /* Install from source */</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 />
If Qt4 is missing the sqlite use flags, then re-install Qt4 with sqlite features:<br />
echo x11-libs/qt dbus sqlite 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_p2" 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 />
<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 />
== Installing from source ==<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 />
<br />
svn co https://mumble.svn.sourceforge.net/svnroot/mumble/trunk mumble<br />
cd mumble/<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 />
Be sure to have everything installed and in place for your linux distribution (see the sections above)<br />
<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>Haudraufhttps://wiki.mumble.info/index.php?title=BuildingLinux&diff=2072BuildingLinux2008-05-18T17:45:04Z<p>Haudrauf: </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 />
If Qt4 is missing the sqlite use flags, then re-install Qt4 with sqlite features:<br />
echo x11-libs/qt dbus sqlite 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_p2" 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 />
<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 />
== Install from source ==<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 />
<br />
svn co https://mumble.svn.sourceforge.net/svnroot/mumble/trunk mumble<br />
cd mumble/<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 />
Be sure to have everything installed and in place for your linux distribution (see the sections above)<br />
<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>Haudraufhttps://wiki.mumble.info/index.php?title=Installing_Mumble&diff=2071Installing Mumble2008-05-18T17:36:34Z<p>Haudrauf: /* Linux */</p>
<hr />
<div>=Getting and Installing Mumble=<br />
==Windows==<br />
Just head to [http://sourceforge.net/project/showfiles.php?group_id=147372 SourceForge downloads page], get the Windows executable and run it. Follow the installer instructions and you are done.<br />
<br />
Also, you can build Mumble yourself from source as described in [[BuildingWindows]].<br />
<br />
==Linux==<br />
Some Linux distributions already have mumble packaged so that an easy installation is possible. Check your package manager of your distribution for mumble.<br />
<br />
But sometimes those packages are not up to date. So if you want more in-depth information about installing mumble for Linux read up on [[BuildingLinux]]. Installation from source (svn and tarball) is also described there.<br />
<br />
===Ubuntu ===<br />
<br />
In hardy, the 1.1.X series is included, so just<br />
apt-get install mumble mumble-server<br />
<br />
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 [http://sourceforge.net/project/showfiles.php?group_id=147372 SourceForge] and install it with your package manager. <br />
<br />
Alternately you can use the PPA for mumble builds, which can be found at [https://edge.launchpad.net/~slicer/+archive 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.<br />
<br />
===Fedora===<br />
Fedora 7 RPMs: [http://koji.fedoraproject.org/koji/getfile?taskID=227582&name=mumble-1.1.0-1.fc7.i386.rpm 1.1.0 i386] [http://koji.fedoraproject.org/koji/getfile?taskID=227581&name=mumble-1.1.0-1.fc7.x86_64.rpm 1.1.0 x86_64]<br />
Fedora 8 RPMs: [http://koji.fedoraproject.org/koji/getfile?taskID=231652&name=mumble-1.1.0-2.fc8.i386.rpm 1.1.0 i386] [http://koji.fedoraproject.org/koji/getfile?taskID=231651&name=mumble-1.1.0-2.fc8.x86_64.rpm 1.1.0 x86_64]<br />
<br />
Install them via double click.<br />
===PCLinuxOS and other RPM based distros===<br />
You can find a rpm package in the [http://sourceforge.net/forum/forum.php?thread_id=1782689&forum_id=492606 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):<br />
<br />
rpm -i mumble-1.0.0-2.i386.rpm<br />
<br />
===Gentoo===<br />
Become root and do:<br />
emerge -av mumble<br />
That should do the magic. If something fails though, check up on [[BuildingLinux]]<br />
<br />
===ArchLinux===<br />
A PKGBUILD is avalaible in the [http://aur.archlinux.org/packages.php?do_Details=1&ID=10221&K=mumble AUR]. Download the tarball and then run:<br />
tar xzfv mumble.tar.gz<br />
cd mumble<br />
makepkg<br />
<br />
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:<br />
<br />
pacman -S alsa-lib qt4 libxevie sqlite3 boost<br />
<br />
Finally, install the package:<br />
<br />
pacman -A mumble-1.0.0-1.pkg.tar.gz<br />
<br />
Of course, replace the package name as appropriate.<br />
<br />
==Mac OS X==<br />
Precompiled Mac OS X universal binaries are available from the [http://sourceforge.net/project/showfiles.php?group_id=147372 SourceForge downloads page].<br />
<br />
You can also build it from source yourself if you wish. See [[BuildingMacOsX]] for more information.<br />
<br />
=Post-installation tips=<br />
==Common tips==<br />
===Initializing/Resetting Murmur password===<br />
Type:<br />
murmur -supw <password><br />
That will change the password for SuperUser, a special user that has all rights.<br />
If you want to reset the entire database, just delete murmur.sqlite and the recreate it with the command above.<br />
<br />
==Windows==<br />
===Text-to-Speech===<br />
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 [http://www.nextup.com NextUp]).<br />
<br />
===Creating a server connection shortcut===<br />
You can right click on your desktop and choose "New" and pick "Shortcut" from the sub-menu.<br />
In the box that says "Type the location of the item" put "mumble://username:password@servername/channel"<br />
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. <br />
<br />
===It complains about mumble_ol.dll / Problems with Overlay===<br />
If you are running XP you will need to update it to SP2. You also need to update to the latest DirectX9 version that can be downloaded from the [http://www.microsoft.com/downloads/details.aspx?FamilyId=2DA43D38-DB71-4C1B-BC6A-9B6652CD92A3&displaylang=en Microsoft site]. The [http://www.microsoft.com/downloads/details.aspx?FamilyID=b406cf67-d926-463b-99e8-27199d6626b5&DisplayLang=en June 2007 version] should be enough.<br />
<br />
=== Murmur dies when I log out! How can I get Murmur to stay on all the time? ===<br />
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.<br />
<br />
Some references you'll see int his write-up:<br />
<br />
instsrv.exe - A program that adds services to the Windows registry.<br />
<br />
srvany.exe - A program that allows any Windows application and some Windows 16-bit applications to run as a service.<br />
<br />
'''The HOW-TO'''<br />
<br />
Step 1: Gain Administrator access on the machine running Murmur.<br />
<br />
Step 2: Download and install the following collection of tools from Microsoft to the default directory (C:\Program Files\Windows Resource Kits):<br />
<br />
[http://www.microsoft.com/downloads/details.aspx?FamilyID=9d467a69-57ff-4ae7-96ee-b18c4790cffd&displaylang=en Windows 2003 Server Resource Kit].<br />
<br />
Step 3: Open a command console (Start >> Accessories >> Command Prompt).<br />
<br />
Step 4: If you have installed to the default directory, type the following:<br />
<br />
"C:\Program Files\Windows Resource Kits\Tools\instsrv.exe" "Murmur" "C:\Program Files\Windows Resource Kits\Tools\srvany.exe"<br />
<br />
Below is an example of what you should see:<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/command.jpg<br />
<br />
The result of this step is a new service in the Services console (Start >> Control Panel >> Administrative Tools >> Services).<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/service.jpg<br />
<br />
'''Be sure to close the Services console before proceeding.'''<br />
<br />
Step 5: Open the registry editor (Start >> Run and enter "regedit") and navigate to the following key:<br />
<br />
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Murmur Demo<br />
<br />
Regedit should look something like this:<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/regedit.jpg<br />
<br />
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.<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/newkey.jpg<br />
<br />
Step 7: Name this new key "Parameters"<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/parameters.jpg<br />
<br />
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.<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/newstring.jpg<br />
<br />
Step 9: Name this new String value "Application".<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/application.jpg<br />
<br />
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.<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/editapplication.jpg<br />
<br />
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:<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/final.jpg<br />
<br />
Step 11: Close Regedit<br />
<br />
Step 12: Open the Services console. Navigate to your service, and right click it and select Properties.<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/panel.jpg<br />
<br />
Step 13: Make sure the Startup Type value is Automatic, and then press the Start button.<br />
<br />
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.<br />
<br />
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.<br />
<br />
If your server did not start, recheck your settings. Most problems are related to typos in configuration settings.<br />
<br />
==Linux==<br />
===Getting the Shortcuts to work===<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 />
===Running murmur as a SysV service===<br />
You can use [[Murmur_Init_Script]].</div>Haudraufhttps://wiki.mumble.info/index.php?title=Installing_Mumble&diff=2070Installing Mumble2008-05-18T17:34:54Z<p>Haudrauf: /* Linux */</p>
<hr />
<div>=Getting and Installing Mumble=<br />
==Windows==<br />
Just head to [http://sourceforge.net/project/showfiles.php?group_id=147372 SourceForge downloads page], get the Windows executable and run it. Follow the installer instructions and you are done.<br />
<br />
Also, you can build Mumble yourself from source as described in [[BuildingWindows]].<br />
<br />
==Linux==<br />
Some Linux distributions already have mumble packaged so that an easy installation is possible. Check your package manager of your distribution for mumble.<br />
<br />
But sometimes those packages are not up to date. So if you want more in-depth information about installing mumble for Linux read up on [[BuildingLinux]].<br />
<br />
===Ubuntu ===<br />
<br />
In hardy, the 1.1.X series is included, so just<br />
apt-get install mumble mumble-server<br />
<br />
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 [http://sourceforge.net/project/showfiles.php?group_id=147372 SourceForge] and install it with your package manager. <br />
<br />
Alternately you can use the PPA for mumble builds, which can be found at [https://edge.launchpad.net/~slicer/+archive 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.<br />
<br />
===Fedora===<br />
Fedora 7 RPMs: [http://koji.fedoraproject.org/koji/getfile?taskID=227582&name=mumble-1.1.0-1.fc7.i386.rpm 1.1.0 i386] [http://koji.fedoraproject.org/koji/getfile?taskID=227581&name=mumble-1.1.0-1.fc7.x86_64.rpm 1.1.0 x86_64]<br />
Fedora 8 RPMs: [http://koji.fedoraproject.org/koji/getfile?taskID=231652&name=mumble-1.1.0-2.fc8.i386.rpm 1.1.0 i386] [http://koji.fedoraproject.org/koji/getfile?taskID=231651&name=mumble-1.1.0-2.fc8.x86_64.rpm 1.1.0 x86_64]<br />
<br />
Install them via double click.<br />
===PCLinuxOS and other RPM based distros===<br />
You can find a rpm package in the [http://sourceforge.net/forum/forum.php?thread_id=1782689&forum_id=492606 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):<br />
<br />
rpm -i mumble-1.0.0-2.i386.rpm<br />
<br />
===Gentoo===<br />
Become root and do:<br />
emerge -av mumble<br />
That should do the magic. If something fails though, check up on [[BuildingLinux]]<br />
<br />
===ArchLinux===<br />
A PKGBUILD is avalaible in the [http://aur.archlinux.org/packages.php?do_Details=1&ID=10221&K=mumble AUR]. Download the tarball and then run:<br />
tar xzfv mumble.tar.gz<br />
cd mumble<br />
makepkg<br />
<br />
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:<br />
<br />
pacman -S alsa-lib qt4 libxevie sqlite3 boost<br />
<br />
Finally, install the package:<br />
<br />
pacman -A mumble-1.0.0-1.pkg.tar.gz<br />
<br />
Of course, replace the package name as appropriate.<br />
<br />
===Installing from source===<br />
The most generic approach to install mumble under any linux is to install from source. Download the tarball and then run:<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 />
Read the linux specific entries in the INSTALL file, since there you get to know about the pre-requisites needed for compilation. Be sure to have everything installed and in place for your linux distribution.<br />
<br />
Then run:<br />
qmake main.pro<br />
make<br />
<br />
After the compilation is finished, you will find the binaries in the directory "release". To run it there:<br />
cd release<br />
./mumble<br />
<br />
==Mac OS X==<br />
Precompiled Mac OS X universal binaries are available from the [http://sourceforge.net/project/showfiles.php?group_id=147372 SourceForge downloads page].<br />
<br />
You can also build it from source yourself if you wish. See [[BuildingMacOsX]] for more information.<br />
<br />
=Post-installation tips=<br />
==Common tips==<br />
===Initializing/Resetting Murmur password===<br />
Type:<br />
murmur -supw <password><br />
That will change the password for SuperUser, a special user that has all rights.<br />
If you want to reset the entire database, just delete murmur.sqlite and the recreate it with the command above.<br />
<br />
==Windows==<br />
===Text-to-Speech===<br />
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 [http://www.nextup.com NextUp]).<br />
<br />
===Creating a server connection shortcut===<br />
You can right click on your desktop and choose "New" and pick "Shortcut" from the sub-menu.<br />
In the box that says "Type the location of the item" put "mumble://username:password@servername/channel"<br />
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. <br />
<br />
===It complains about mumble_ol.dll / Problems with Overlay===<br />
If you are running XP you will need to update it to SP2. You also need to update to the latest DirectX9 version that can be downloaded from the [http://www.microsoft.com/downloads/details.aspx?FamilyId=2DA43D38-DB71-4C1B-BC6A-9B6652CD92A3&displaylang=en Microsoft site]. The [http://www.microsoft.com/downloads/details.aspx?FamilyID=b406cf67-d926-463b-99e8-27199d6626b5&DisplayLang=en June 2007 version] should be enough.<br />
<br />
=== Murmur dies when I log out! How can I get Murmur to stay on all the time? ===<br />
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.<br />
<br />
Some references you'll see int his write-up:<br />
<br />
instsrv.exe - A program that adds services to the Windows registry.<br />
<br />
srvany.exe - A program that allows any Windows application and some Windows 16-bit applications to run as a service.<br />
<br />
'''The HOW-TO'''<br />
<br />
Step 1: Gain Administrator access on the machine running Murmur.<br />
<br />
Step 2: Download and install the following collection of tools from Microsoft to the default directory (C:\Program Files\Windows Resource Kits):<br />
<br />
[http://www.microsoft.com/downloads/details.aspx?FamilyID=9d467a69-57ff-4ae7-96ee-b18c4790cffd&displaylang=en Windows 2003 Server Resource Kit].<br />
<br />
Step 3: Open a command console (Start >> Accessories >> Command Prompt).<br />
<br />
Step 4: If you have installed to the default directory, type the following:<br />
<br />
"C:\Program Files\Windows Resource Kits\Tools\instsrv.exe" "Murmur" "C:\Program Files\Windows Resource Kits\Tools\srvany.exe"<br />
<br />
Below is an example of what you should see:<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/command.jpg<br />
<br />
The result of this step is a new service in the Services console (Start >> Control Panel >> Administrative Tools >> Services).<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/service.jpg<br />
<br />
'''Be sure to close the Services console before proceeding.'''<br />
<br />
Step 5: Open the registry editor (Start >> Run and enter "regedit") and navigate to the following key:<br />
<br />
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Murmur Demo<br />
<br />
Regedit should look something like this:<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/regedit.jpg<br />
<br />
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.<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/newkey.jpg<br />
<br />
Step 7: Name this new key "Parameters"<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/parameters.jpg<br />
<br />
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.<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/newstring.jpg<br />
<br />
Step 9: Name this new String value "Application".<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/application.jpg<br />
<br />
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.<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/editapplication.jpg<br />
<br />
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:<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/final.jpg<br />
<br />
Step 11: Close Regedit<br />
<br />
Step 12: Open the Services console. Navigate to your service, and right click it and select Properties.<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/panel.jpg<br />
<br />
Step 13: Make sure the Startup Type value is Automatic, and then press the Start button.<br />
<br />
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.<br />
<br />
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.<br />
<br />
If your server did not start, recheck your settings. Most problems are related to typos in configuration settings.<br />
<br />
==Linux==<br />
===Getting the Shortcuts to work===<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 />
===Running murmur as a SysV service===<br />
You can use [[Murmur_Init_Script]].</div>Haudraufhttps://wiki.mumble.info/index.php?title=Installing_Mumble&diff=2069Installing Mumble2008-05-18T17:24:31Z<p>Haudrauf: /* Linux */</p>
<hr />
<div>=Getting and Installing Mumble=<br />
==Windows==<br />
Just head to [http://sourceforge.net/project/showfiles.php?group_id=147372 SourceForge downloads page], get the Windows executable and run it. Follow the installer instructions and you are done.<br />
<br />
Also, you can build Mumble yourself from source as described in [[BuildingWindows]].<br />
<br />
==Linux==<br />
Some Linux distributions already have mumble packaged so that an easy installation is possible. Check your package manager of your distribution for mumble.<br />
<br />
But sometimes those packages are not up to date. So if you want more in-depth information about installing mumble for Linux read up on [[BuildingLinux]].<br />
<br />
==Mac OS X==<br />
Precompiled Mac OS X universal binaries are available from the [http://sourceforge.net/project/showfiles.php?group_id=147372 SourceForge downloads page].<br />
<br />
You can also build it from source yourself if you wish. See [[BuildingMacOsX]] for more information.<br />
<br />
=Post-installation tips=<br />
==Common tips==<br />
===Initializing/Resetting Murmur password===<br />
Type:<br />
murmur -supw <password><br />
That will change the password for SuperUser, a special user that has all rights.<br />
If you want to reset the entire database, just delete murmur.sqlite and the recreate it with the command above.<br />
<br />
==Windows==<br />
===Text-to-Speech===<br />
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 [http://www.nextup.com NextUp]).<br />
<br />
===Creating a server connection shortcut===<br />
You can right click on your desktop and choose "New" and pick "Shortcut" from the sub-menu.<br />
In the box that says "Type the location of the item" put "mumble://username:password@servername/channel"<br />
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. <br />
<br />
===It complains about mumble_ol.dll / Problems with Overlay===<br />
If you are running XP you will need to update it to SP2. You also need to update to the latest DirectX9 version that can be downloaded from the [http://www.microsoft.com/downloads/details.aspx?FamilyId=2DA43D38-DB71-4C1B-BC6A-9B6652CD92A3&displaylang=en Microsoft site]. The [http://www.microsoft.com/downloads/details.aspx?FamilyID=b406cf67-d926-463b-99e8-27199d6626b5&DisplayLang=en June 2007 version] should be enough.<br />
<br />
=== Murmur dies when I log out! How can I get Murmur to stay on all the time? ===<br />
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.<br />
<br />
Some references you'll see int his write-up:<br />
<br />
instsrv.exe - A program that adds services to the Windows registry.<br />
<br />
srvany.exe - A program that allows any Windows application and some Windows 16-bit applications to run as a service.<br />
<br />
'''The HOW-TO'''<br />
<br />
Step 1: Gain Administrator access on the machine running Murmur.<br />
<br />
Step 2: Download and install the following collection of tools from Microsoft to the default directory (C:\Program Files\Windows Resource Kits):<br />
<br />
[http://www.microsoft.com/downloads/details.aspx?FamilyID=9d467a69-57ff-4ae7-96ee-b18c4790cffd&displaylang=en Windows 2003 Server Resource Kit].<br />
<br />
Step 3: Open a command console (Start >> Accessories >> Command Prompt).<br />
<br />
Step 4: If you have installed to the default directory, type the following:<br />
<br />
"C:\Program Files\Windows Resource Kits\Tools\instsrv.exe" "Murmur" "C:\Program Files\Windows Resource Kits\Tools\srvany.exe"<br />
<br />
Below is an example of what you should see:<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/command.jpg<br />
<br />
The result of this step is a new service in the Services console (Start >> Control Panel >> Administrative Tools >> Services).<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/service.jpg<br />
<br />
'''Be sure to close the Services console before proceeding.'''<br />
<br />
Step 5: Open the registry editor (Start >> Run and enter "regedit") and navigate to the following key:<br />
<br />
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Murmur Demo<br />
<br />
Regedit should look something like this:<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/regedit.jpg<br />
<br />
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.<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/newkey.jpg<br />
<br />
Step 7: Name this new key "Parameters"<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/parameters.jpg<br />
<br />
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.<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/newstring.jpg<br />
<br />
Step 9: Name this new String value "Application".<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/application.jpg<br />
<br />
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.<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/editapplication.jpg<br />
<br />
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:<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/final.jpg<br />
<br />
Step 11: Close Regedit<br />
<br />
Step 12: Open the Services console. Navigate to your service, and right click it and select Properties.<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/panel.jpg<br />
<br />
Step 13: Make sure the Startup Type value is Automatic, and then press the Start button.<br />
<br />
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.<br />
<br />
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.<br />
<br />
If your server did not start, recheck your settings. Most problems are related to typos in configuration settings.<br />
<br />
==Linux==<br />
===Getting the Shortcuts to work===<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 />
===Running murmur as a SysV service===<br />
You can use [[Murmur_Init_Script]].</div>Haudraufhttps://wiki.mumble.info/index.php?title=Installing_Mumble&diff=2068Installing Mumble2008-05-18T17:13:14Z<p>Haudrauf: /* Gentoo */</p>
<hr />
<div>=Getting and Installing Mumble=<br />
==Windows==<br />
Just head to [http://sourceforge.net/project/showfiles.php?group_id=147372 SourceForge downloads page], get the Windows executable and run it. Follow the installer instructions and you are done.<br />
<br />
Also, you can build Mumble yourself from source as described in [[BuildingWindows]].<br />
<br />
==Linux==<br />
If you want to compile your own version of Mumble, you can read some help in [[BuildingLinux]].<br />
<br />
===Ubuntu ===<br />
<br />
In hardy, the 1.1.X series is included, so just<br />
apt-get install mumble mumble-server<br />
<br />
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 [http://sourceforge.net/project/showfiles.php?group_id=147372 SourceForge] and install it with your package manager. <br />
<br />
Alternately you can use the PPA for mumble builds, which can be found at [https://edge.launchpad.net/~slicer/+archive 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.<br />
<br />
===Fedora===<br />
Fedora 7 RPMs: [http://koji.fedoraproject.org/koji/getfile?taskID=227582&name=mumble-1.1.0-1.fc7.i386.rpm 1.1.0 i386] [http://koji.fedoraproject.org/koji/getfile?taskID=227581&name=mumble-1.1.0-1.fc7.x86_64.rpm 1.1.0 x86_64]<br />
Fedora 8 RPMs: [http://koji.fedoraproject.org/koji/getfile?taskID=231652&name=mumble-1.1.0-2.fc8.i386.rpm 1.1.0 i386] [http://koji.fedoraproject.org/koji/getfile?taskID=231651&name=mumble-1.1.0-2.fc8.x86_64.rpm 1.1.0 x86_64]<br />
<br />
Install them via double click.<br />
===PCLinuxOS and other RPM based distros===<br />
You can find a rpm package in the [http://sourceforge.net/forum/forum.php?thread_id=1782689&forum_id=492606 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):<br />
<br />
rpm -i mumble-1.0.0-2.i386.rpm<br />
<br />
===Gentoo===<br />
Become root and do:<br />
emerge -av mumble<br />
That should do it. You will need Qt4 compiled with the dbus, sqlite and sqlite3 flags.<br />
<br />
If Qt4 is missing the sqlite use flags, then re-install Qt4 with sqlite features:<br />
echo x11-libs/qt dbus sqlite sqlite3 >> /etc/portage/package.use<br />
emerge -av ">=x11-libs/qt-4.3" <br />
<br />
Note that if the ebuild in the repository is a little outdated, you can find newer versions in the [http://sourceforge.net/forum/forum.php?thread_id=1779400&forum_id=492606 forums].<br />
<br />
If the forums are outdated too, you can always compile mumble from source. First install the dependencies manually:<br />
emerge -av --oneshot ">=media-libs/speex-1.2_beta3_p2" 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 />
===ArchLinux===<br />
A PKGBUILD is avalaible in the [http://aur.archlinux.org/packages.php?do_Details=1&ID=10221&K=mumble AUR]. Download the tarball and then run:<br />
tar xzfv mumble.tar.gz<br />
cd mumble<br />
makepkg<br />
<br />
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:<br />
<br />
pacman -S alsa-lib qt4 libxevie sqlite3 boost<br />
<br />
Finally, install the package:<br />
<br />
pacman -A mumble-1.0.0-1.pkg.tar.gz<br />
<br />
Of course, replace the package name as appropriate.<br />
<br />
===Installing from source===<br />
The most generic approach to install mumble under any linux is to install from source. Download the tarball and then run:<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 />
Read the linux specific entries in the INSTALL file, since there you get to know about the pre-requisites needed for compilation. Be sure to have everything installed and in place for your linux distribution.<br />
<br />
Then run:<br />
qmake main.pro<br />
make<br />
<br />
After the compilation is finished, you will find the binaries in the directory "release". To run it there:<br />
cd release<br />
./mumble<br />
<br />
==Mac OS X==<br />
Precompiled Mac OS X universal binaries are available from the [http://sourceforge.net/project/showfiles.php?group_id=147372 SourceForge downloads page].<br />
<br />
You can also build it from source yourself if you wish. See [[BuildingMacOsX]] for more information.<br />
<br />
=Post-installation tips=<br />
==Common tips==<br />
===Initializing/Resetting Murmur password===<br />
Type:<br />
murmur -supw <password><br />
That will change the password for SuperUser, a special user that has all rights.<br />
If you want to reset the entire database, just delete murmur.sqlite and the recreate it with the command above.<br />
<br />
==Windows==<br />
===Text-to-Speech===<br />
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 [http://www.nextup.com NextUp]).<br />
<br />
===Creating a server connection shortcut===<br />
You can right click on your desktop and choose "New" and pick "Shortcut" from the sub-menu.<br />
In the box that says "Type the location of the item" put "mumble://username:password@servername/channel"<br />
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. <br />
<br />
===It complains about mumble_ol.dll / Problems with Overlay===<br />
If you are running XP you will need to update it to SP2. You also need to update to the latest DirectX9 version that can be downloaded from the [http://www.microsoft.com/downloads/details.aspx?FamilyId=2DA43D38-DB71-4C1B-BC6A-9B6652CD92A3&displaylang=en Microsoft site]. The [http://www.microsoft.com/downloads/details.aspx?FamilyID=b406cf67-d926-463b-99e8-27199d6626b5&DisplayLang=en June 2007 version] should be enough.<br />
<br />
=== Murmur dies when I log out! How can I get Murmur to stay on all the time? ===<br />
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.<br />
<br />
Some references you'll see int his write-up:<br />
<br />
instsrv.exe - A program that adds services to the Windows registry.<br />
<br />
srvany.exe - A program that allows any Windows application and some Windows 16-bit applications to run as a service.<br />
<br />
'''The HOW-TO'''<br />
<br />
Step 1: Gain Administrator access on the machine running Murmur.<br />
<br />
Step 2: Download and install the following collection of tools from Microsoft to the default directory (C:\Program Files\Windows Resource Kits):<br />
<br />
[http://www.microsoft.com/downloads/details.aspx?FamilyID=9d467a69-57ff-4ae7-96ee-b18c4790cffd&displaylang=en Windows 2003 Server Resource Kit].<br />
<br />
Step 3: Open a command console (Start >> Accessories >> Command Prompt).<br />
<br />
Step 4: If you have installed to the default directory, type the following:<br />
<br />
"C:\Program Files\Windows Resource Kits\Tools\instsrv.exe" "Murmur" "C:\Program Files\Windows Resource Kits\Tools\srvany.exe"<br />
<br />
Below is an example of what you should see:<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/command.jpg<br />
<br />
The result of this step is a new service in the Services console (Start >> Control Panel >> Administrative Tools >> Services).<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/service.jpg<br />
<br />
'''Be sure to close the Services console before proceeding.'''<br />
<br />
Step 5: Open the registry editor (Start >> Run and enter "regedit") and navigate to the following key:<br />
<br />
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Murmur Demo<br />
<br />
Regedit should look something like this:<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/regedit.jpg<br />
<br />
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.<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/newkey.jpg<br />
<br />
Step 7: Name this new key "Parameters"<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/parameters.jpg<br />
<br />
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.<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/newstring.jpg<br />
<br />
Step 9: Name this new String value "Application".<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/application.jpg<br />
<br />
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.<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/editapplication.jpg<br />
<br />
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:<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/final.jpg<br />
<br />
Step 11: Close Regedit<br />
<br />
Step 12: Open the Services console. Navigate to your service, and right click it and select Properties.<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/panel.jpg<br />
<br />
Step 13: Make sure the Startup Type value is Automatic, and then press the Start button.<br />
<br />
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.<br />
<br />
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.<br />
<br />
If your server did not start, recheck your settings. Most problems are related to typos in configuration settings.<br />
<br />
==Linux==<br />
===Getting the Shortcuts to work===<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 />
===Running murmur as a SysV service===<br />
You can use [[Murmur_Init_Script]].</div>Haudraufhttps://wiki.mumble.info/index.php?title=Installing_Mumble&diff=2067Installing Mumble2008-05-18T16:56:45Z<p>Haudrauf: /* Installing from source */</p>
<hr />
<div>=Getting and Installing Mumble=<br />
==Windows==<br />
Just head to [http://sourceforge.net/project/showfiles.php?group_id=147372 SourceForge downloads page], get the Windows executable and run it. Follow the installer instructions and you are done.<br />
<br />
Also, you can build Mumble yourself from source as described in [[BuildingWindows]].<br />
<br />
==Linux==<br />
If you want to compile your own version of Mumble, you can read some help in [[BuildingLinux]].<br />
<br />
===Ubuntu ===<br />
<br />
In hardy, the 1.1.X series is included, so just<br />
apt-get install mumble mumble-server<br />
<br />
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 [http://sourceforge.net/project/showfiles.php?group_id=147372 SourceForge] and install it with your package manager. <br />
<br />
Alternately you can use the PPA for mumble builds, which can be found at [https://edge.launchpad.net/~slicer/+archive 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.<br />
<br />
===Fedora===<br />
Fedora 7 RPMs: [http://koji.fedoraproject.org/koji/getfile?taskID=227582&name=mumble-1.1.0-1.fc7.i386.rpm 1.1.0 i386] [http://koji.fedoraproject.org/koji/getfile?taskID=227581&name=mumble-1.1.0-1.fc7.x86_64.rpm 1.1.0 x86_64]<br />
Fedora 8 RPMs: [http://koji.fedoraproject.org/koji/getfile?taskID=231652&name=mumble-1.1.0-2.fc8.i386.rpm 1.1.0 i386] [http://koji.fedoraproject.org/koji/getfile?taskID=231651&name=mumble-1.1.0-2.fc8.x86_64.rpm 1.1.0 x86_64]<br />
<br />
Install them via double click.<br />
===PCLinuxOS and other RPM based distros===<br />
You can find a rpm package in the [http://sourceforge.net/forum/forum.php?thread_id=1782689&forum_id=492606 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):<br />
<br />
rpm -i mumble-1.0.0-2.i386.rpm<br />
<br />
===Gentoo===<br />
Become root and do:<br />
emerge -av mumble<br />
That should do it. You will need Qt4 compiled with the dbus, sqlite and sqlite3 flags.<br />
<br />
If Qt4 is missing the sqlite use flags, then re-install Qt4 with sqlite features:<br />
echo x11-libs/qt dbus sqlite sqlite3 >> /etc/portage/package.use<br />
emerge -av ">=x11-libs/qt-4.3" <br />
<br />
Note that if the ebuild in the repository is a little outdated, you can find newer versions in the [http://sourceforge.net/forum/forum.php?thread_id=1779400&forum_id=492606 forums].<br />
<br />
If the forums are outdated too, you can always compile mumble from source. First install the dependencies manually:<br />
emerge -av --oneshot ">=media-libs/speex-1" 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 />
===ArchLinux===<br />
A PKGBUILD is avalaible in the [http://aur.archlinux.org/packages.php?do_Details=1&ID=10221&K=mumble AUR]. Download the tarball and then run:<br />
tar xzfv mumble.tar.gz<br />
cd mumble<br />
makepkg<br />
<br />
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:<br />
<br />
pacman -S alsa-lib qt4 libxevie sqlite3 boost<br />
<br />
Finally, install the package:<br />
<br />
pacman -A mumble-1.0.0-1.pkg.tar.gz<br />
<br />
Of course, replace the package name as appropriate.<br />
<br />
===Installing from source===<br />
The most generic approach to install mumble under any linux is to install from source. Download the tarball and then run:<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 />
Read the linux specific entries in the INSTALL file, since there you get to know about the pre-requisites needed for compilation. Be sure to have everything installed and in place for your linux distribution.<br />
<br />
Then run:<br />
qmake main.pro<br />
make<br />
<br />
After the compilation is finished, you will find the binaries in the directory "release". To run it there:<br />
cd release<br />
./mumble<br />
<br />
==Mac OS X==<br />
Precompiled Mac OS X universal binaries are available from the [http://sourceforge.net/project/showfiles.php?group_id=147372 SourceForge downloads page].<br />
<br />
You can also build it from source yourself if you wish. See [[BuildingMacOsX]] for more information.<br />
<br />
=Post-installation tips=<br />
==Common tips==<br />
===Initializing/Resetting Murmur password===<br />
Type:<br />
murmur -supw <password><br />
That will change the password for SuperUser, a special user that has all rights.<br />
If you want to reset the entire database, just delete murmur.sqlite and the recreate it with the command above.<br />
<br />
==Windows==<br />
===Text-to-Speech===<br />
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 [http://www.nextup.com NextUp]).<br />
<br />
===Creating a server connection shortcut===<br />
You can right click on your desktop and choose "New" and pick "Shortcut" from the sub-menu.<br />
In the box that says "Type the location of the item" put "mumble://username:password@servername/channel"<br />
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. <br />
<br />
===It complains about mumble_ol.dll / Problems with Overlay===<br />
If you are running XP you will need to update it to SP2. You also need to update to the latest DirectX9 version that can be downloaded from the [http://www.microsoft.com/downloads/details.aspx?FamilyId=2DA43D38-DB71-4C1B-BC6A-9B6652CD92A3&displaylang=en Microsoft site]. The [http://www.microsoft.com/downloads/details.aspx?FamilyID=b406cf67-d926-463b-99e8-27199d6626b5&DisplayLang=en June 2007 version] should be enough.<br />
<br />
=== Murmur dies when I log out! How can I get Murmur to stay on all the time? ===<br />
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.<br />
<br />
Some references you'll see int his write-up:<br />
<br />
instsrv.exe - A program that adds services to the Windows registry.<br />
<br />
srvany.exe - A program that allows any Windows application and some Windows 16-bit applications to run as a service.<br />
<br />
'''The HOW-TO'''<br />
<br />
Step 1: Gain Administrator access on the machine running Murmur.<br />
<br />
Step 2: Download and install the following collection of tools from Microsoft to the default directory (C:\Program Files\Windows Resource Kits):<br />
<br />
[http://www.microsoft.com/downloads/details.aspx?FamilyID=9d467a69-57ff-4ae7-96ee-b18c4790cffd&displaylang=en Windows 2003 Server Resource Kit].<br />
<br />
Step 3: Open a command console (Start >> Accessories >> Command Prompt).<br />
<br />
Step 4: If you have installed to the default directory, type the following:<br />
<br />
"C:\Program Files\Windows Resource Kits\Tools\instsrv.exe" "Murmur" "C:\Program Files\Windows Resource Kits\Tools\srvany.exe"<br />
<br />
Below is an example of what you should see:<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/command.jpg<br />
<br />
The result of this step is a new service in the Services console (Start >> Control Panel >> Administrative Tools >> Services).<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/service.jpg<br />
<br />
'''Be sure to close the Services console before proceeding.'''<br />
<br />
Step 5: Open the registry editor (Start >> Run and enter "regedit") and navigate to the following key:<br />
<br />
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Murmur Demo<br />
<br />
Regedit should look something like this:<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/regedit.jpg<br />
<br />
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.<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/newkey.jpg<br />
<br />
Step 7: Name this new key "Parameters"<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/parameters.jpg<br />
<br />
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.<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/newstring.jpg<br />
<br />
Step 9: Name this new String value "Application".<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/application.jpg<br />
<br />
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.<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/editapplication.jpg<br />
<br />
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:<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/final.jpg<br />
<br />
Step 11: Close Regedit<br />
<br />
Step 12: Open the Services console. Navigate to your service, and right click it and select Properties.<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/panel.jpg<br />
<br />
Step 13: Make sure the Startup Type value is Automatic, and then press the Start button.<br />
<br />
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.<br />
<br />
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.<br />
<br />
If your server did not start, recheck your settings. Most problems are related to typos in configuration settings.<br />
<br />
==Linux==<br />
===Getting the Shortcuts to work===<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 />
===Running murmur as a SysV service===<br />
You can use [[Murmur_Init_Script]].</div>Haudraufhttps://wiki.mumble.info/index.php?title=Installing_Mumble&diff=2066Installing Mumble2008-05-18T16:54:45Z<p>Haudrauf: /* Gentoo */</p>
<hr />
<div>=Getting and Installing Mumble=<br />
==Windows==<br />
Just head to [http://sourceforge.net/project/showfiles.php?group_id=147372 SourceForge downloads page], get the Windows executable and run it. Follow the installer instructions and you are done.<br />
<br />
Also, you can build Mumble yourself from source as described in [[BuildingWindows]].<br />
<br />
==Linux==<br />
If you want to compile your own version of Mumble, you can read some help in [[BuildingLinux]].<br />
<br />
===Ubuntu ===<br />
<br />
In hardy, the 1.1.X series is included, so just<br />
apt-get install mumble mumble-server<br />
<br />
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 [http://sourceforge.net/project/showfiles.php?group_id=147372 SourceForge] and install it with your package manager. <br />
<br />
Alternately you can use the PPA for mumble builds, which can be found at [https://edge.launchpad.net/~slicer/+archive 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.<br />
<br />
===Fedora===<br />
Fedora 7 RPMs: [http://koji.fedoraproject.org/koji/getfile?taskID=227582&name=mumble-1.1.0-1.fc7.i386.rpm 1.1.0 i386] [http://koji.fedoraproject.org/koji/getfile?taskID=227581&name=mumble-1.1.0-1.fc7.x86_64.rpm 1.1.0 x86_64]<br />
Fedora 8 RPMs: [http://koji.fedoraproject.org/koji/getfile?taskID=231652&name=mumble-1.1.0-2.fc8.i386.rpm 1.1.0 i386] [http://koji.fedoraproject.org/koji/getfile?taskID=231651&name=mumble-1.1.0-2.fc8.x86_64.rpm 1.1.0 x86_64]<br />
<br />
Install them via double click.<br />
===PCLinuxOS and other RPM based distros===<br />
You can find a rpm package in the [http://sourceforge.net/forum/forum.php?thread_id=1782689&forum_id=492606 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):<br />
<br />
rpm -i mumble-1.0.0-2.i386.rpm<br />
<br />
===Gentoo===<br />
Become root and do:<br />
emerge -av mumble<br />
That should do it. You will need Qt4 compiled with the dbus, sqlite and sqlite3 flags.<br />
<br />
If Qt4 is missing the sqlite use flags, then re-install Qt4 with sqlite features:<br />
echo x11-libs/qt dbus sqlite sqlite3 >> /etc/portage/package.use<br />
emerge -av ">=x11-libs/qt-4.3" <br />
<br />
Note that if the ebuild in the repository is a little outdated, you can find newer versions in the [http://sourceforge.net/forum/forum.php?thread_id=1779400&forum_id=492606 forums].<br />
<br />
If the forums are outdated too, you can always compile mumble from source. First install the dependencies manually:<br />
emerge -av --oneshot ">=media-libs/speex-1" 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 />
===ArchLinux===<br />
A PKGBUILD is avalaible in the [http://aur.archlinux.org/packages.php?do_Details=1&ID=10221&K=mumble AUR]. Download the tarball and then run:<br />
tar xzfv mumble.tar.gz<br />
cd mumble<br />
makepkg<br />
<br />
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:<br />
<br />
pacman -S alsa-lib qt4 libxevie sqlite3 boost<br />
<br />
Finally, install the package:<br />
<br />
pacman -A mumble-1.0.0-1.pkg.tar.gz<br />
<br />
Of course, replace the package name as appropriate.<br />
<br />
===Installing from source===<br />
The most generic approach to install mumble under any linux is to install from source. Download the tarball and then run:<br />
tar xzfv mumble.tar.gz<br />
cd mumble-x.x.x # (whereas the X are the version number of mumble)<br />
Read the linux specific entries in the INSTALL file, since there you get to know about the pre-requisites needed for compilation. Be sure to have everything installed and in place for your linux distribution.<br />
<br />
Then run:<br />
qmake main.pro<br />
make<br />
<br />
After the compilation is finished, you will find the binaries in the directory "release". To run it there:<br />
cd release<br />
./mumble<br />
<br />
==Mac OS X==<br />
Precompiled Mac OS X universal binaries are available from the [http://sourceforge.net/project/showfiles.php?group_id=147372 SourceForge downloads page].<br />
<br />
You can also build it from source yourself if you wish. See [[BuildingMacOsX]] for more information.<br />
<br />
=Post-installation tips=<br />
==Common tips==<br />
===Initializing/Resetting Murmur password===<br />
Type:<br />
murmur -supw <password><br />
That will change the password for SuperUser, a special user that has all rights.<br />
If you want to reset the entire database, just delete murmur.sqlite and the recreate it with the command above.<br />
<br />
==Windows==<br />
===Text-to-Speech===<br />
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 [http://www.nextup.com NextUp]).<br />
<br />
===Creating a server connection shortcut===<br />
You can right click on your desktop and choose "New" and pick "Shortcut" from the sub-menu.<br />
In the box that says "Type the location of the item" put "mumble://username:password@servername/channel"<br />
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. <br />
<br />
===It complains about mumble_ol.dll / Problems with Overlay===<br />
If you are running XP you will need to update it to SP2. You also need to update to the latest DirectX9 version that can be downloaded from the [http://www.microsoft.com/downloads/details.aspx?FamilyId=2DA43D38-DB71-4C1B-BC6A-9B6652CD92A3&displaylang=en Microsoft site]. The [http://www.microsoft.com/downloads/details.aspx?FamilyID=b406cf67-d926-463b-99e8-27199d6626b5&DisplayLang=en June 2007 version] should be enough.<br />
<br />
=== Murmur dies when I log out! How can I get Murmur to stay on all the time? ===<br />
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.<br />
<br />
Some references you'll see int his write-up:<br />
<br />
instsrv.exe - A program that adds services to the Windows registry.<br />
<br />
srvany.exe - A program that allows any Windows application and some Windows 16-bit applications to run as a service.<br />
<br />
'''The HOW-TO'''<br />
<br />
Step 1: Gain Administrator access on the machine running Murmur.<br />
<br />
Step 2: Download and install the following collection of tools from Microsoft to the default directory (C:\Program Files\Windows Resource Kits):<br />
<br />
[http://www.microsoft.com/downloads/details.aspx?FamilyID=9d467a69-57ff-4ae7-96ee-b18c4790cffd&displaylang=en Windows 2003 Server Resource Kit].<br />
<br />
Step 3: Open a command console (Start >> Accessories >> Command Prompt).<br />
<br />
Step 4: If you have installed to the default directory, type the following:<br />
<br />
"C:\Program Files\Windows Resource Kits\Tools\instsrv.exe" "Murmur" "C:\Program Files\Windows Resource Kits\Tools\srvany.exe"<br />
<br />
Below is an example of what you should see:<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/command.jpg<br />
<br />
The result of this step is a new service in the Services console (Start >> Control Panel >> Administrative Tools >> Services).<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/service.jpg<br />
<br />
'''Be sure to close the Services console before proceeding.'''<br />
<br />
Step 5: Open the registry editor (Start >> Run and enter "regedit") and navigate to the following key:<br />
<br />
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Murmur Demo<br />
<br />
Regedit should look something like this:<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/regedit.jpg<br />
<br />
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.<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/newkey.jpg<br />
<br />
Step 7: Name this new key "Parameters"<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/parameters.jpg<br />
<br />
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.<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/newstring.jpg<br />
<br />
Step 9: Name this new String value "Application".<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/application.jpg<br />
<br />
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.<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/editapplication.jpg<br />
<br />
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:<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/final.jpg<br />
<br />
Step 11: Close Regedit<br />
<br />
Step 12: Open the Services console. Navigate to your service, and right click it and select Properties.<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/panel.jpg<br />
<br />
Step 13: Make sure the Startup Type value is Automatic, and then press the Start button.<br />
<br />
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.<br />
<br />
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.<br />
<br />
If your server did not start, recheck your settings. Most problems are related to typos in configuration settings.<br />
<br />
==Linux==<br />
===Getting the Shortcuts to work===<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 />
===Running murmur as a SysV service===<br />
You can use [[Murmur_Init_Script]].</div>Haudraufhttps://wiki.mumble.info/index.php?title=Installing_Mumble&diff=2065Installing Mumble2008-05-18T16:53:11Z<p>Haudrauf: /* Gentoo */</p>
<hr />
<div>=Getting and Installing Mumble=<br />
==Windows==<br />
Just head to [http://sourceforge.net/project/showfiles.php?group_id=147372 SourceForge downloads page], get the Windows executable and run it. Follow the installer instructions and you are done.<br />
<br />
Also, you can build Mumble yourself from source as described in [[BuildingWindows]].<br />
<br />
==Linux==<br />
If you want to compile your own version of Mumble, you can read some help in [[BuildingLinux]].<br />
<br />
===Ubuntu ===<br />
<br />
In hardy, the 1.1.X series is included, so just<br />
apt-get install mumble mumble-server<br />
<br />
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 [http://sourceforge.net/project/showfiles.php?group_id=147372 SourceForge] and install it with your package manager. <br />
<br />
Alternately you can use the PPA for mumble builds, which can be found at [https://edge.launchpad.net/~slicer/+archive 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.<br />
<br />
===Fedora===<br />
Fedora 7 RPMs: [http://koji.fedoraproject.org/koji/getfile?taskID=227582&name=mumble-1.1.0-1.fc7.i386.rpm 1.1.0 i386] [http://koji.fedoraproject.org/koji/getfile?taskID=227581&name=mumble-1.1.0-1.fc7.x86_64.rpm 1.1.0 x86_64]<br />
Fedora 8 RPMs: [http://koji.fedoraproject.org/koji/getfile?taskID=231652&name=mumble-1.1.0-2.fc8.i386.rpm 1.1.0 i386] [http://koji.fedoraproject.org/koji/getfile?taskID=231651&name=mumble-1.1.0-2.fc8.x86_64.rpm 1.1.0 x86_64]<br />
<br />
Install them via double click.<br />
===PCLinuxOS and other RPM based distros===<br />
You can find a rpm package in the [http://sourceforge.net/forum/forum.php?thread_id=1782689&forum_id=492606 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):<br />
<br />
rpm -i mumble-1.0.0-2.i386.rpm<br />
<br />
===Gentoo===<br />
Become root and do:<br />
emerge mumble<br />
That should do it. You will need Qt4 compiled with the dbus, sqlite and sqlite3 flags.<br />
<br />
If Qt4 is missing the sqlite use flags, then re-install Qt4 with sqlite features:<br />
echo x11-libs/qt dbus sqlite sqlite3 >> /etc/portage/package.use<br />
emerge -av ">=x11-libs/qt-4.3" <br />
<br />
Note that if the ebuild in the repository is a little outdated, you can find newer versions in the [http://sourceforge.net/forum/forum.php?thread_id=1779400&forum_id=492606 forums].<br />
<br />
If the forums are outdated too, you can always compile mumble from source. First install the dependencies manually:<br />
emerge -av --oneshot ">=media-libs/speex-1" 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 />
===ArchLinux===<br />
A PKGBUILD is avalaible in the [http://aur.archlinux.org/packages.php?do_Details=1&ID=10221&K=mumble AUR]. Download the tarball and then run:<br />
tar xzfv mumble.tar.gz<br />
cd mumble<br />
makepkg<br />
<br />
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:<br />
<br />
pacman -S alsa-lib qt4 libxevie sqlite3 boost<br />
<br />
Finally, install the package:<br />
<br />
pacman -A mumble-1.0.0-1.pkg.tar.gz<br />
<br />
Of course, replace the package name as appropriate.<br />
<br />
===Installing from source===<br />
The most generic approach to install mumble under any linux is to install from source. Download the tarball and then run:<br />
tar xzfv mumble.tar.gz<br />
cd mumble-x.x.x # (whereas the X are the version number of mumble)<br />
Read the linux specific entries in the INSTALL file, since there you get to know about the pre-requisites needed for compilation. Be sure to have everything installed and in place for your linux distribution.<br />
<br />
Then run:<br />
qmake main.pro<br />
make<br />
<br />
After the compilation is finished, you will find the binaries in the directory "release". To run it there:<br />
cd release<br />
./mumble<br />
<br />
==Mac OS X==<br />
Precompiled Mac OS X universal binaries are available from the [http://sourceforge.net/project/showfiles.php?group_id=147372 SourceForge downloads page].<br />
<br />
You can also build it from source yourself if you wish. See [[BuildingMacOsX]] for more information.<br />
<br />
=Post-installation tips=<br />
==Common tips==<br />
===Initializing/Resetting Murmur password===<br />
Type:<br />
murmur -supw <password><br />
That will change the password for SuperUser, a special user that has all rights.<br />
If you want to reset the entire database, just delete murmur.sqlite and the recreate it with the command above.<br />
<br />
==Windows==<br />
===Text-to-Speech===<br />
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 [http://www.nextup.com NextUp]).<br />
<br />
===Creating a server connection shortcut===<br />
You can right click on your desktop and choose "New" and pick "Shortcut" from the sub-menu.<br />
In the box that says "Type the location of the item" put "mumble://username:password@servername/channel"<br />
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. <br />
<br />
===It complains about mumble_ol.dll / Problems with Overlay===<br />
If you are running XP you will need to update it to SP2. You also need to update to the latest DirectX9 version that can be downloaded from the [http://www.microsoft.com/downloads/details.aspx?FamilyId=2DA43D38-DB71-4C1B-BC6A-9B6652CD92A3&displaylang=en Microsoft site]. The [http://www.microsoft.com/downloads/details.aspx?FamilyID=b406cf67-d926-463b-99e8-27199d6626b5&DisplayLang=en June 2007 version] should be enough.<br />
<br />
=== Murmur dies when I log out! How can I get Murmur to stay on all the time? ===<br />
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.<br />
<br />
Some references you'll see int his write-up:<br />
<br />
instsrv.exe - A program that adds services to the Windows registry.<br />
<br />
srvany.exe - A program that allows any Windows application and some Windows 16-bit applications to run as a service.<br />
<br />
'''The HOW-TO'''<br />
<br />
Step 1: Gain Administrator access on the machine running Murmur.<br />
<br />
Step 2: Download and install the following collection of tools from Microsoft to the default directory (C:\Program Files\Windows Resource Kits):<br />
<br />
[http://www.microsoft.com/downloads/details.aspx?FamilyID=9d467a69-57ff-4ae7-96ee-b18c4790cffd&displaylang=en Windows 2003 Server Resource Kit].<br />
<br />
Step 3: Open a command console (Start >> Accessories >> Command Prompt).<br />
<br />
Step 4: If you have installed to the default directory, type the following:<br />
<br />
"C:\Program Files\Windows Resource Kits\Tools\instsrv.exe" "Murmur" "C:\Program Files\Windows Resource Kits\Tools\srvany.exe"<br />
<br />
Below is an example of what you should see:<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/command.jpg<br />
<br />
The result of this step is a new service in the Services console (Start >> Control Panel >> Administrative Tools >> Services).<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/service.jpg<br />
<br />
'''Be sure to close the Services console before proceeding.'''<br />
<br />
Step 5: Open the registry editor (Start >> Run and enter "regedit") and navigate to the following key:<br />
<br />
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Murmur Demo<br />
<br />
Regedit should look something like this:<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/regedit.jpg<br />
<br />
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.<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/newkey.jpg<br />
<br />
Step 7: Name this new key "Parameters"<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/parameters.jpg<br />
<br />
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.<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/newstring.jpg<br />
<br />
Step 9: Name this new String value "Application".<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/application.jpg<br />
<br />
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.<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/editapplication.jpg<br />
<br />
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:<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/final.jpg<br />
<br />
Step 11: Close Regedit<br />
<br />
Step 12: Open the Services console. Navigate to your service, and right click it and select Properties.<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/panel.jpg<br />
<br />
Step 13: Make sure the Startup Type value is Automatic, and then press the Start button.<br />
<br />
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.<br />
<br />
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.<br />
<br />
If your server did not start, recheck your settings. Most problems are related to typos in configuration settings.<br />
<br />
==Linux==<br />
===Getting the Shortcuts to work===<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 />
===Running murmur as a SysV service===<br />
You can use [[Murmur_Init_Script]].</div>Haudraufhttps://wiki.mumble.info/index.php?title=Installing_Mumble&diff=2064Installing Mumble2008-05-18T16:51:57Z<p>Haudrauf: /* Gentoo */</p>
<hr />
<div>=Getting and Installing Mumble=<br />
==Windows==<br />
Just head to [http://sourceforge.net/project/showfiles.php?group_id=147372 SourceForge downloads page], get the Windows executable and run it. Follow the installer instructions and you are done.<br />
<br />
Also, you can build Mumble yourself from source as described in [[BuildingWindows]].<br />
<br />
==Linux==<br />
If you want to compile your own version of Mumble, you can read some help in [[BuildingLinux]].<br />
<br />
===Ubuntu ===<br />
<br />
In hardy, the 1.1.X series is included, so just<br />
apt-get install mumble mumble-server<br />
<br />
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 [http://sourceforge.net/project/showfiles.php?group_id=147372 SourceForge] and install it with your package manager. <br />
<br />
Alternately you can use the PPA for mumble builds, which can be found at [https://edge.launchpad.net/~slicer/+archive 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.<br />
<br />
===Fedora===<br />
Fedora 7 RPMs: [http://koji.fedoraproject.org/koji/getfile?taskID=227582&name=mumble-1.1.0-1.fc7.i386.rpm 1.1.0 i386] [http://koji.fedoraproject.org/koji/getfile?taskID=227581&name=mumble-1.1.0-1.fc7.x86_64.rpm 1.1.0 x86_64]<br />
Fedora 8 RPMs: [http://koji.fedoraproject.org/koji/getfile?taskID=231652&name=mumble-1.1.0-2.fc8.i386.rpm 1.1.0 i386] [http://koji.fedoraproject.org/koji/getfile?taskID=231651&name=mumble-1.1.0-2.fc8.x86_64.rpm 1.1.0 x86_64]<br />
<br />
Install them via double click.<br />
===PCLinuxOS and other RPM based distros===<br />
You can find a rpm package in the [http://sourceforge.net/forum/forum.php?thread_id=1782689&forum_id=492606 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):<br />
<br />
rpm -i mumble-1.0.0-2.i386.rpm<br />
<br />
===Gentoo===<br />
Become root and do:<br />
emerge mumble<br />
That should do it. You will need Qt4 compiled with the dbus, sqlite and sqlite3 flags.<br />
<br />
If Qt4 is missing the sqlite use flags, then re-install Qt4 with sqlite features:<br />
echo x11-libs/qt dbus sqlite sqlite3 >> /etc/portage/package.use<br />
emerge -av ">=x11-libs/qt-4.3" <br />
<br />
Note that if the ebuild in the repository is a little outdated, you can find newer versions in the [http://sourceforge.net/forum/forum.php?thread_id=1779400&forum_id=492606 forums].<br />
<br />
If the forums are outdated too, you can always compile mumble from source. First install the dependencies manually:<br />
emerge -av --oneshot >=media-libs/speex-1.2 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 />
===ArchLinux===<br />
A PKGBUILD is avalaible in the [http://aur.archlinux.org/packages.php?do_Details=1&ID=10221&K=mumble AUR]. Download the tarball and then run:<br />
tar xzfv mumble.tar.gz<br />
cd mumble<br />
makepkg<br />
<br />
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:<br />
<br />
pacman -S alsa-lib qt4 libxevie sqlite3 boost<br />
<br />
Finally, install the package:<br />
<br />
pacman -A mumble-1.0.0-1.pkg.tar.gz<br />
<br />
Of course, replace the package name as appropriate.<br />
<br />
===Installing from source===<br />
The most generic approach to install mumble under any linux is to install from source. Download the tarball and then run:<br />
tar xzfv mumble.tar.gz<br />
cd mumble-x.x.x # (whereas the X are the version number of mumble)<br />
Read the linux specific entries in the INSTALL file, since there you get to know about the pre-requisites needed for compilation. Be sure to have everything installed and in place for your linux distribution.<br />
<br />
Then run:<br />
qmake main.pro<br />
make<br />
<br />
After the compilation is finished, you will find the binaries in the directory "release". To run it there:<br />
cd release<br />
./mumble<br />
<br />
==Mac OS X==<br />
Precompiled Mac OS X universal binaries are available from the [http://sourceforge.net/project/showfiles.php?group_id=147372 SourceForge downloads page].<br />
<br />
You can also build it from source yourself if you wish. See [[BuildingMacOsX]] for more information.<br />
<br />
=Post-installation tips=<br />
==Common tips==<br />
===Initializing/Resetting Murmur password===<br />
Type:<br />
murmur -supw <password><br />
That will change the password for SuperUser, a special user that has all rights.<br />
If you want to reset the entire database, just delete murmur.sqlite and the recreate it with the command above.<br />
<br />
==Windows==<br />
===Text-to-Speech===<br />
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 [http://www.nextup.com NextUp]).<br />
<br />
===Creating a server connection shortcut===<br />
You can right click on your desktop and choose "New" and pick "Shortcut" from the sub-menu.<br />
In the box that says "Type the location of the item" put "mumble://username:password@servername/channel"<br />
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. <br />
<br />
===It complains about mumble_ol.dll / Problems with Overlay===<br />
If you are running XP you will need to update it to SP2. You also need to update to the latest DirectX9 version that can be downloaded from the [http://www.microsoft.com/downloads/details.aspx?FamilyId=2DA43D38-DB71-4C1B-BC6A-9B6652CD92A3&displaylang=en Microsoft site]. The [http://www.microsoft.com/downloads/details.aspx?FamilyID=b406cf67-d926-463b-99e8-27199d6626b5&DisplayLang=en June 2007 version] should be enough.<br />
<br />
=== Murmur dies when I log out! How can I get Murmur to stay on all the time? ===<br />
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.<br />
<br />
Some references you'll see int his write-up:<br />
<br />
instsrv.exe - A program that adds services to the Windows registry.<br />
<br />
srvany.exe - A program that allows any Windows application and some Windows 16-bit applications to run as a service.<br />
<br />
'''The HOW-TO'''<br />
<br />
Step 1: Gain Administrator access on the machine running Murmur.<br />
<br />
Step 2: Download and install the following collection of tools from Microsoft to the default directory (C:\Program Files\Windows Resource Kits):<br />
<br />
[http://www.microsoft.com/downloads/details.aspx?FamilyID=9d467a69-57ff-4ae7-96ee-b18c4790cffd&displaylang=en Windows 2003 Server Resource Kit].<br />
<br />
Step 3: Open a command console (Start >> Accessories >> Command Prompt).<br />
<br />
Step 4: If you have installed to the default directory, type the following:<br />
<br />
"C:\Program Files\Windows Resource Kits\Tools\instsrv.exe" "Murmur" "C:\Program Files\Windows Resource Kits\Tools\srvany.exe"<br />
<br />
Below is an example of what you should see:<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/command.jpg<br />
<br />
The result of this step is a new service in the Services console (Start >> Control Panel >> Administrative Tools >> Services).<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/service.jpg<br />
<br />
'''Be sure to close the Services console before proceeding.'''<br />
<br />
Step 5: Open the registry editor (Start >> Run and enter "regedit") and navigate to the following key:<br />
<br />
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Murmur Demo<br />
<br />
Regedit should look something like this:<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/regedit.jpg<br />
<br />
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.<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/newkey.jpg<br />
<br />
Step 7: Name this new key "Parameters"<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/parameters.jpg<br />
<br />
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.<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/newstring.jpg<br />
<br />
Step 9: Name this new String value "Application".<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/application.jpg<br />
<br />
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.<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/editapplication.jpg<br />
<br />
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:<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/final.jpg<br />
<br />
Step 11: Close Regedit<br />
<br />
Step 12: Open the Services console. Navigate to your service, and right click it and select Properties.<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/panel.jpg<br />
<br />
Step 13: Make sure the Startup Type value is Automatic, and then press the Start button.<br />
<br />
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.<br />
<br />
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.<br />
<br />
If your server did not start, recheck your settings. Most problems are related to typos in configuration settings.<br />
<br />
==Linux==<br />
===Getting the Shortcuts to work===<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 />
===Running murmur as a SysV service===<br />
You can use [[Murmur_Init_Script]].</div>Haudraufhttps://wiki.mumble.info/index.php?title=Installing_Mumble&diff=2063Installing Mumble2008-05-18T16:48:37Z<p>Haudrauf: /* Gentoo */</p>
<hr />
<div>=Getting and Installing Mumble=<br />
==Windows==<br />
Just head to [http://sourceforge.net/project/showfiles.php?group_id=147372 SourceForge downloads page], get the Windows executable and run it. Follow the installer instructions and you are done.<br />
<br />
Also, you can build Mumble yourself from source as described in [[BuildingWindows]].<br />
<br />
==Linux==<br />
If you want to compile your own version of Mumble, you can read some help in [[BuildingLinux]].<br />
<br />
===Ubuntu ===<br />
<br />
In hardy, the 1.1.X series is included, so just<br />
apt-get install mumble mumble-server<br />
<br />
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 [http://sourceforge.net/project/showfiles.php?group_id=147372 SourceForge] and install it with your package manager. <br />
<br />
Alternately you can use the PPA for mumble builds, which can be found at [https://edge.launchpad.net/~slicer/+archive 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.<br />
<br />
===Fedora===<br />
Fedora 7 RPMs: [http://koji.fedoraproject.org/koji/getfile?taskID=227582&name=mumble-1.1.0-1.fc7.i386.rpm 1.1.0 i386] [http://koji.fedoraproject.org/koji/getfile?taskID=227581&name=mumble-1.1.0-1.fc7.x86_64.rpm 1.1.0 x86_64]<br />
Fedora 8 RPMs: [http://koji.fedoraproject.org/koji/getfile?taskID=231652&name=mumble-1.1.0-2.fc8.i386.rpm 1.1.0 i386] [http://koji.fedoraproject.org/koji/getfile?taskID=231651&name=mumble-1.1.0-2.fc8.x86_64.rpm 1.1.0 x86_64]<br />
<br />
Install them via double click.<br />
===PCLinuxOS and other RPM based distros===<br />
You can find a rpm package in the [http://sourceforge.net/forum/forum.php?thread_id=1782689&forum_id=492606 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):<br />
<br />
rpm -i mumble-1.0.0-2.i386.rpm<br />
<br />
===Gentoo===<br />
Become root and do:<br />
emerge mumble<br />
That should do it. You will need Qt4 compiled with the sqlite and sqlite3 flags. Control with: equery uses ">x11-libs/qt-4"<br />
<br />
If Qt4 is missing the sqlite use flags, then re-install Qt4 with sqlite features:<br />
echo x11-libs/qt sqlite sqlite3 >> /etc/portage/package.use<br />
emerge -av ">=x11-libs/qt-4.3" <br />
<br />
Note that the ebuild in the repository is a little outdated, you can find newer versions in the [http://sourceforge.net/forum/forum.php?thread_id=1779400&forum_id=492606 forums].<br />
<br />
If the forums are outdated too, you can always compile mumble from source. First install the dependencies manually:<br />
emerge -av --oneshot >=media-libs/speex-1.2 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 />
===ArchLinux===<br />
A PKGBUILD is avalaible in the [http://aur.archlinux.org/packages.php?do_Details=1&ID=10221&K=mumble AUR]. Download the tarball and then run:<br />
tar xzfv mumble.tar.gz<br />
cd mumble<br />
makepkg<br />
<br />
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:<br />
<br />
pacman -S alsa-lib qt4 libxevie sqlite3 boost<br />
<br />
Finally, install the package:<br />
<br />
pacman -A mumble-1.0.0-1.pkg.tar.gz<br />
<br />
Of course, replace the package name as appropriate.<br />
<br />
===Installing from source===<br />
The most generic approach to install mumble under any linux is to install from source. Download the tarball and then run:<br />
tar xzfv mumble.tar.gz<br />
cd mumble-x.x.x # (whereas the X are the version number of mumble)<br />
Read the linux specific entries in the INSTALL file, since there you get to know about the pre-requisites needed for compilation. Be sure to have everything installed and in place for your linux distribution.<br />
<br />
Then run:<br />
qmake main.pro<br />
make<br />
<br />
After the compilation is finished, you will find the binaries in the directory "release". To run it there:<br />
cd release<br />
./mumble<br />
<br />
==Mac OS X==<br />
Precompiled Mac OS X universal binaries are available from the [http://sourceforge.net/project/showfiles.php?group_id=147372 SourceForge downloads page].<br />
<br />
You can also build it from source yourself if you wish. See [[BuildingMacOsX]] for more information.<br />
<br />
=Post-installation tips=<br />
==Common tips==<br />
===Initializing/Resetting Murmur password===<br />
Type:<br />
murmur -supw <password><br />
That will change the password for SuperUser, a special user that has all rights.<br />
If you want to reset the entire database, just delete murmur.sqlite and the recreate it with the command above.<br />
<br />
==Windows==<br />
===Text-to-Speech===<br />
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 [http://www.nextup.com NextUp]).<br />
<br />
===Creating a server connection shortcut===<br />
You can right click on your desktop and choose "New" and pick "Shortcut" from the sub-menu.<br />
In the box that says "Type the location of the item" put "mumble://username:password@servername/channel"<br />
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. <br />
<br />
===It complains about mumble_ol.dll / Problems with Overlay===<br />
If you are running XP you will need to update it to SP2. You also need to update to the latest DirectX9 version that can be downloaded from the [http://www.microsoft.com/downloads/details.aspx?FamilyId=2DA43D38-DB71-4C1B-BC6A-9B6652CD92A3&displaylang=en Microsoft site]. The [http://www.microsoft.com/downloads/details.aspx?FamilyID=b406cf67-d926-463b-99e8-27199d6626b5&DisplayLang=en June 2007 version] should be enough.<br />
<br />
=== Murmur dies when I log out! How can I get Murmur to stay on all the time? ===<br />
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.<br />
<br />
Some references you'll see int his write-up:<br />
<br />
instsrv.exe - A program that adds services to the Windows registry.<br />
<br />
srvany.exe - A program that allows any Windows application and some Windows 16-bit applications to run as a service.<br />
<br />
'''The HOW-TO'''<br />
<br />
Step 1: Gain Administrator access on the machine running Murmur.<br />
<br />
Step 2: Download and install the following collection of tools from Microsoft to the default directory (C:\Program Files\Windows Resource Kits):<br />
<br />
[http://www.microsoft.com/downloads/details.aspx?FamilyID=9d467a69-57ff-4ae7-96ee-b18c4790cffd&displaylang=en Windows 2003 Server Resource Kit].<br />
<br />
Step 3: Open a command console (Start >> Accessories >> Command Prompt).<br />
<br />
Step 4: If you have installed to the default directory, type the following:<br />
<br />
"C:\Program Files\Windows Resource Kits\Tools\instsrv.exe" "Murmur" "C:\Program Files\Windows Resource Kits\Tools\srvany.exe"<br />
<br />
Below is an example of what you should see:<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/command.jpg<br />
<br />
The result of this step is a new service in the Services console (Start >> Control Panel >> Administrative Tools >> Services).<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/service.jpg<br />
<br />
'''Be sure to close the Services console before proceeding.'''<br />
<br />
Step 5: Open the registry editor (Start >> Run and enter "regedit") and navigate to the following key:<br />
<br />
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Murmur Demo<br />
<br />
Regedit should look something like this:<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/regedit.jpg<br />
<br />
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.<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/newkey.jpg<br />
<br />
Step 7: Name this new key "Parameters"<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/parameters.jpg<br />
<br />
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.<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/newstring.jpg<br />
<br />
Step 9: Name this new String value "Application".<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/application.jpg<br />
<br />
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.<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/editapplication.jpg<br />
<br />
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:<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/final.jpg<br />
<br />
Step 11: Close Regedit<br />
<br />
Step 12: Open the Services console. Navigate to your service, and right click it and select Properties.<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/panel.jpg<br />
<br />
Step 13: Make sure the Startup Type value is Automatic, and then press the Start button.<br />
<br />
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.<br />
<br />
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.<br />
<br />
If your server did not start, recheck your settings. Most problems are related to typos in configuration settings.<br />
<br />
==Linux==<br />
===Getting the Shortcuts to work===<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 />
===Running murmur as a SysV service===<br />
You can use [[Murmur_Init_Script]].</div>Haudraufhttps://wiki.mumble.info/index.php?title=Installing_Mumble&diff=2062Installing Mumble2008-05-18T16:46:57Z<p>Haudrauf: /* Gentoo */</p>
<hr />
<div>=Getting and Installing Mumble=<br />
==Windows==<br />
Just head to [http://sourceforge.net/project/showfiles.php?group_id=147372 SourceForge downloads page], get the Windows executable and run it. Follow the installer instructions and you are done.<br />
<br />
Also, you can build Mumble yourself from source as described in [[BuildingWindows]].<br />
<br />
==Linux==<br />
If you want to compile your own version of Mumble, you can read some help in [[BuildingLinux]].<br />
<br />
===Ubuntu ===<br />
<br />
In hardy, the 1.1.X series is included, so just<br />
apt-get install mumble mumble-server<br />
<br />
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 [http://sourceforge.net/project/showfiles.php?group_id=147372 SourceForge] and install it with your package manager. <br />
<br />
Alternately you can use the PPA for mumble builds, which can be found at [https://edge.launchpad.net/~slicer/+archive 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.<br />
<br />
===Fedora===<br />
Fedora 7 RPMs: [http://koji.fedoraproject.org/koji/getfile?taskID=227582&name=mumble-1.1.0-1.fc7.i386.rpm 1.1.0 i386] [http://koji.fedoraproject.org/koji/getfile?taskID=227581&name=mumble-1.1.0-1.fc7.x86_64.rpm 1.1.0 x86_64]<br />
Fedora 8 RPMs: [http://koji.fedoraproject.org/koji/getfile?taskID=231652&name=mumble-1.1.0-2.fc8.i386.rpm 1.1.0 i386] [http://koji.fedoraproject.org/koji/getfile?taskID=231651&name=mumble-1.1.0-2.fc8.x86_64.rpm 1.1.0 x86_64]<br />
<br />
Install them via double click.<br />
===PCLinuxOS and other RPM based distros===<br />
You can find a rpm package in the [http://sourceforge.net/forum/forum.php?thread_id=1782689&forum_id=492606 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):<br />
<br />
rpm -i mumble-1.0.0-2.i386.rpm<br />
<br />
===Gentoo===<br />
Become root and do:<br />
emerge mumble<br />
That should do it. You will need Qt4 compiled with the sqlite and sqlite3 flags. Control with: emerge -av x11-libs/qt<br />
<br />
If Qt4 is missing the sqlite use flags, then re-install Qt4 with sqlite features:<br />
echo x11-libs/qt sqlite sqlite3 >> /etc/portage/package.use<br />
emerge -av ">=x11-libs/qt-4.3" <br />
<br />
Note that the ebuild in the repository is a little outdated, you can find newer versions in the [http://sourceforge.net/forum/forum.php?thread_id=1779400&forum_id=492606 forums].<br />
<br />
If the forums are outdated too, you can always compile mumble from source. First install the dependencies manually:<br />
emerge -av --oneshot >=media-libs/speex-1.2 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 />
===ArchLinux===<br />
A PKGBUILD is avalaible in the [http://aur.archlinux.org/packages.php?do_Details=1&ID=10221&K=mumble AUR]. Download the tarball and then run:<br />
tar xzfv mumble.tar.gz<br />
cd mumble<br />
makepkg<br />
<br />
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:<br />
<br />
pacman -S alsa-lib qt4 libxevie sqlite3 boost<br />
<br />
Finally, install the package:<br />
<br />
pacman -A mumble-1.0.0-1.pkg.tar.gz<br />
<br />
Of course, replace the package name as appropriate.<br />
<br />
===Installing from source===<br />
The most generic approach to install mumble under any linux is to install from source. Download the tarball and then run:<br />
tar xzfv mumble.tar.gz<br />
cd mumble-x.x.x # (whereas the X are the version number of mumble)<br />
Read the linux specific entries in the INSTALL file, since there you get to know about the pre-requisites needed for compilation. Be sure to have everything installed and in place for your linux distribution.<br />
<br />
Then run:<br />
qmake main.pro<br />
make<br />
<br />
After the compilation is finished, you will find the binaries in the directory "release". To run it there:<br />
cd release<br />
./mumble<br />
<br />
==Mac OS X==<br />
Precompiled Mac OS X universal binaries are available from the [http://sourceforge.net/project/showfiles.php?group_id=147372 SourceForge downloads page].<br />
<br />
You can also build it from source yourself if you wish. See [[BuildingMacOsX]] for more information.<br />
<br />
=Post-installation tips=<br />
==Common tips==<br />
===Initializing/Resetting Murmur password===<br />
Type:<br />
murmur -supw <password><br />
That will change the password for SuperUser, a special user that has all rights.<br />
If you want to reset the entire database, just delete murmur.sqlite and the recreate it with the command above.<br />
<br />
==Windows==<br />
===Text-to-Speech===<br />
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 [http://www.nextup.com NextUp]).<br />
<br />
===Creating a server connection shortcut===<br />
You can right click on your desktop and choose "New" and pick "Shortcut" from the sub-menu.<br />
In the box that says "Type the location of the item" put "mumble://username:password@servername/channel"<br />
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. <br />
<br />
===It complains about mumble_ol.dll / Problems with Overlay===<br />
If you are running XP you will need to update it to SP2. You also need to update to the latest DirectX9 version that can be downloaded from the [http://www.microsoft.com/downloads/details.aspx?FamilyId=2DA43D38-DB71-4C1B-BC6A-9B6652CD92A3&displaylang=en Microsoft site]. The [http://www.microsoft.com/downloads/details.aspx?FamilyID=b406cf67-d926-463b-99e8-27199d6626b5&DisplayLang=en June 2007 version] should be enough.<br />
<br />
=== Murmur dies when I log out! How can I get Murmur to stay on all the time? ===<br />
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.<br />
<br />
Some references you'll see int his write-up:<br />
<br />
instsrv.exe - A program that adds services to the Windows registry.<br />
<br />
srvany.exe - A program that allows any Windows application and some Windows 16-bit applications to run as a service.<br />
<br />
'''The HOW-TO'''<br />
<br />
Step 1: Gain Administrator access on the machine running Murmur.<br />
<br />
Step 2: Download and install the following collection of tools from Microsoft to the default directory (C:\Program Files\Windows Resource Kits):<br />
<br />
[http://www.microsoft.com/downloads/details.aspx?FamilyID=9d467a69-57ff-4ae7-96ee-b18c4790cffd&displaylang=en Windows 2003 Server Resource Kit].<br />
<br />
Step 3: Open a command console (Start >> Accessories >> Command Prompt).<br />
<br />
Step 4: If you have installed to the default directory, type the following:<br />
<br />
"C:\Program Files\Windows Resource Kits\Tools\instsrv.exe" "Murmur" "C:\Program Files\Windows Resource Kits\Tools\srvany.exe"<br />
<br />
Below is an example of what you should see:<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/command.jpg<br />
<br />
The result of this step is a new service in the Services console (Start >> Control Panel >> Administrative Tools >> Services).<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/service.jpg<br />
<br />
'''Be sure to close the Services console before proceeding.'''<br />
<br />
Step 5: Open the registry editor (Start >> Run and enter "regedit") and navigate to the following key:<br />
<br />
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Murmur Demo<br />
<br />
Regedit should look something like this:<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/regedit.jpg<br />
<br />
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.<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/newkey.jpg<br />
<br />
Step 7: Name this new key "Parameters"<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/parameters.jpg<br />
<br />
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.<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/newstring.jpg<br />
<br />
Step 9: Name this new String value "Application".<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/application.jpg<br />
<br />
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.<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/editapplication.jpg<br />
<br />
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:<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/final.jpg<br />
<br />
Step 11: Close Regedit<br />
<br />
Step 12: Open the Services console. Navigate to your service, and right click it and select Properties.<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/panel.jpg<br />
<br />
Step 13: Make sure the Startup Type value is Automatic, and then press the Start button.<br />
<br />
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.<br />
<br />
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.<br />
<br />
If your server did not start, recheck your settings. Most problems are related to typos in configuration settings.<br />
<br />
==Linux==<br />
===Getting the Shortcuts to work===<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 />
===Running murmur as a SysV service===<br />
You can use [[Murmur_Init_Script]].</div>Haudraufhttps://wiki.mumble.info/index.php?title=Installing_Mumble&diff=2061Installing Mumble2008-05-18T16:24:06Z<p>Haudrauf: /* ArchLinux */</p>
<hr />
<div>=Getting and Installing Mumble=<br />
==Windows==<br />
Just head to [http://sourceforge.net/project/showfiles.php?group_id=147372 SourceForge downloads page], get the Windows executable and run it. Follow the installer instructions and you are done.<br />
<br />
Also, you can build Mumble yourself from source as described in [[BuildingWindows]].<br />
<br />
==Linux==<br />
If you want to compile your own version of Mumble, you can read some help in [[BuildingLinux]].<br />
<br />
===Ubuntu ===<br />
<br />
In hardy, the 1.1.X series is included, so just<br />
apt-get install mumble mumble-server<br />
<br />
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 [http://sourceforge.net/project/showfiles.php?group_id=147372 SourceForge] and install it with your package manager. <br />
<br />
Alternately you can use the PPA for mumble builds, which can be found at [https://edge.launchpad.net/~slicer/+archive 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.<br />
<br />
===Fedora===<br />
Fedora 7 RPMs: [http://koji.fedoraproject.org/koji/getfile?taskID=227582&name=mumble-1.1.0-1.fc7.i386.rpm 1.1.0 i386] [http://koji.fedoraproject.org/koji/getfile?taskID=227581&name=mumble-1.1.0-1.fc7.x86_64.rpm 1.1.0 x86_64]<br />
Fedora 8 RPMs: [http://koji.fedoraproject.org/koji/getfile?taskID=231652&name=mumble-1.1.0-2.fc8.i386.rpm 1.1.0 i386] [http://koji.fedoraproject.org/koji/getfile?taskID=231651&name=mumble-1.1.0-2.fc8.x86_64.rpm 1.1.0 x86_64]<br />
<br />
Install them via double click.<br />
===PCLinuxOS and other RPM based distros===<br />
You can find a rpm package in the [http://sourceforge.net/forum/forum.php?thread_id=1782689&forum_id=492606 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):<br />
<br />
rpm -i mumble-1.0.0-2.i386.rpm<br />
<br />
===Gentoo===<br />
emerge mumble<br />
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 [http://sourceforge.net/forum/forum.php?thread_id=1779400&forum_id=492606 forums].<br />
<br />
===ArchLinux===<br />
A PKGBUILD is avalaible in the [http://aur.archlinux.org/packages.php?do_Details=1&ID=10221&K=mumble AUR]. Download the tarball and then run:<br />
tar xzfv mumble.tar.gz<br />
cd mumble<br />
makepkg<br />
<br />
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:<br />
<br />
pacman -S alsa-lib qt4 libxevie sqlite3 boost<br />
<br />
Finally, install the package:<br />
<br />
pacman -A mumble-1.0.0-1.pkg.tar.gz<br />
<br />
Of course, replace the package name as appropriate.<br />
<br />
===Installing from source===<br />
The most generic approach to install mumble under any linux is to install from source. Download the tarball and then run:<br />
tar xzfv mumble.tar.gz<br />
cd mumble-x.x.x # (whereas the X are the version number of mumble)<br />
Read the linux specific entries in the INSTALL file, since there you get to know about the pre-requisites needed for compilation. Be sure to have everything installed and in place for your linux distribution.<br />
<br />
Then run:<br />
qmake main.pro<br />
make<br />
<br />
After the compilation is finished, you will find the binaries in the directory "release". To run it there:<br />
cd release<br />
./mumble<br />
<br />
==Mac OS X==<br />
Precompiled Mac OS X universal binaries are available from the [http://sourceforge.net/project/showfiles.php?group_id=147372 SourceForge downloads page].<br />
<br />
You can also build it from source yourself if you wish. See [[BuildingMacOsX]] for more information.<br />
<br />
=Post-installation tips=<br />
==Common tips==<br />
===Initializing/Resetting Murmur password===<br />
Type:<br />
murmur -supw <password><br />
That will change the password for SuperUser, a special user that has all rights.<br />
If you want to reset the entire database, just delete murmur.sqlite and the recreate it with the command above.<br />
<br />
==Windows==<br />
===Text-to-Speech===<br />
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 [http://www.nextup.com NextUp]).<br />
<br />
===Creating a server connection shortcut===<br />
You can right click on your desktop and choose "New" and pick "Shortcut" from the sub-menu.<br />
In the box that says "Type the location of the item" put "mumble://username:password@servername/channel"<br />
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. <br />
<br />
===It complains about mumble_ol.dll / Problems with Overlay===<br />
If you are running XP you will need to update it to SP2. You also need to update to the latest DirectX9 version that can be downloaded from the [http://www.microsoft.com/downloads/details.aspx?FamilyId=2DA43D38-DB71-4C1B-BC6A-9B6652CD92A3&displaylang=en Microsoft site]. The [http://www.microsoft.com/downloads/details.aspx?FamilyID=b406cf67-d926-463b-99e8-27199d6626b5&DisplayLang=en June 2007 version] should be enough.<br />
<br />
=== Murmur dies when I log out! How can I get Murmur to stay on all the time? ===<br />
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.<br />
<br />
Some references you'll see int his write-up:<br />
<br />
instsrv.exe - A program that adds services to the Windows registry.<br />
<br />
srvany.exe - A program that allows any Windows application and some Windows 16-bit applications to run as a service.<br />
<br />
'''The HOW-TO'''<br />
<br />
Step 1: Gain Administrator access on the machine running Murmur.<br />
<br />
Step 2: Download and install the following collection of tools from Microsoft to the default directory (C:\Program Files\Windows Resource Kits):<br />
<br />
[http://www.microsoft.com/downloads/details.aspx?FamilyID=9d467a69-57ff-4ae7-96ee-b18c4790cffd&displaylang=en Windows 2003 Server Resource Kit].<br />
<br />
Step 3: Open a command console (Start >> Accessories >> Command Prompt).<br />
<br />
Step 4: If you have installed to the default directory, type the following:<br />
<br />
"C:\Program Files\Windows Resource Kits\Tools\instsrv.exe" "Murmur" "C:\Program Files\Windows Resource Kits\Tools\srvany.exe"<br />
<br />
Below is an example of what you should see:<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/command.jpg<br />
<br />
The result of this step is a new service in the Services console (Start >> Control Panel >> Administrative Tools >> Services).<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/service.jpg<br />
<br />
'''Be sure to close the Services console before proceeding.'''<br />
<br />
Step 5: Open the registry editor (Start >> Run and enter "regedit") and navigate to the following key:<br />
<br />
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Murmur Demo<br />
<br />
Regedit should look something like this:<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/regedit.jpg<br />
<br />
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.<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/newkey.jpg<br />
<br />
Step 7: Name this new key "Parameters"<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/parameters.jpg<br />
<br />
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.<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/newstring.jpg<br />
<br />
Step 9: Name this new String value "Application".<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/application.jpg<br />
<br />
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.<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/editapplication.jpg<br />
<br />
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:<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/final.jpg<br />
<br />
Step 11: Close Regedit<br />
<br />
Step 12: Open the Services console. Navigate to your service, and right click it and select Properties.<br />
<br />
http://soapbox.sytes.net/Portals/soapbox/Mumble/panel.jpg<br />
<br />
Step 13: Make sure the Startup Type value is Automatic, and then press the Start button.<br />
<br />
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.<br />
<br />
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.<br />
<br />
If your server did not start, recheck your settings. Most problems are related to typos in configuration settings.<br />
<br />
==Linux==<br />
===Getting the Shortcuts to work===<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 />
===Running murmur as a SysV service===<br />
You can use [[Murmur_Init_Script]].</div>Haudrauf