![]() Whenever we notice that voice chat latency increases, we can just switch the server we’ve got set up, and it’s easy to do so. My conclusion? It is a nice alternative to Discord, for a small price. We do see quite a few context switches though, so quality network cards and infrastructure capable of handling high packet load are recommended on servers hosting a big number of clients. Since only minimal processing, as required for cryptography and “visibility checks” between users, is done serverside, we were not able to push even 1% of actual CPU usage with 4 users on a Xeon 3.4Ghz. So if there are 10 other users on the server with you, your incoming bandwidth requirement will be 100-400 kbit/s if they all talk at the same time.īased on data from out testserver, murmur will use about 40 MB of virtual memory, of which about 4 MB are resident in physical memory. Mumble will use 10-40 kbit/s outgoing, and the same incoming for each user. It’s quite astonishing how cheap it is to run this in terms of resources. There’s also a very welcome dark UI option.) (You can now tune how loud every participant sounds, for example. The latest client is currently a release candidate at the time of writing and a serious improvement over the previous version of the client. The most annoying bit is that it requires a little bit more set-up initially (client-side) before you can actually connect, but it’s quite easy to use once you’ve got it set up correctly. It uses your server and encryption, so your privacy is guaranteed (provided you trust the machine you install this on).More granular control over busy voice channels (support for sub-channels, for example).Higher audio quality for those participating in the conversation (up to 128 kbps, Opus codec).Lower latency (roughly 20 ms to our server in Amsterdam, instead of 40-80 ms average on Discord which sometimes spikes to 100+ ms, although your mileage may vary).Using Mumble actually has various advantages over Discord, namely: (It’s open source after all, so that’s great!)Īll I needed to do was install a package on an existing VPS, edit the configuration file to set up a passphrase, and allow a port through the firewall of my server, and I was done. ![]() ![]() In order to keep interruptions to a minimum, I decided to set up a Mumble server (using Murmur) after reading a bunch of positive things about the software on Hacker News. And we use Discord a lot to talk to friends. Lately, though, we’ve found that the connection to Discord’s voice servers (regardless of server region) has been a little bit less reliable than it used to be. In the past, we’ve been using Discord for all of our VoIP needs ever since it became a viable alternative to Skype. A little bothersome, but not too annoying. Later, we’d merge the audio of both ends. Me on my end, my friend on the other end. In order to have a record of the conversations we have, we’ve been recording those sessions locally. Mumble uses a client-server architecture which allows users to talk to each other when connected to the same server. For a side project a friend and me have been working on, we’ve been using Discord whenever we needed to talk.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |