Why use mumble

No additional steps necessary. Murmur should be run from the command line, so start a shell command prompt and go to wherever you installed Mumble. Run murmur as. Example --pull s each time to check for updated base image, then downloads and builds master branch. The OpenGL overlay works by intercepting the call to switch buffers, and just before the buffer switch, we draw our nice GUI. If you have Mumble installed through the binary packages, this can be done by simply typing:.

Skip to content. Star 4. View license. Branches Tags. Could not load branches. Could not load tags. Latest commit. Git stats 9, commits. Failed to load latest commit information. CI: Update to latest vcpkg environment. Jul 27, Jun 15, Add transifex client configuration for project. Apr 27, Mar 28, Aug 10, Jul 8, DOCS: Add common build errors.

Sep 23, Apr 9, Mumble requires a connection to a server to function. Servers can be rented from commercial hosting companies. The Mumble server software is also available free-of-charge under and open source license, so individuals are free to create their own servers, without limitations. Mumble is open source software, developed collaboratively on the Internet. Mumble and its server software are available for free, for anyone to use. This app has been updated by Apple to display the Apple Watch app icon.

Hi there, over all, I would say that Mumble works great. I run an online radio station, and would like to see some improvements made, such as an even higher bitrate such as 96 or kbps audio, plus easier use with an audio interface. As of now, if I launch Mumble with the interface connected, it is not recognized. I have to launch mumble and then plug in the interface for audio to be able to output.

With input there is no problem, but it will not output to the interface unless I follow the procedure I just described. By default Mumble is not started with root privileges.

More on that in a moment. By default your server is accessible to anyone who knows the IP address of the server. More on that below. In order to access your server from outside of your local network, you have to forward Mumble port on your router. Check out this tutorial on port forwarding to see how. In order to connect to your server, you need a client application which will enable the connection.

Navigate to mumble. After the installation, open the client. On desktop you will have to configure the program. Follow any on-screen prompts to setup your sound system. As this part is dependent on your system, I will not provide a guide for it. You will also be prompted to create a certificate. This is a user certificate. It is used to authenticate the user, not the server. Every user has its own certificate. Not just maintain, probably grow market share significantly now that they're adding it as a built-in app in Windows On mumble this is instantaneous.

LinuxBender 4 months ago prev next [—]. Should Discord some day be purchased by one of the big players, I would expect them to follow the path of Zoom and add voice transcription thus allowing them to not only save text chats forever, but also save everything that everyone says.

Their user-base are already asking for it [1] One would have more control over this on a Murmur Mumble server. In my experience, people are more relaxed with things they say vs.

There is the assumption that only the people visible in the channel are listening. It is only a matter of time before voice transcription is standard on all the large platforms and I am not confident that this data will be protected properly.

Some of it is probably already transcribed too. It's just that doing it for every possible accent and language is not easy without training, so they probably don't have everything transcribed, but some of it probably is and the rest is just waiting in archives for when they want to give it more attention. I'd like to point out that Mumble is one of those rare solutions that works just fine on the Tor network, for everyone's privacy. Why would it be normal for a voice server to know where you reside in order to take part in a discussion?

It'd be nice if it just had a "Connect through TOR" checkbox in its preferences, but I have a feeling it's not even remotely so easy, is it? It's not so easy no, but it's not so hard either. I believe it's as straightforward as that, but to be honest i haven't fired up a network log to check that Mumble wasn't sending IP addresses or other "private" information over there.

The average person's not going to know or even want to know how to do that. It needs to be made as simple as a "connect over tor" button, and everything should be done for you, including setting up tor Not that i disagree with your point, but that's not exactly part of tor's threat model that it would be setup by a random application trying to leverage it.

Usually, you set it up once on your system then apps access it. Auto-setup may be easier if you're targeting a certain platforms, for example on Android you can keep a local copy of the F-Droid PGP key, download the latest installer, set it up, and from there enable Guardian Project repository and setup Orbot tor for Android. On Debian, you could just run "apt install tor" acquiring privileges on the go from your program and then start proxying through localhost But if you're targeting many systems the problem becomes hairier.

If you have better suggestions about how to ease this process, i'm sure folks from the Tor community will be very interested! Edit: Ok, that doesn't work. You're right, there should be a Tor button in Mumble. Great software, poor UX. I have difficulty getting people to use it over zoom or discord.

Poor UX seems to be a recurring theme with open source projects. Anyone knows why? Here is how it goes: - you slap together a low effort UI in order to test your code. Also as it was quick-and-dirty stuff it would also be very difficult for others to redo the UI. So you have to make a low-effort UI to test and demo your library. Apart from all issues mentioned so far all valid edit: utunga got there while I was still writing , there's also a problem where you can't apply good UX in small patches here and there.

You can fix some terrible experience where it's actually a problem, but to really improve UX in an app, you need to touch almost everything at the same time, which means a lot of time spent on the task and required commitment to the idea from the leaders. That's really hard to organise in opensource world. And when you try to introduce leadership which can do it and try to collect information, you get the issues Audacity ran into.

Sure, Tentacrul can lead the UX effort and will make Audacity much better, but the community impact was pretty negative. The only opensource project I really remember pulling off a well organised UX update is Blender. And even that was after years of people screaming "don't touch right-click-to-select, we're used to it and newbies need to learn". First develop the core functionality without a UI as a library or daemon or whatever.

The actual UI is then developed as a front-end to the library. This allows multiple front-ends to coexist so a new UI can be developed without disturbing the people that like the old version. Too many projects tightly couple their UI and mechanism, which always leads to problems. Interesting way to develop a program while keeping ui seperated, would have never thought of that approach.

But in my experience, developing the UI alongside also leads to insights into your product you hadn't foreseen.

Developing both the backend and an initial UI front end in parallel is a good idea. The point is to separate different aspects of the program into manageable, modular sections. Separating the mechanism and UI is just an another way to practice information hiding and modular programming. What happened with the Audacity community when Tantacrul started?

The telemetry was one thing, but there was also a few people with "what do you mean muse owns this project now? I'm forking rather than accepting forced leaders". Nextgrid 4 months ago root parent prev next [—]. I agree with your first point but I disagree that telemetry is required to improve UX. You can "collect information" in a respectful way by asking users instead of stalking them and letting a malicious third-party such as Google Analytics do so as well.

Quoting from a commenting on this thread: "The only thing that can confuse people is the certificate security system While not universal, OSS has a higher tendency to not-my-problem certain things. Often this is UX, other things too. Interoperability, multiple implementations, advanced features, user choice, etc. Stuff that proprietary software tends to be bad at.

The thing that drives facebook or Tinder to make their software addictive is the same thing that drives them to make it usable for the average person. And by the time anyone's developing for the project, they're already entirely familiar with all the quirks and UI decisions. It takes real top-down leadership or a one-man project to be able to change those things. He released V20 after so long and so much feature feedback from dedicated users in the Play Store beta channel.

Immediate community revolt from V19 users who just liked the UI the way it was and never new there was a beta program in the first place. Much subreddit infighting. Cooling off period. Some people were proper angry and he was in a tough spot. Anyhow its probably better material for a business school case study but point here is even a one man project can get caught by UI pattern bias. It's an important question that deserves a considered response.

IMHO its more than just lack of designers though that's important it's actually a balance of power thing. Delivering really good UX requires taking a design-led approach to the whole project. Unfortunately this conflicts with one of the main reasons coders enjoy working on open source. No management, no customers and you get to work on what you want. Design it for yourself, not others. But of course, the interface that the average coder wants is nothing like the interface that the average user needs - especially if the average coder is intimately familiar with all the features.

Most coders appreciate this and try to design a 'friendly' interface but at the end of the day it's a power imbalance. In a conflict between clean design or adding more features, a team led by programmers is going to prioritize features.

Just guessing: There's not a lot of designers in open-source circles. They tend to get paid a lot less than devs and so many don't get the privilege to care as much about FOSS. When I went to design school and tried to use Inkscape I was laughed at. The day-1 was basically here's a Mac, here's Adobe, now learn to play in this sandbox which I did til post college.

I would like to be involved, but I'm not really sure how. The open source culture and tooling is strictly all about code. At least, that's the way it feels to me.

Very unapproachable. And often times, there is zero signal that they would even be interested in getting the help. From my experience. For what it's worth, I'm a design lead and make six figures. I don't think that has much to do with anything. You could just create an issue for a project to discuss it, or bring it up wherever their community is. Hendrikto 4 months ago root parent prev next [—]. I do not follow this line of reasoning.

Why would your salary matter? Say you don't have a lot of cash and you want microblogging and VoIP. Do you spend money to host your own Mastodon and Mumble servers, or use one where many admins understandably require payment or donations to cover costs, or do you use the free-because-you're-the-product Twitter and Discord?

Do you use the centralizing, closed-source GitHub or pay for SourceHut or host your own Gitea server? Can you afford to build a rack at home to self-host and invest in the skill to maintain and secure it? Do you invest time in learning GIMP despite lower-quality, community tutorials because it's free as in beer and freedom or do you follow the crowd and use Creative Suite or Affinity Studio because it's the tool most your jobs will expect you to use?

I think it is unfortunately a privilege of being able to afford the FOSS and privacy-focused alternatives--through money and time. A good salary gives you room for privilege. I don't think you can separate finances from the equation. Many people are just out there trying to take the easiest route to survive, and FOSS isn't as easy.

Heck, even speaking English is a privilege many here on HN have. I've been in Thailand for a while now and while the much of the youth demographics resents its government, almost no one knows about decentralized, private, FOSS services because it hasn't been localized and people can't afford the bill either--and as such the government has many times censored Facebook and YouTube and other centralized systems.

Qwertious 4 months ago root parent next [—]. The ability to make tools stems from access to time. The freedom of time comes from having money. Someone else was subsidizing the overhead. It's a good article, I recommend it.

And you have to host your own server. It all just works and it costs a fortune to run. No one has enough free time to build a brand new high quality app for mumble which works on 3 desktop OSs and 2 mobile. QT because that requires a big download in addition to the program, and also 'doesn't feel native' or 'doesn't look right' or 'sets off the AV scanner'. Instead it just gobbles CPU cycles, memory, and is slow and horrid. I'm to the point that I don't care what wins, or how horrid writing for it is; I just need a widgets toolkit and bindings that can be developed for ONCE, is hosted with the OS and shared among all apps, and works on Mobile all of them , Win, OSX, and 'nix.

Electron is what Discord and Teams and Slack use. And Google's stuff just uses web pages. Qwertious 4 months ago root parent prev next [—]. I keep wondering if something like Godot could win out in GUI-land. It's the first time I hear of "sets off the AV scanner" being a major problem for native apps.

How frequent is it? I believe this happens because writing high quality UIs which is consistent, is well studied as in having studied how users react to it in order to improve the worst parts , and is available for multiple platforms, is a HUGE amount of work that would only go forward if people got paid to do it. So I'd wager that lots of OSS have bad UI because no commercial entity considered that the market is big enough to justify spending resources on it.

This is, an external company pouring money at hiring OSS devs to work on the UI, or maybe even the project creators themselves founding a one-person business to sell services or products that require such a good UI. An example: if Mumble had a huge user base, maybe there would possibly be some company selling high-quality, easy to use desktop applications for it. But reaching that goal is very hard, and most OSS projects never get even a fraction of the traction that would be needed for such commercial efforts.

Because not every free-software project has UX designers working on them? I mean the UI is the frosting on the cake, that you can do in pretty much any language and usually with less knowledge of the backend infrastructure Kudos to the Tor Project and Conversations.

The setup wizard expects one to setup microphone levels, I didn't even have the mic connected. And I have different setups connected at home and at work, which makes me doubt the agility of this configuration can it adapt to plugging in and removing equipment? I think of it like this: open source software is typically written by volunteers. Volunteers with good systems skills but no UX skills can author open source software on their own.

Oppositely, volunteers with no systems skills, only UX skills cannot. This is probably worsened by the fact that people who care about good UX will gravitate towards software with good UX, which is often commercial.

Whereby used to be excellent: No login no plugin. The great thing is that mumble is a free client with an open protocol, dofferent clients can coexist. To my knowledge this warrents a ban on Discord. This is all great when people make that a priority. Since this is a client server architecture wouldn't there be alternative clients? Bombthecat 4 months ago parent prev next [—]. There is video now? Well, those are just what my friends and peers generally use.

I frequently use zoom with cameras turned off. But boy do I wish they would. Such little barriers were a great initial filter for toxic wannabes with short attention span. And now with Teamspeak 5 it's just Matrix. And Matrix is a super heavy protocol. That's not the fault of the "heavy" protocol, but the implementation of it. Avi0n 4 months ago root parent prev next [—]. TS5 is matrix?

I use mumble with the plumble client when I'm taking the train or just walking at the park when we have voice only meetings at work. It is a very power and bandwidth efficient solution. I've always been a fan of Mumble and murmur server and its high quality, open source software. I still operate it today since there's still a few users out there. I realize most are using Discord now. I'm sure it's possible, but not too sure if there's still a sizable audience willing to use Mumble over Discord these days.

I used this back in in high school to chat with friends while playing Minecraft. I had a good experience with it then, can't speak for it now though. Lammy 4 months ago prev next [—]. I never did anything fancy with my server but I never noticed anything that umurmur didn't have, meanwhile it used virtually zero resources. Mumble has been one of the if not the best additions to FiveM[1] It has allowed for so many cool in game features, like the ability to have DSP audio filters on channels so we can do RadioFX audio effects in game without any external applications.

Quite popular in the EVE: Online community, where alliances and corps run mumble servers with tens of hundreds of people each.