Software-update: Mumble 1.4.230

Mumble logo (75 pix) Versie 1.4.230 van Mumble is uitgekomen. Mumble is een opensource- en crossplatform-voip-programma. Clients zijn beschikbaar voor Windows, Linux, macOS, Android en iOS. De communicatie vindt altijd over een versleutelde verbinding plaats en kent een lage latency. Wordt het binnen spellen gebruikt, dan kan aan de hand van een overlay worden getoond wie er spreekt en bovendien is het programma in staat om de positie van die ander te herkennen en het geluid zo weer te geven dat je kunt horen waar die speler zich bevindt. De release notes voor deze uitgave kunnen hieronder worden gevonden.

Mumble 1.4.230

It has been over two years since we released Mumble 1.3.0. Since then many new features and improvements have found their way into the software. And not less importantly: many fixes for issues that have been encountered with Mumble. Talking about each and every change here would definitely exceed the size of any reasonable release announcement. Therefore, we will restrict ourselves to highlighting what we think are the most prominent and/or interesting changes and we invite everyone to simply try out the new version and explore what has changed yourself. For the interested reader, we of course also include a full changelog at the bottom of this page as well.

If you are wondering, why this first 1.4.x release is not versions 1.4.0, but 1.4.230, please see this recent blog post describing our new versioning scheme that explains the absence of the mentioned version numbers.

Feature spotlight

As there are many, many changes with this new version, here is a selection of things that we think are most prominent. If you’re interested in all changes, have a look at the full changelog.

Plugin framework

Mumble has supported something it called “plugins” for a very long time. However, these plugins were not what one would typically expect when hearing about them for the first time. Instead of being general-purpose, (potentially) multi-function plugins, they were only ever dedicated for providing positional data from games (generally by reading the game’s in-memory representation). In addition to that, these plugins couldn’t really be installed and updated independently from the main application (for technical reasons) and therefore, plugins were mostly a static part of the Mumble client.

With Mumble 1.4 a new, general purpose plugin framework has been introduced. With this framework, the range of possibilities offered to plugin developers has been vastly increased and most importantly plugins are no longer restricted to positional data delivery (though that is of course still possible) and they can now be installed and updated at any time, without causing incompatibilities with the main Mumble client.

If you want to find out more about this new plugin framework (including how to write your first plugin), check out the plugin documentation.

Search dialog

If you have ever been on a somewhat large-ish Mumble server, you will probably know that sometimes it can be a bit hard to find a specific user or channel. Some of you might even be familiar with the feature of “free-type search” which was a built-in search functionality that worked by simply starting to type the user’s or channel’s name while the Mumble client has focus. However, this feature was very clumsy, not well documented and quite unsuitable, if the searched-for text yields more than one match on that particular server.

In order to improve on this situation, Mumble 1.4 ships with a fully featured search dialog that can be opened either via the menu bar or via the shortcut Ctrl+F (this shortcut previously toggled the channel filter but that has been re-assigned to Ctrl+Shift+F). With this dialog you can easily search for users or channels (or both) and you can even specify whether your search string is to be interpreted as a regular expression.

Channel listeners

This feature can to some extent be compared to the ability to link channels. Except that this does not operate on a per-channel basis but on a per-user basis.

Concretely this new feature allows a user to “listen to” a channel. In that case all audio that is heard by people in this particular channel (be it by direct communication, shouts or via linked channels) is also heard by the listening user. Conceptually you could picture “listening to” a channel with placing a microphone in a room and then listening to what is recorded.

This feature is one-way only, meaning that in order to speak to people in the listened channel, you’ll have to either join the channel or shout to it.

It should be noted that you will not be secretly listened to with this new feature. Listening to a channel creates a new entry in the channel’s user-list (referred to as an “ear” or a “listener”) and is thereby just as visible as a user actually being in that channel. There is also a dedicated ACL and several new server config options that can restrict this new feature.

Older clients (< 1.4) will not indicate listeners in the UI though! However, they are informed if this feature is enabled on a server when they join it (via chat).

Note: This feature requires server-side support and therefore is only available on servers running at least Mumble 1.4.


Have you ever been in a situation where you heard someone talking but couldn’t quite figure out who it was? Then this feature is probably for you!

The TalkingUI can be considered the equivalent of the already existing overlay but for “non-gamers” or in other terms for everyday usage.

This feature adds an optional floating window, containing a list of currently speaking users and their respective channels. This allows you to quickly see who’s currently talking and in which channel that person currently is in (this becomes important if you want to respond to that person).

The big difference between the TalkingUI and Mumble’s main window (which of course also contains this information) is that the TalkingUI does not contain all the other UI elements nor does it necessarily show the entire channel-tree. Furthermore it automatically resizes itself to the minimal size needed to display the respective information. Thus it usually does not take up a lot of space and can therefore be left floating in the corner of the screen without consuming too much screen real estate.

Note that the TalkingUI is highly configurable (Settings -> User Interface) and also provides selection and context-menu support just as you get it in the main window. In fact, the selection between TalkingUI and main window is synchronized and thus this plays really nice with the new “whisper to selected” feature allowing to whisper to whatever currently is selected in the UI (be it a channel or a user).

UI indication for access restrictions

In previous versions of Mumble there was no indication of whether you are able to join a channel or not. You just had to try it out and either it worked or you got a permission denied message. This feature solves this problem by marking “access-restricted” channels with a lock icon. Access restricted channels are all channels that are either only open to a specific group on the server or require a password (access token) to join.

In total, a channel can be in one of three states: either it is not access-restricted in which case it just looks like channels used to look prior to the introduction of this feature or it is indeed access-restricted. In the latter case a lock icon is shown to the right of channel name. This look can either be open and green or closed and red. Green means that you can enter the channel nonetheless (you belong to the required group or have the correct password (access token) set) whereas red means that you are not allowed to enter the channel.

Note that this is also a feature that requires server-side support and thus only takes effect on servers that are at least running Mumble version 1.4.


For those of you who don’t know what markdown is, we recommend a quick read of the respective Wikipedia article. In simple words it allows formatting of text by simply typing a few extra characters in it.

Mumble now supports markdown for text messages written in the normal chat bar. It is not supported for cases in which you use the dedicated message editor (e.g. for private messages). Furthermore only a subset of markdown is supported: sections, inline-code, code-blocks, bold, italic and strike-through text, links and quotes. Not supported are lists and tables.

This feature is probably best explained by an example. Try pasting the following text into the chat bar and see for yourself:

# Markdown
## Code
We can have `inline` code and

## Emphasis
**bold** and *italic* (__bold__ and _italic_ also works) text is supported. ~~Scratch that~~

## Links
We can have [links]( and

## Quotes
> I am a quote
Although these are not pretty, they do work and are supported.

## Escaping
We can escape special characters using the \\ character: \*not italic\* and \*\*not bold\*\*
Stereo playback

With version 1.4 Mumble (finally) learned how to play back stereo audio streams. This means that it is now possible to send a stereo stream to a Mumble client and it will actually be played back without being mixed down to a mono stream.

Note however that this feature is currently restricted to playback. The official Mumble client will still continue sending audio as mono. This feature is primarily intended to be made use of by (music) bots.

If you want to try this feature out yourself, you can either write a bot using pymumble version 1.2 or later or you can simply use a recent version of botamusqiue.


For those of you who are annoyed by people using excessively long or complicated names or people changing their nickname frequently, Mumble 1.4 introduces the possibility to set a nickname for users.

Depending on your configuration, a nickname will either be displayed next to a user’s name or replace it entirely.

The nickname will persist across restarts of client and server. In fact it’ll last until you either remove it again or the person the nickname was assigned to changes their client-certificate (Mumble’s way of keeping track of a user’s identity).

Note that nicknames are not tied to a particular server. That means that if you assign a nickname to a user on server A and then you meet that person again on server B, they will still have that very same nickname set on server B (the same way friends are recognized across servers as well).

Mumble screenshot (620 pix)

Versienummer 1.4.230
Releasestatus Final
Besturingssystemen Windows 7, Android, Linux, macOS, iOS, Windows 8, Windows 10, Windows 11
Website Mumble
Bestandsgrootte 31,10MB
Licentietype GPL

Door Bart van Klaveren

Downloads en Best Buy Guide

17-01-2022 • 12:39

10 Linkedin

Submitter: Ronnie N

Bron: Mumble


01-'22 Mumble 1.4.230 10
02-'21 Mumble 1.3.4 4
10-'20 Mumble 1.3.3 20
09-'19 Mumble 1.3.0 1
02-'17 Mumble 1.2.19 2
01-'17 Mumble 1.2.18 18
09-'16 Mumble 1.2.17 0
05-'16 Mumble 1.2.16 6
01-'16 Mumble 1.2.13 19
12-'15 Mumble 1.2.11 2
Meer historie

Reacties (10)

Wijzig sortering
Uit de beschrijving is het mij pas in 2e instantie duidelijk dat dit stuk software een eigen omgeving nodig heeft. Of is dit ook een stuk software dat richting voip-telefonie gebruikt kan worden? Dat ik de gegevens van mijn telefoon provider er in kan steken en dat ik het dan kan gebruiken om te bellen?
Nee je hebt nu een totaal verkeerde usecase voor ogen. Mumble is inderdaad self-hosted en werkt met kanalen waarin meerdere mensen met elkaar kunnen praten. Je zou dit kunnen gebruiken om een vergadering te hebben (zonder beeld) maar de software is oorspronkelijk bedoeld voor gebruik tijdens online multiplayer games. Vanwege de lage latency kan je daadwerkelijk je teamgenoten op tijd attenderen op veranderende situaties in spellen waarin je snel moet reageren, zoals shooters.
Die staan er al in, die nare dingen. Ze loggen alles en profilen er flink op los. (Oeps verkeerd geplaatst was voor @rbr320)

[Reactie gewijzigd door Jerie op 18 januari 2022 11:28]

Wat profilen ze dan precies? Ik lig namelijk alleen in, gebruik voice tijdens het gamen en ga weer. Ook weet ik niet met welke partij ze gelieerd zijn om mij iets te verkopen of mij gerichte advertenties te sturen.

Niet dat ik je niet geloof, integendeel, maar zou je iets concreter kunnen zijn?
Dat staat gewoon netjes in de EULA dat ze precies bijhouden wat je zegt, wanneer, welke devices je gebruikt, enz. Kortom, profiling/tracking.

Verder is de CEO degene die het bedrijf OpenFeint heeft opgezet, en dat bedrijf is niet controversieel. Dat was ook al spyware: https://www.courthousenew...-openfeint-sold-them-out/
Dus ze nemen alle audio op of transcriben het? Dat is inderdaad wel zorgelijk...
Iedereen die ik ken is allang overgestapt op discord, persoonlijk mis ik wil de minimalistische doeltreffende functies van dit programma. Echter kan ik niemand overtuigen om het te blijven gebruiken.
Idem, helaas lopen veel mensen weg met de social media features van Discord. Zodra zij nare dingen in hun gebruikersovereenkomst gaan zetten ga ik zo weer terug naar Mumble.
Onze go-to gamer Voice Chat. In ons vriendengroepje draait een lokaal gehoste Mumble server op een Raspberry Pi. De voornaamste redenen dat we Mumble gebruiken is de lage latency, de goede instelbaarheid van de microfoon, en de Open Source vrijheid om het te gebruiken waar en hoe we willen.
Mooi stukje opensource software! Voor gamen gebruiken het groepje mensen waar ik wekelijks mee game ook nu al een aantal jaar Mumble, daarvoor TeamSpeak. Het werkt verder wel prima maar voor mijn geval is de geluid kwaliteit van TeamSpeak beter, maar om de de meerderheid over naar Mumble wou hebben we toen TeamSpeak vervangen door Mumble.

[Reactie gewijzigd door Hydranet op 17 januari 2022 14:22]

Op dit item kan niet meer gereageerd worden.

Tweakers maakt gebruik van cookies

Tweakers plaatst functionele en analytische cookies voor het functioneren van de website en het verbeteren van de website-ervaring. Deze cookies zijn noodzakelijk. Om op Tweakers relevantere advertenties te tonen en om ingesloten content van derden te tonen (bijvoorbeeld video's), vragen we je toestemming. Via ingesloten content kunnen derde partijen diensten leveren en verbeteren, bezoekersstatistieken bijhouden, gepersonaliseerde content tonen, gerichte advertenties tonen en gebruikersprofielen opbouwen. Hiervoor worden apparaatgegevens, IP-adres, geolocatie en surfgedrag vastgelegd.

Meer informatie vind je in ons cookiebeleid.


Toestemming beheren

Hieronder kun je per doeleinde of partij toestemming geven of intrekken. Meer informatie vind je in ons cookiebeleid.

Functioneel en analytisch

Deze cookies zijn noodzakelijk voor het functioneren van de website en het verbeteren van de website-ervaring. Klik op het informatie-icoon voor meer informatie. Meer details


    Relevantere advertenties

    Dit beperkt het aantal keer dat dezelfde advertentie getoond wordt (frequency capping) en maakt het mogelijk om binnen Tweakers contextuele advertenties te tonen op basis van pagina's die je hebt bezocht. Meer details

    Tweakers genereert een willekeurige unieke code als identifier. Deze data wordt niet gedeeld met adverteerders of andere derde partijen en je kunt niet buiten Tweakers gevolgd worden. Indien je bent ingelogd, wordt deze identifier gekoppeld aan je account. Indien je niet bent ingelogd, wordt deze identifier gekoppeld aan je sessie die maximaal 4 maanden actief blijft. Je kunt deze toestemming te allen tijde intrekken.

    Ingesloten content van derden

    Deze cookies kunnen door derde partijen geplaatst worden via ingesloten content. Klik op het informatie-icoon voor meer informatie over de verwerkingsdoeleinden. Meer details