You can get the fixed Mumble 1.2.3a stable installer from:
http://sourceforge.net/projects/mumble/files/Mumble/1.2.3a/mumble-1.2.3a.msi/download (uninstall 1.2.3 stable first).
An updated installer for the snapshot version is available from: http://mumble.info/snapshot/mumble-1.2.3-271-gca8b25c.msi
You can also download a fixed Mumble.exe for the 1.2.3 stable from: http://sourceforge.net/projects/mumble/files/Mumble/1.2.3a/mumble-1.2.3-resigned-binary.zip/download

We are sorry for the inconvenience this may cause. We will follow up with a more detailed explanation later.

Regards,
The Mumble team

We recommend all snapshot users to update to the new version by manually triggering an update check via “Help->Check for Update”.

Sorry for the inconvenience.

No data was lost in this incident (yes we would have had backups ) and we are fully operational again.

Thank you for your patience.

Your Mumble team

ps: Thanks to our helpful remote hands.
pps: See our original announcement below.

Original announcement:

Blog and mumble public server list down

As you might have noticed the mumble public server list is currently unavailable. Around 16:00 CET this saturday the box serving mumble.info, this includes our blog and the public server list, became unresponsive. Remote diagnostics reports a dual disc failure as well as an backup battery failure in the servers raid-5. Efforts to try to remotely recover the server showed that the drives themselves are probably intact while the server itself is unstable at hardware level.

At this point we believe we will have to rely on remote hands to recover the data and to repair or even replace the server. Unfortunately our read-only cache we usually could fail over to is currently not available either.

So what does this mean? It will probably take us some time to get our services back online. Until this time neither our blog nor the public server list will be available. We apologize for any inconvenience this may cause.

Your Mumble team

• Windows Client + Server
• MacOSX Client + Server
• Linux Server binaries
• Source release (.tar.gz)

All of those can also be found on our homepage. We also have Ubuntu https://launchpad.net/~slicer/+archive/ppa

Special thanks to our community for their contributions to code, documentation, support and testing as well as the many great ideas they have come up with.

Your,
Mumble Team

Since we had some minor code changes since the last RC we want to give the code a few more days to cool down and we plan to release Mumble 1.2.3 stable the upcoming weekend.

We hope you’ll enjoy our new release. Snapshots/RC users will receive auto updates to stable. Mumble 1.2.2 stable users will see the usual update notification. Of course there will also be another blog entry

Regards,
The Mumble Team

As always the download can be found on our webpage at http://mumble.info.

If you want to know what exactly was changed since the last RC you can find our commitlog here.

Thanks to all the people that tested RC1 and reported bugs. Without you quite a few release critical bugs would have slipped through. Kudos to you all.

The Mumble 1.2.3 RC download can be found on our homepage at http://mumble.info.
To find out what is new in this release visit the upcoming releases page on our wiki.

Regards,
The Mumble team

As you might have realised it has been quite some time since 1.2.2 was released and we are eager to take the next step: 1.2.3 stable.

Unfortunately there is one tricky thing about stable releases: They should be stable With now more than 190.000 users using 1.2.2 we cannot risk pushing something out there that breaks what used to work or behaves erratically in other obvious ways. This is why we need YOUR HELP.

In our quest to exterminate each and every bug in Mumble, a quest at least as futile as honorable in software development, we rely on bugreports from you. If you want a quick and stable 1.2.3 release, then get one of our snapshots and test it. If you find a bug please visit our bugtracker and, unless there already is one, create a ticket. Please remember that for us to be able to fix the bug we will need as much information on it as possible.

Thanks,
The Mumble Team

The usual method for freezing strings is to export them all to a webpage, load that webpage into Word and use the spelling and grammar checker. This catches the worst mistakes, and there always are quite a few. However, it does not catch nuances of language, and it certainly doesn’t catch wrong information.

As I was looking through the strings for this release, I notice that the tooltip for the bitrate in the audiostats mention that you can adjust the bitrate by changing complexity in the audio settings. We replaced the complexity slider with a direct bitrate slider before 1.2.0, so that text has been wrong for quite a few releases. Thankfully, it appears nobody has noticed.

Translations are one of the last hurdles before 1.2.3 ships, and since translations can’t start until strings are frozen, we need a bit of help. The dev team wrote these strings, and we’ve seen them so many times we aren’t really reading them anymore. It’s therefore hard for us to spot mistakes and errors.

So, if you find any spelling, grammar or textual logic errors in the current snapshot, or in the exported strings, please let us know

UPDATE: Strings are frozen now. Thanks for your help.

Mumble-Django channel viewer

Mumble provides a pretty neat online experience to its users as it is – still, people often look for some kind of an interface to query the server for status information over the web. The most common use for such an interface is an embedded channel viewer on a team’s web site, but it could be used for monitoring or other kinds of status notifications as well – the limit being your imagination.

If you take a look at the 3rd party applications Wiki page, you will see that quite a few apps around Mumble have emerged recently, and probably a lot more are currently in development. This is great, as it makes the Mumble ecosystem a lot more vivid. The downside is that if you want to use these applications, you will soon run into problems if each application uses its own protocol to expose information, because using this method will require the server side component and the channel viewer application to match.

Needing to install a specific server-side component for each individual app would cause a lot of unneccessary work for both installation and maintenance, so being able to use a single server-side component for all apps would be preferable – especially if your favorite web interface already implemented the server side component.

From a client’s perspective, being able to use your favorite app with a certain server would require the server admin to configure an interface for the client to use. Being able to simply use an existing interface would mean a lot less work, especially since web interface applications usually provide the server side for all servers that they manage.

The ultimate goal is that each channel viewer is compatible with each server side implementation, no matter which one the respective administrators choose to install, while still being easily maintainable for each server admin.

However, this can only be achieved when the components use the same data format, because otherwise they simply would not understand each other. To achieve this, the Channel Viewer Protocol has been agreed upon. If you want to create a new web application, you are highly encouraged to use the JSON or XML data format defined in the Protocol.

The Channel Viewer Protocol is aimed to be extendable, lightweight and easy to implement on both the server and client side. By using it, you will enable your users to freely choose which applications they prefer to use, and thereby support the idea of software freedom, because giving the user a choice is what this is all about.

If you have any proposals for the standard, please feel free to visit the #mumble channel on IRC or post in the forums.

—

Note by staff: Svedrin, the author of this article, is a Mumble community member and developer of the 3rd party Web-Interface Mumble-Django. We thank him very much for contributing this article. We would love to be able to publish articles written by our community on a regular basis, so if you have an idea you think is worth getting into this blog, please contact us.