{{Infobox Software
| name = Mumble
| logo = File:Mumblesoftwarelogo.png
| screenshot = File:Mumble-1.3.0-lite.png
| caption = Main view of Mumble
| developer = [https:github.com/orgs/mumble-voip/people Mumble VoIP Team]
| repo = {{URL|https://github.com/mumble-voip/mumble}}
| programming language = C++
| operating system = Linux, Windows, macOS, Android, iOS
| license = New BSD License
| website = mumble.nixnet.services

'''Mumble''' is a free, open source, high quality, and low latency voice chat software. Primarily intended for gaming, it is also commonly used for recording podcasts and collaborating on software development as well as in a lot of other situations. If you want to use my server for pretty much anything related to voice (podcast, call, D&D session, collaborative software development), [https:nixnet.services/contact let me know] and I'll create a channel and give you admin. Refer to the Administration section for how to manage it.

Make sure you read the Privacy Policy and Terms of Service.

Installation =

Downloads for various operating systems can be found on the [https:www.mumble.info/downloads/ Mumble website]. For most Linux distributions, you can also just use your package manager: <code>sudo pacman -S mumble</code> for Arch, <code>sudo apt install mumble</code> for Debian, and so on. For Android, [https:f-droid.org/packages/se.lublin.mumla/ Mumla] is quite good. It does crash when you import a certificate though. The '''best''' experience is on desktop Linux; some people have weird audio issues on other platforms but I don't know of anyone who's had any problems on Linux.

Usage =

Launch the application then '''go through the Audio Wizard'''. It will help you identify most issues and get them resolved before connecting to the server. Once that's finished, a dialogue should pop up prompting you to connect. Click <kbd>Add New...</kbd>, enter <code>mumble.nixnet.services</code> as the address, leave the port as default, enter the username you'd like to use, then give the server a friendly name with the <kbd>Label</kbd> box. You'll be able to quickly connect to the server again by clicking it as an option under <code>Favourite</code>.

After joining, you'll notice that there are a variety of channels under <code>Root</code>. To make the UI a bit easier to navigate, I recommend clicking the arrows to the left and collapsing them so you don't see all the subchannels and users within them. To join them, just double-click the channel.

Noise Suppression ==

Mumble has the ''best'' noise suppression I've ever encountered ([https:github.com/xiph/rnnoise RNNoise]) but it's disabled by default for some reason. To enable it, go to <code>Settings</code> -> <code>Audio Input</code> -> <code>Audio Processing</code> and check the bottom box to enable <code>RNNoise</code>. If you want, you can also crank the <code>Noise Suppression</code> slider alllll the way up.

Global info =

  • '''Hosted Groups''' are different communities that have requested channels; if you're a member of one, you'll have been told which to use. Otherwise, please refrain from joining them. If you want a channel for your group, [https:nixnet.services/contact contact me] and I'll get you set up.

  • '''General''' is exactly what it sounds like; general discussion and hangout for anyone who feels like participating. It's typically empty 😉

  • '''Redacted Life''' is a podcast by Amolith (me); the website can be found at [https:redacted.life redacted.life]. The channel currently unused but I eventually plan to do live recordings and interviews with people there.

  • '''Gaming''' is for people who are gaming together! If there are people already in one room, please join the next. If they're all full, [https:nixnet.services/contact send me a message somewhere] and I'll create a new one.

  • '''Private''' is simply for people wanting to have a private conversation. Even more important with these, if one room already has people in it, ''do not enter''. Just join the next one down the list or [https:nixnet.services/contact send me a message] and I'll create a new one.

Guidelines =

NixNet channels ===

(including Redacted Life)
In general, please be respectful of other users, especially around people you don't know. When first starting the application, go through the audio wizard. As stated elsewhere, if you don't have headphones, enable push-to-talk to reduce echo. When other people are talking, don't talk over them and wait until there's an opening. '''Don't yell'''; not only does it contribute nothing but the distortion is incredibly annoying.

Hosted Communities ===

Abide by whatever the admin of that channel says.

Gaming groups ===

As long as there's not a serious problem like harassment, bullying, etc., I'm not going to step in. If the dynamic of your group is hurling good-natured insults at one another and screaming your head off, go right ahead.

Administration =

Mumble has a very odd way of granting different permissions to different users. This is done via the Access Control List (ACL).

The nearby screenshot shows the default permissions for ''all'': everyone who joins the channel. There's also ''admin'', ''auth'', and whatever custom groups you create. The latter is where you add admins and mods.
thumb|Screenshot of the ACL pane

Click <code>Add</code> then fill the <code>Group</code> box in with some random (or predetermined) string such as <code>shoh5quei4moeTh7daigoh9ah</code>. Enter this in the box like <code>#shoh5quei4moeTh7daigoh9ah</code>. Set the permissions you want them to have (<code>Write ACL</code> means they have full admin) then send the original string to the people you want administering or moderating. They'll need to put this in their Access Tokens which can be found in <code>Server</code> -> <code>Access Tokens</code>. I also recommend having them register and go through the certificate wizard; this will ensure their username can't be taken by anyone else.

If you have <code>Write ACL</code> permissions in a specific channel, you can then create subchannels within and build a hierarchy for different purposes. "Admins" typically have this permission but may be slightly restricted according what the parent channel's owner decides. ''Personally'', I create a subchannel for some purpose and give the person requesting the channel the <code>Write ACL</code> permission so they can do what they will with it from then on; it's their space to use as they see fit.

Troubleshooting =

If you're having issues, [https:nixnet.services/contact let me know], we'll get it resolved, and I'll add the problem/solution here.