https://wiki.mumble.info/api.php?action=feedcontributions&user=Mit+service&feedformat=atomMumble Wiki - User contributions [en]2024-03-29T13:03:53ZUser contributionsMediaWiki 1.31.0https://wiki.mumble.info/index.php?title=Skins&diff=2172Skins2008-08-11T05:37:27Z<p>Mit service: </p>
<hr />
<div>== Skin Websites ==<br />
<br />
Here are some sites hosting skins:<br />
*[http://mumble-tower.de/download Mumble-tower downloads] skin downloads<br />
*[http://www.clandooc.de/content/mumble_skins/index.php clandooc.de] skin-list with screenshots<br />
*[http://zavaboy.com/mumble zavaboy designs] skin downloads with screenshots<br />
*[http://www.radiusdesign.fr/download.php?view.3 radiusdesign] skin download with screenshot<br />
== See Also ==<br />
*[[Skinning]] for a tutorial on how to skin</div>Mit servicehttps://wiki.mumble.info/index.php?title=FAQ/English&diff=1922FAQ/English2008-01-28T06:28:38Z<p>Mit service: /* Shortcuts don't work on Linux */</p>
<hr />
<div>= This Document in other Languages =<br />
<br />
This Document is available in following Languages:<br><br />
[[FAQ_(English)|English]]&nbsp;&nbsp; [[FAQ_(Deutsch)|Deutsch]]<br />
<br />
<br />
= About Mumble =<br />
<br />
<br />
== What is Mumble? ==<br />
<br />
Mumble is a voice chat application for groups. While it can be used for any kind of activity, it is primarily intended for gaming.<br />
<br />
== What platforms does it run on? ==<br />
<br />
The client, Mumble, runs on Windows XP and Linux. The server component, Murmur, should run on anything you can compile Qt 4.0 on.<br />
<br />
== What are the system requirements? ==<br />
<br />
The client runs on any Linux or Windows XP machine, and you also need a microphone. The server is mostly bandwidth bound, so as long as your network hardware is sufficient it should run on pretty much anything.<br />
<br />
Please note that the binaries distributed from SourceForge are compiled for SSE (Pentium 3 or Athlon-XP). Mumble is a VOIP solution for gaming, and as most modern games require at least that good a CPU it makes little sense for us not to optimize for it.<br />
<br />
== Installing Mumble ==<br />
Prebuilt binary packages can be downloaded from SourceForge[http://sourceforge.net/projects/mumble/] if you're running Windows or an i386 Linux distribution with the Debian package manager installed.<br />
Installation sources:<br />
*Windows: [http://sourceforge.net/project/showfiles.php?group_id=147372 SourceForge]<br />
*Linux:<br />
**Debian, Ubuntu, etc: [http://sourceforge.net/project/showfiles.php?group_id=147372 SourceForge] (.deb) or Treviño repository ([http://3v1n0.tuxfamily.org/])<br />
**RPM based distro's: You could try [http://sourceforge.net/forum/forum.php?thread_id=1782689&forum_id=492606 a rpm found in the forum]. <br />
**Gentoo: ''emerge mumble'' should do it (You'll need sqlite and/or sqlite3 flags enabled, and reemerge qt4 if it was emerged without them)<br />
**Archlinux: You can find a PKGBUILD in the AUR: [http://aur.archlinux.org/packages.php?do_Details=1&ID=10221]<br />
<br />
'''Disclaimer''': Only the files are SourceForge are official. Be careful with the other ones.<br />
<br />
For those who need to (or want to), here are two good tutorials for compiling Mumble/Murmur for your system:<br />
*Linux - [[Building_from_Source]]<br />
*Windows - [[BuildingWindows]]<br />
<br />
== What makes Mumble better? ==<br />
<br />
Mumble has very low latency combined with good sound quality; it uses Speex extensively, not just the voice compression technology, but also the voice preprocessing to remove noise and improve clarity. Mumble also has positional audio for supported games, meaning the other players' voice will come from the direction their character is in game.<br />
<br />
== What are the bandwidth requirements? ==<br />
<br />
From 0.9.1, this is highly variable, and mostly up to the user. With top quality, minimum latency and positional information sent, it is 64.6 kbit/s including the IP and UDP overhead. With 80 ms transmission delay, the lowest quality speech and no positional information, it is 11.0 kbit/s (again with IP and UDP overhead). The default uses 45.4 kbit/s; we did not hear any noticable improvement in quality from the last 20 kbit/s. When comparing with other products, remember to compare the total bandwidth use and not just the bitrate of the audio encoding.<br />
<br />
There are two parts to tuning the bandwidth; the audio bitrate per audio frame (20ms) and the amount of frames to put in each packet. Each transmitted packet has a overhead of 28 bytes from IP and UDP alone, so at the highest transmission rate (50 packets per second), that is 1400 bytes of data for raw network overhead alone. You should try to find a balance that works well for you, but we generally recommend sacrificing high audio bitrate for lower latency; Mumble sounds quite good even on the lowest quality setting.<br />
<br />
There is no way to adjust the amount of incoming bandwidth; you will have to have enough to sustain the total amount of speaking players. This should be a minor issue; most players these days are on asymetric lines and hence it is only upload that is a bottleneck.<br />
<br />
== What tools did you use to make this? ==<br />
<br />
See [[Development Tools]].<br />
<br />
== How can I help? ==<br />
<br />
A good start would be just using Mumble. If you like it, tell all your friends. If you do not like it, tell us what is wrong so we can fix it.<br />
<br />
= Audio Features = <br />
<br />
== How does the positional sound work? ==<br />
<br />
Your position ingame is transmitted along with every audio packet, and Mumble uses standard DirectSound 3D to position the audio on the receiver side. Only games for which a plug-in has been written get positional audio. All other games will work as well, you just will not get 3D sound.<br />
<br />
== Why does Mumble sound so much better than other voice products? ==<br />
<br />
One word: Denoising. This is a standard part of Speex 1.1 and above, and any voice product already implementing speex should be able to trivially include the same filtering. <br />
Removing the noise from the input means that the audio will be clearer and that the needed bitrate will decrease. It takes fewer bits to model clear voice than it does to accurately represent the noise, so in any noisy transmission a large share of the bits will be noise modelling.<br />
<br />
== Where is the volume control? ==<br />
<br />
Mumble uses the default volume you have configured in your operating system. There is no support for amplifying incoming voices, and there probably will not be, as this will decrease audio quality, something we are very reluctant to do.<br />
<br />
== The text-to-speech quality is horrible! ==<br />
<br />
We use the standard MS Speech API, and the included voices are not all that good. If you have installed either MS Office or the Speech SDK, you will get more voices which can be configured from the Speech control panel. You can also buy a commercial Text-To-Speech engine; as long as it's SAPI5 compatible it can be used by Mumble. The main developers are currently using NeoSpeech Kate (buyable standalone from [http://www.nextup.com NextUp]).<br />
<br />
== Why do some voices sound metallic? ==<br />
<br />
Mumble uses Speex noise filtering, and if the environment of the sender is especially noisy, some parts of the voice will be filtered as well. The alternative would be noisy sound, meaning precious bandwidth would be used to encode noise and the clarity of the voice would also decrease.<br />
<br />
== Why doesn't the voice activity detect my voice any more? ==<br />
<br />
If you change your audio environment suddenly and drastically, by for example disconnecting and reconnecting your microphone or dragging a piece of paper directly over the microphone, you will throw the voice preprocessor off balance. It will recover, but it will take time. <br />
<br />
To reset the preprocessor, choose 'Reset' from the 'Audio' menu.<br />
<br />
== What is this weird echo I hear of myself from other users? ==<br />
<br />
Unfortunately, a lot of popular headsets produce tiny traces of echo. In other VOIP products, you will not notice it because the echo is lower than the noise level, but as Mumble dutifully removes all noise, the echo suddenly becomes clear. There is little the person hearing the echo can do, but there are a few things the person producing the echo can do. The easy solution is to use ASIO and enable echo cancellation, however this requires that the headset is of the analog type (no USB) and a very high quality soundcard.<br />
<br />
The more troublesome solution is to modify the headset. If it is possible to pry the arm with the microphone from the headphones, do so and reattach it with a thick piece of rubber tape; this should insulate it from vibrations. If your headset is open (no large earmuffs), there exists an echo path through air from the headphones to the microphone. You can fix this by attaching anything foam-like to the front of the headphones to muffle the sound heard outside them, but this will most likely ruin the ergonomics of the headset as well as look somewhat odd.<br />
<br />
We might put up a page of "tested headsets" if anyone wants it.<br />
<br />
= Server =<br />
<br />
== What sort of bandwidth will I need for the server? ==<br />
<br />
Worst case scenario: Number of users &times; Number of talking users &times; 60 kbit/s. With less aggressive quality settings, it's ~20 kbit/s, and the bare minimum is 12kbit/s. Note that Mumble is geared towards social gaming; its quality enables people to talk naturally to each other instead of just barking short commands, so the amount of "users talking at the same time" can be somewhat higher than expected.<br />
<br />
This means that a server with 20 players and 2 players talking at once requires 0.8-2.4 Mbit/s, depending on quality settings. In the server's .ini file, you can specify the maximum allowed bitrate for users as well as the maximum number of clients to allow.<br />
<br />
== Where do I configure the welcome message, listen port and so on? ==<br />
<br />
murmur.ini, it is self-documenting.<br />
<br />
== How do the ACLs work? ==<br />
<br />
See [[ACL and Groups]]<br />
<br />
== mumble.pri:8: Unknown test function: CONFIG ==<br />
<br />
Mumble requires Qt version 4.3 or better; you are running qmake from Qt 3<br />
<br />
== Where is the administrator account? ==<br />
<br />
The topmost user in the Mumble hierarchy is the useraccount "SuperUser", which bypasses all permission checks and is always allowed to do anything. SuperUser can't be used as a normal user account (it can't talk) and should only be used for initial configuration or to recover from misconfiguration.<br />
<br />
To set the superuser password, start murmur with<br />
murmur.exe -supw supersecretpw<br />
or<br />
murmurd -supw supersecretpw<br />
<br />
== How can I reset the database? ==<br />
<br />
Delete the murmur.sqlite file.<br /><br />
Rerun the command:<br /><br /><br />
<br />
<code><br />
murmur -supw <password><br />
</code><br /><br />
<br />
== How can I add an user? ==<br />
See [[Registering_users]]<br />
<br />
== How can I change a users password? ==<br />
<code><br />
$ '''sqlite3 murmur.sqlite'''<br /><br />
sqlite> '''UPDATE players SET pw = 'newpassword' WHERE name = 'playername';'''<br /><br />
sqlite> <Ctrl-D><br /><br />
</code><br />
<br />
== How do I backup the database? ==<br />
<br />
Shut down the server (kill the process), and make a copy of murmur.sqlite. That file is the database.<br />
<br />
<br />
== How do I run Murmur as a Linux/Unix Sys V service? ==<br />
<br />
See [[Murmur Init Script]]<br />
<br />
<br />
== How can I use an external database for Murmur? ==<br />
<br />
See [[Murmur and PostgreSQL]]<br />
<br />
= Common Problems and Resolutions =<br />
<br />
Problem: Webserver not able to write to DB when using murmur.cgi. <br />
<br />
Solution: Make sure both DB and directory that DB is in is writing be the webserver user.<br />
<br />
Problem: Error message in murmur.cgi line 118<br />
<br />
Solution: You need an MTA on localhost unless you have defined a different SMTP server.<br />
<br />
Problem: Connecting, but not able to create/join channels<br />
<br />
Solution: You currently cannot use the 0.9.1 client with the CVS version of the server (0.9.2).<br />
<br />
Problem: Can't find Push to Talk button<br />
<br />
Solution: When you set Push to talk in Configure > Settings > Basic Audio, you then need to also bind a key to PTT. You do this in Configure > Settings > Shortcuts.<br />
<br />
== Failure to load mumble_ol.dll ==<br />
<br />
If you are running Win XP with SP2, this is due to a outdated DirectX. DirectX is actually updated each and every month, which is why you see every game trying to update your DirectX. So while the version may be 9.0c, what you want to look at is the release date. The latest version may be found at<br />
http://www.microsoft.com/windows/directx/default.mspx<br />
<br />
Downloaded, extracted and installed this package and it fixed this problem for me: [http://www.microsoft.com/downloads/details.aspx?FamilyID=b406cf67-d926-463b-99e8-27199d6626b5&DisplayLang=en DirectX End-User Runtimes (June 2007)] --[[User:Iam8up|Iam8up]] 08:01, 10 July 2007 (PDT)<br />
<br />
== Can't hear other users/users can't hear me ==<br />
<br />
This seems to be fixable by experimenting with the "Use TCP mode" checkbox in "Basic Audio" settings.<br />
<br />
Also this problem can happen if you have server with multible IP's, you need to use server PRIMARY IP or you will experience random "can't hear you, but you can hear me" issues. Not sure is it possible to bind murmur just use one IP from box.<br />
<br />
== Shortcuts don't work on Linux ==<br />
There are two alternatives:<br />
Either use native input or Xevie.<br />
<br />
For native input make sure that the user running Mumble has read permissions on the /dev/input/eventX files of the input devices you want to use for shortcuts.<br />
Be aware that too weak permissions may be a security risk, because malicious processes may log all your input.<br />
<br />
If Mumble can not read from any input device it falls back to Xevie.<br />
<br />
You need to have Xevie enabled in your xorg.conf. To do this you will have to add the following line to xorg.conf, in the extensions section:<br />
<br />
Option "XEVIE" "Enable"<br />
<br />
That should like something like this:<br />
<br />
Section "Extensions"<br />
...<br />
Option "XEVIE" "Enable"<br />
...<br />
EndSection<br />
<br />
Then restart the X server (Ctrl+Alt+Backspace) and try again.<br />
<br />
== Keys seem to lock when using Shortcuts on Linux ==<br />
<br />
Sometimes, keys get "locked" when using Xevie. For example, you press two keys at the same time, but when you release them, only of them is detected as released. This is better seen on games, when you start moving diagonally, and when you stop, it keeps moving.<br />
This can be fixed by playing around with the key repetition settings which can be found:<br />
* Gnome: System->Preferences->Keyboard<br />
* KDE: K menu->Control Center->Peripherals->Keyboard<br />
<br />
You can try changing the Speed/Rate slider and disabling the key repetition (first checkbox)</div>Mit servicehttps://wiki.mumble.info/index.php?title=Installing_Mumble&diff=1921Installing Mumble2008-01-25T13:46:39Z<p>Mit service: /* Getting the Shortcuts to work */</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 [[Building_from_Source]].<br />
<br />
===Ubuntu ===<br />
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. '''Warning:''' the package is Ubuntu only as it depends on specific ubuntu versions of libraries. If you are not sure how to do this, just head to a console and type the following as root:<br />
<br />
dpkg --install mumble_1.0.0_i386.deb<br />
<br />
Of course, change the version number as appropriate. <br />
You can also try using the [http://3v1n0.tuxfamily.org/ Treviño repository]. Just add it to your repository list, update the package list and install 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 xfv 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 />
There are currently no precompiled Mac OS X binaries. But you can build Mumble yourself from source as described in [[BuildingMacOsX]].<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>Mit servicehttps://wiki.mumble.info/index.php?title=ACL_Tutorial/English&diff=1791ACL Tutorial/English2007-11-06T13:21:40Z<p>Mit service: /* Setting permission for the whole server */</p>
<hr />
<div>= This Document in other Languages =<br />
<br />
This Document is available in following Languages:<br><br />
[[ACL_tutorial_(English)|English]]&nbsp;&nbsp; [[ACL_tutorial_(Deutsch)|Deutsch]]<br />
<br />
<br />
=ACL tutorial=<br />
This tutorial will help you understand how permissions work on Mumble. Details about this topic can be found in [[ACL and Groups]], where there are some examples, descriptions of special groups, etc.<br />
<br />
==What we are going to do==<br />
We are going to set a server, with a ''General chat'' channel where everyone can talk. We are also creating a ''Custom channels'' channel where anyone who is authed can create and administrate his own channel.<br />
Then, as a normal authed user, we will create a couple of channels for a FPS game where people can talk either to their team or to everyone just by pressing one key.<br />
<br />
Enough talking, let's get to work.<br />
<br />
==Setting permission for the whole server==<br />
First, we will need to set up a password for the SuperUser. If you haven't done that yet, you can do it by typing this at a console/command prompt:<br />
murmur -supw somepassword<br />
<br />
Then, we open Mumble and connect to the server using SuperUser and the password we have just set. You should be looking at something like this now:<br />
<br />
http://img361.imageshack.us/img361/6586/mumbletut1dx8.png<br />
<br />
Let's start with the permissions. Open the ACL editor, you can do this by selecting "Edit ACL" from the Channel menu. Once we are there, you can see a window with two tabs. The first one is for defining people who are in a group, etc. The second one is used to assign permissions to groups. <br />
Right now, in that tab, you should have two rules set: <br />
*The first one allows people on the auth group to create channels in the root channel and its subchannels.<br />
*The second one allows people in the group admins to ''Write'', that means edit permissions.<br />
<br />
For now, we will delete the rule related with the auth group by selecting it and clicking remove. We said that we don't want anyone in the root channel, as we will make a ''General chat'' channel for that. So we will add a rule to keep them out. To do that, click add, and click every checkbox in the deny column except the ''Traverse'' one.<br />
<br />
The reason to leave traverse unchecked is because it will forbid people to enter this channel '''and''' subchannels. Since every other channel is a subchannel of root, this will effectively forbid people from entering any channel. So we leave it unchecked. It is not neccesary to mark the allow check, because ''Traverse'' is allowed by default. Default settings are:<br />
*Allow: Traverse, Enter, Speak and AltSpeak<br />
*Deny: Write, Mute/Deafen, Move/Kick, Make Channel and Link channel<br />
<br />
If you are wondering, yes, we could have left Write, Mute/Deafen, Move/Kick, Make Channel and Link channel unchecked and they will still be forbidden. There is no reason to leave those rights denied as they will be by default. Now your screen should be looking like this (except that you have disabled some useless checks):<br />
<br />
http://img361.imageshack.us/img361/9215/mumbletut2hw0.png<br />
<br />
In Mumble, rules are applied from top to bottom. Right now, the:<br />
@admins allow write<br />
rule is useless as it will get over written by the<br />
@all deny write ...<br />
So we will have to fix it. Simply select the rule referring to all and click up. That should put that on top. You have now established some default settings for the whole server :)<br />
<br />
http://img363.imageshack.us/img363/3368/mumbletut3if8.png<br />
<br />
==Creating the ''General chat'' channel and setting its permissions==<br />
This channel will serve as a chat room for everyone that gets to join our channel. Since we don't allow them to speak in the root channel, and they must join this channel if they want to chat, maybe we should put a welcome message to the server that warns about that. Anyways, here we go.<br />
First, create the channel. This is as easy as clicking Channel->Add (or right-clicking in the channel you want and click add to create a subchannel, but you know, root isn't shown, so we will use the menu one). In the box that appears type the channel name, click ''OK'' and we are done.<br />
<br />
Now, we want to give the right for everyone to speak here. So we head to ''Edit ACL'' (remember to select the new channel before). You will see the rules of the root channel, but if you select them, you will see that all the options are grayed out. That's because they are inherited from the parent channel (in this case, ''Root''). If you uncheck the ''Inherit ACL's'' option, they will disappear, but we don't want that. Just add a new rule that allow everyone (group=all) to Speak or AltSpeak and click ok to save it. We are now done with this channel. Easy, no?.<br />
<br />
http://img372.imageshack.us/img372/2854/mumbletut4wu0.png<br />
<br />
==Creating the ''Custom channels'' channel and configuring it==<br />
As we said, we will let anyone who is registered to create his own channel here. The first step is easy, create the channel just as we did before. You should have something like this just in front of your nose:<br />
<br />
http://img361.imageshack.us/img361/1720/mumbletut5qo2.png<br />
<br />
Now we'll be giving ''Make channel'' rights to authed people. Just go to ACL editor, add a new rule, in the group list select or write auth and select the allow make channel checkbox.<br />
'''Warning:''' If you type the group name, make sure you press enter when you've finished. This will update the rule group. You can see that if tou type and don't press enter, it will not change the group in the top listing.<br />
<br />
http://img356.imageshack.us/img356/7333/mumbletut6vl9.png http://img387.imageshack.us/img387/6638/mumbletut6bsq9.png<br />
<br />
And now we have a pretty channel when people can create his own channel. Note that they cannot even enter ''Custom channels'' channel but they still can create subchannels. Isn't it cool?<br />
<br />
=Registered user=<br />
In this part, we will be playing a registered and authed player with a veeeeery original name: AuthedPlayer. He will be creating his own channels to host a little public channel and two private subchannels, one for each team of a FPS game. He would like that they can talk to their team or to both teams. We are seeing how to do this with the AltSpeak right, linking channels and more.<br />
<br />
==Creating the main channel==<br />
After logging in, we may play a little to check that we can't enter the root channel once we leave it (the first time you connect you will land here), that we cannot enter the ''Custom channels'' channel, etc. Once we have checked that permissions are working as expected we start creating our first channel. We simply right click in ''Custom channels'' (remember that you can still use the menu) and click add to create a new channel. As I am very creative I called it ''My Private Channel''. Automatically we are added to the admins group in that channel, so we can ''Write'' on it (remember the rules in the root channel? they are inherited all the way down to our channel). But that also mean that we get the ''Make channel'' permission inherited, so everyone who is authed can make a channel inside ours. We don't like that so...<br />
<br />
http://img400.imageshack.us/img400/2249/mumbletut7dw7.png<br />
<br />
Our rule will overwrite the inherited one, because inherited rules are always put at top. So now that we have our channel secured, we will give permission to enter and speak:<br />
<br />
http://img387.imageshack.us/img387/2315/mumbletut8lu5.png<br />
<br />
Note that we have disabled ''Applies to sub-channels''. As subchannels will not be public, we don't want them to have the ''Enter'' permission granted. If we haven't disabled this option, we have to create yet another rule just to deny the ''Enter'' permission. This way is easier. And now, we have this channel ready for service. Let's continue with the subchannels.<br />
<br />
==Creating the team subchannels==<br />
First, we create two subchannels of our own channel. As usual I called them in a very creative way... Team1 and Team2. We could define rules for each one, but it is quicker to define them in the parent channel (My Private Channel) and make the subchannels inherit the rules. First, we want people in one team channel to be able to speak so we do it like that:<br />
<br />
http://img452.imageshack.us/img452/2127/mumbletut9ix7.png<br />
<br />
Notice that we have unchecked the ''Apply to this channel'' option, as we are defining this rule only for the subchannels. More interesting is the use of the speacial group ''in''. This group refers to the people that are inside the channel the rules refers to. It appears it is the same as all, but it is quite different: <br />
We are going to link both channels. That means that people in different channels will hear each other. But we want that people only can hear teammates. So we use ''in'' to give Speak privileges to people in the same channel. This means, people in Team2 can't hear people in Team1 because the people in Team1 don't have rights to speak in Team2 because the ''in'' group only gives them permission in his own channel. It is a little complicated to understand at first, but it is very useful. To understand it, you have first to understand that each channel has its separate groups. That means that ''in'' group in Team1 is no the same group that ''in'' group in Team2.<br />
<br />
To explain it better I'm going to use some names...<br />
*Jack is in Team1<br />
*John is in Team2<br />
Both channels are linked, so the voice will be transmitted from one to the other as long as the speaker have rights in the destination channel. Jack speaks but John will not be able to hear it. That is because Jack has no rights to speak in Team2 as it is not in the Team2's ''in'' group. So voice will not be transmitted across the channel link and John will not be able to hear Jack.<br />
If we have used ''all'' instead of ''in'' for the rule, Jack and John will hear each other without a problem, as everyone is in ''all'' group.<br />
<br />
Well, let's continue. We wanted to people talk to the other team. This is when AltSpeak comes handy. We add a rule like this:<br />
<br />
http://img359.imageshack.us/img359/7660/mumbletut10sq9.png<br />
<br />
This will allow everyone (both teams) to talk to each other when AltSpeaking. AltSpeak is enabled while pressing a key defined in Shortcuts (in the Mumble options). While holding down that key, voice will be transmitted using the AltSpeak rights. As we allowed anyone to AltSpeak and both channels are linked, that means that if someone talks while pressing the key, it will be heard by both teams.<br />
<br />
And we are done.<br />
<br />
==How it looks like for some anonymous players==<br />
First you "invite" them to your team channels (you can move them from your public channel to your team channels by drag-and-drop). They have to be in your public channel to do that, as you will need Move permissions in both the origin and destination channels. If not AltSpeaking...<br />
<br />
http://img361.imageshack.us/img361/3603/mumbletut11zg8.png http://img358.imageshack.us/img358/6740/mumbletut11bkf8.png<br />
<br />
If AltSpeaking:<br />
<br />
http://img361.imageshack.us/img361/5271/mumbletut12ef3.png http://img462.imageshack.us/img462/8103/mumbletut12bko1.png<br />
<br />
=Final notes=<br />
This is a quick tutorial and I have not explained a lot of things. For example custom groups. They should be easy to figure out but here goes a quick explanation:<br />
*You define rights for that group by simply writing the group name in the group box (remember, ENTER is your friend;)) and marking the appropriate checkboxes. <br />
*To add a person to the group you go to the other tab in the ACL editor, select the group name in the group box (or write it+enter), write the name you want to add in the box at the botton of the added list and press the corresponding add button. You can only add registered nicks to that list.<br />
*Groups are per-channel and are inheritable. If you want to inherit some group members, you can mark inherit and add the members you don't want to be part of the group in the specific channel to the remove list (there is a button at the end of the inherited list to make this easy).<br />
I have also left behind the use of the sub group. You can find more info about that in [[ACL and Groups]]<br />
<br />
There are a lot of rules that could have been made easier. For example, in the last part of the tutorial, you could stick the ''deny Make Channel'' and the ''allow AltSpeak'' in the same rule applied to both channel and subchannels. This is just an example of which can be made without going too deep, feel free to create your own impossible-to-understand layouts and add them to the examples section in [[ACL and Groups]]<br />
<br />
And last but not least, please leave a comment in the discussion page of this article if you feel like that. Thanks :)</div>Mit servicehttps://wiki.mumble.info/index.php?title=Commercial_Hosting&diff=1767Commercial Hosting2007-10-25T13:23:07Z<p>Mit service: /* Multiserver support */</p>
<hr />
<div>Mumble (and murmur) are open source, and therefore completely free of charge. However, to fully experience the quality of Mumble, a quality server with good network connection is needed. Home-based DSL or Cable servers are far from optimal, and do not scale to much more than 5-6 users.<br />
<br />
We are therefore interested in facilitating commercial hosting of murmur, to enable users who lack either the server hardware and network connection or the skill to compile and maintain murmur to use Mumble.<br />
<br />
This page is specifically targeted at commercial hosting providers. This is where we'll present a short summary of murmur's expected resource requirements, and where you can edit it to provide us with information on what you need to make your job easier.<br />
<br />
= Murmur technical requirements =<br />
<br />
Murmur runs on any operating system where Qt can compile. At the moment, that is "most" UNIXes, Windows and MacOSX. Our internal testserver runs on Linux, and a binary version for Windows is included in the mumble installer.<br />
<br />
Based on data from out testserver, murmur will use about 40 MB of virtual memory, of which about 4 MB are resident in physical memory.<br />
<br />
As no processing is done serverside, we were not able to push even 1% of actual CPU usage with 4 users on a Xeon 3.4Ghz. We do see quite a few context switches though, so high quality network cards is likely a requirement.<br />
<br />
Mumble uses VBR speex, and using the highest quality and lowest latency, the peak bandwidth is 65kbit/s per speaker per listener (with IP and UDP overhead). <br />
In other words, a server with 10 users and 1 user speaking will need to replicate the datastream 9 times, for a total of 65*9=585kbit/s outgoing bandwidth. If all 10 users speak at once, each stream has to be replicated 9 times, for a total of 65kbit/s*9*10=5.8 Mbit/s. Note that these are absolute worst-case scenarios, and the average bandwidth use is around 20-30 kbit/s during speech, multiplied by the number of listeners.<br />
<br />
= Licensing =<br />
<br />
Murmur and Mumble is GPL, which means that much like the Linux kernel, you are free to use it in commercial hosting without royalties. You are selling a service, not a program.<br />
<br />
= Requirements for Murmur for adoption by commercial providers =<br />
<br />
I'll note down what I can imagine commercial hosting providers would like to see implemented in murmur before they start offering it as a service. If you are a commercial provider, please comment on the below in the discussion (even if you agree, it helps to know we're on the right track), or add new sections.<br />
<br />
== Ability to limit number of users ==<br />
<br />
Set the "users" parameter in murmur.ini<br />
<br />
== Ability to limit audio quality ==<br />
<br />
Set the "bandwidth" parameter in murmur.ini, which limits the per-user incoming bandwidth. Multiply this by the number of users in a channel to find the used outgoing bandwidth per active speaker.<br />
<br />
== No frills ACLs and Groups ==<br />
<br />
The multi-channel [[ACL and Groups]] system in Mumble enables easy setup of linked channels that can match most any scenario. On the downside, it's also easy to mess up, especially if you're an inexperienced user. While this might ultimately be up to the hosting providers, we should probably provide a small example of how to use a webpage to "configure" a very basic access system, and give no users the actual "Write" bit, even the admin. This would allow those users who feel they are competent enough to log in with superuser and foul things up as much as they want, and will also allow for simple management for less sophisticated users.<br />
<br />
If anyone wishes to do so, this can now be done through the DBus RPC interface of murmur.<br />
<br />
== SQL-Server ==<br />
<br />
The default and recommended SQL engine for murmur is SQLite, since it is faster than all the other alternatives and requires less resources. From 0.9.5 onwards, murmur also supports MySQL, Postgres and any other engine that has a Qt database driver.<br />
<br />
== Multiserver support ==<br />
<br />
From version 1.1.0 onwards, murmur fully supports multiple independent virtual servers per process.<br />
<br />
Multiserver support is through dbus. You can use the newServer() call which returns a server id, then use start(id) or stop(id) to stop the server. Before you start it, you probably want to configure it, which is done through setConf(serverid, key, value). <br />
<br />
Known configuration keys are:<br />
*host - IP bound to <br />
*password - server PW <br />
*port - server port <br />
*timeout - client inactivity timeout <br />
*bandwidth - bandwidth restriction <br />
*users - max # of users <br />
*welcometext - the blurb sent by the server on connect <br />
*registername, registerpassword, registerhostname, registerurl - The data for registration in the public server list <br />
*certificate - x509 certificate in PEM form <br />
*key - x509 private key in PEM form <br />
<br />
If a config key is not present, the default is to take the value from the .ini file (except port, which defaults to inifile+server_id-1)<br />
<br />
== RPC ==<br />
<br />
Murmur supports DBus RPC calls, which allow querying all information of the server in real time, and also allow management. Hence, it's fairly easy to write scripts to query and display server status, and also to create web frontends for server administration.</div>Mit servicehttps://wiki.mumble.info/index.php?title=Games&diff=1744Games2007-10-09T08:47:01Z<p>Mit service: </p>
<hr />
<div>Please note that mumble works with '''all games''' as a regular voice chat application. The games below are the ones we've added positional sound support for, so that the voice of your teammates come from their direction in game. To enable specific game support, make sure that Config|Settings|Plugins|Transmit is set to "Position", and that Config|Settings|DirectSound|Method is set to "Panning" (or better).<br />
<br />
* Battlefield 2 (1.0.2)<br />
* World of Wardcraft (1.8.4 EU)<br />
* Trackmania United<br />
* Trackmania Nations<br />
<br />
If you are an active Mumble user and would like to see support for additional games, submit it as a feature request on sourceforge.<br />
<br />
If you want to add support for a game and you are able to modify the source of this game you can use the [[Link]] plugin.</div>Mit service