Jump to content
Mumble forums


  • Posts

  • Joined

  • Last visited

1 Follower

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

mkrautz's Achievements


Newbie (1/14)

  1. Did you try the suggestion of copying your Mumble install to your desktop, and running it from there? That was the main point.
  2. Hi, Thanks for your kind words about Mumble. Greatly appreciated! There's a long running thread on GitHub about this problem. I have been able to use a virtual F13 key using AutoHotKey: https://github.com/mumble-voip/mumble/issues/987#issuecomment-260461709 Could you try the approach at the bottom of my post (copying Mumble to the desktop, and running it from there?). Mumble, by default, on Windows runs in a special mode for assistive technologies, so Mumble can intercept keypresses from some elevated programs. We do this to avoid keys getting "stuck". Please report back with your findings. Thanks!
  3. I am still confused regarding the last bullet point. Are you asking the Mumble project for improved documentation on how to change the client's default settings, to easier allow you to configure the client for connecting to your HN? Or something else? I need to know more about your setup to say anything intelligent. :-) Mumble supports HTTP(S) and SOCKS5 proxies. Are you using those? Or are you using a standalone client?
  4. I've implemented this in https://github.com/mumble-voip/mumble/pull/3118
  5. Hmm, not at the moment. But it's something we could implement...
  6. Hi, We provide RPC APIs to allow you to get to the necessary data for your Murmur server. I am not aware of any "plug-and-play" solution for SMF, unfortunately.
  7. Hi, The problem is that Mumble 1.2.x in Linux distros is built against a stock Qt 4. Our official binaries (as well as some operating systems, such as OpenBSD) use a patch for Qt 4 that allows it to use TLS 1.2. No Linux distros have picked up this patch, to my knowledge. But as I said, our official 1.2.x binaries all carry the ability to negotiate TLS 1.2. If you can get a "mumble-git" or "mumble-snapshot" version for your distro, you should also be good to go, since this version is built against Qt 5, which supports TLS 1.2. Unfortunately, we only provide our static Murmur Linux binaries for x86 at present, so I don't think that's much help for you, on ARM.
  8. I think what happened is that you deleted your original certificate, and you are trying to connect with the username you used previously. If you've created a new certificate, try to choose a different username, and you should be able to connect again. Then you can re-register, and an admin can change your name, if needed.
  9. Sorry for the late response. Could you prehaps show us the output of Mumble's log when this doesn't work, and also when it does work? I'm interested in what parameters Mumble is using for the audio devices. Thanks. Your log file is available at %APPDATA%\Mumble\Console.txt
  10. I haven't tested EVE on Mac recently. I've filed this issue for the problem: https://github.com/mumble-voip/mumble/issues/3117
  11. Also filed https://github.com/mumble-voip/mumble/issues/2667
  12. This issue seems to pop up a lot. Mumble doesn't respect the chosen output device for Text-to-Speech: we simply use Microsoft's Text-to-Speech API, and whatever default output device it uses. I've filed this issue for the problem: https://github.com/mumble-voip/mumble/issues/3116
  13. Yes. Yes, but if it is a modified client, we'd prefer it if you make it clear that it's not official software from the Mumble project. What changes have you made to the software? Sure, we do all our development on our GitHub organization: https://github.com/mumble-voip What changes have you made to the client, if any, at present? How do you imagine the VPN connection would be integrated into Mumble? I'm not sure why you think it is necessary to integrate into Mumble itself, but I'm interested in hearing your thoughts. Thanks, Mikkel
  14. Development snapshots are available thorugh our website: http://www.mumble.info/
  15. Our implementation only worked on Qt 4. What we did was, we made use of our existing overlay. Then we leveraged our GlobalShortcut implementation (including the ability to suppress events). This allowed us to grab mouse coordinates, clicks, etc. -- and ensure they weren't delivered to any other app on the system. Our code is old and unmaintained, and I doubt it works well anymore. However, our implementation mirrored the "Windows platform" windows from Mumble into overlay. That was the most hacky part of it. If you instead use a custom platform plugin in Qt, or you simply draw your widgets yourself, it should be much more doable. Unfortunately, our overlay code isn't really its own project, so it's not easy to integrate into something else.
  • Create New...