Jump to content
Mumble forums


  • Content Count

  • Joined

  • Last visited

Personal Information

  1. Channel switching is so automated that EVERYBODY is automagically switched into the proper channel upon entry into any of our three missions according to either of their two teams within either of our two realms, so (under normal circumstances) nobody even has to think about it. Accordingly, that video clip doesn't show any channel changing. However, click below for a YouTube video clip that we use to train our advanced users, illustrating very advanced management of Mumble. We can "promote" individual players who can then take command of all of the Mumble clients for their entire team, sw
  2. I just LOVE Mumble! I've had great success integrating it into the "cockpit" of my free, open-source combat flight simulator and it behaves very much like an aircraft radio. My sim is written in "c++", and I used the well-known "popen()" function to activate Mumble's standard (but little-known) "Mumble URL" facility to command my local copy of Mumble V1.3.0 to connect with my Mumble Server and then to enter the appropriate channel from among about 30 channels that are dedicated to various teams and missions during online combat. The result is fantastic. THANKS for MUMBLE! Your generosit
  3. Thank you very much kissaki. Your explanation helped me figure out a process that now has everything working reliably. I had misunderstood the role of the murmurd server in this situation. Some of my old mumble clients are evidently misbehaving in the way they participate in the CODEC reporting and negotiation process. (The misbehaving old mumble Mumble 1.2.3 clients are all running on PcLinuxOs, which is a distant, very conservative derivative of Debian LINUX. Although it is problematic because it only supports the ancient 1.2.3 version of Mumble, PcLinuxOs has other redeeming and compelli
  4. I am using murmurd version "1.2.12-lubuntu" to handle all different kinds of Mumble clients. Most of my users now have Mumble V1.3.0 clients, but there are still a lot of them using old Mumble V1.2.3, and I also have several using Android's "Plumble" client. At least one other person uses some kind of Mumble client on an iPhone under IOS. Because some of these diverse Mumble clients (notably the old V1.2.3 ones on Linux) are incompatible with the newer "Opus" CODEC, I never want the murmurd server to force use of the "Opus" codec. In fact, I am assuming (and hoping) that when murmurd receiv
  5. bbosen

    Overlay On Linux

    Yes. Users of Linux Air Combat and old Mumble Version 1.2.3 have done this with good success and it is covered as our FAQ #24. I am appending that text below. (I do not know if this works with new Mumble V1.3.0 on Linux.) As you read this example for Linux Air Combat, replace references to "LAC" or "Lac07p59" with the name of the Linux game you are using. ========================================================= FAQ24: Can I use Mumble's well-known "Overlay" with LAC? A: Yes. However, experience with this Mumble "Overlay" reveals that it slows LAC down a bit. Typically, we see a 10% r
  6. Update: I HAVE NOW figured out how to make Mumble URLs work properly with every version of desktop Mumble since 1.2.3. Now none of my users need configure any of the problematic, channel-changing "shortcuts" any more. Everybody in my little "Linux Air Combat" community is a lot happier now.
  7. I have no control over the choices my users make regarding use of Mumble. Some of them are using current versions and some are using old versions. A lot of them are using "Plumble" on Android. Fortunately, even the old desktop Mumble V1.2.3 supports Mumble URLs in a manner that has enabled me to interface with it. I had to do some adapting (as described in prior memos of this thread) to Linux Air Combat to control every version of Mumble from old V1.2.3 up thru the current 1.3.0, but that effort has now been successful. As a result, anybody that installs any version of Mumble since old V
  8. [12 hours later] Well, I found a bizarre way to make progress. If I insert a command attempting to connect with a non-existent mumble server, specifying a non-existent username and non-existent password BETWEEN commands to my real mumble server, it works better. That non-existent server connection attempt forces a disconnection with my own, real mumble server. The sequence is like this: mumble mumble://LinuxAirCombat.com/001/?version=1.2.0 & works as expected, connecting me to my channel "001". mumble mumble://nobody:nobody@ & Forces a disconnec
  9. To clarify, here is what I am doing. First, on my Linux machine equipped with Mumble V1.2.3, I issue this command line into a bash shell: mumble mumble://LinuxAirCombat.com/001/?version=1.2.0 & That works. I get connected to my Mumble server at LinuxAirCombat.com and I also get switched to the "001' channel, exactly as expected. Immediately after that, I issue these commands in an attempt to switch into channels "002", "003", and "004", respectively: mumble mumble://LinuxAirCombat.com/002/?version=1.2.0 & mumble mumble://LinuxAirCombat.com/003/?version=1.2.0
  10. [2 days later....] I discovered my error in the prior posting: I had neglected to insert a colon character between "mumble" and "//". Having fixed that, I am now experiencing progress with Mumble URLs and Mumble V1.2.3. It still isn't behaving as nicely as Mumble V1.3.0, but I can get it to connect to my server and go to a designated channel. Here is a sample of the command line I am issuing into a LINUX bash shell to get that far: mumble mumble://LinuxAirCombat/com/001/?version=1.2.0 & I can expand that command line to reference any of the channels offered by my Mumble Ser
  11. After a few weeks of experience with a more current, more advanced version of Mumble (Version 1.3 ) I must report that loss of keybindings still happens a lot under LINUX. It's discouraging. I urge my user community to configure 26 Mumble Shortcuts to optimize its use with my "Linux Air Combat" flight simulator, which results in a very nice Mumble interface. Those users that follow my advice report that it works very well, but within a few days they generally lose all of those shortcuts. Sometimes they try again, but the problem repeats and pretty soon they abandon those efforts. The good n
  12. Well maybe I can express my situation more clearly. I have Mumble URLs working correctly with Mumble V1.3.0. and I'm VERY HAPPY with the results. Many of my users, however, are using old Mumble V1.2.3 and it's clear that the interpretation of Mumble URLs is different for them. I have discovered how to format a Mumble URL for V1.2.3 that will cause them to connect with my Mumble Server, but I have not figured out how to specify a desired channel. For example, my Mumble server is at LinuxAirCombat.com, and I can get my LINUX-based Mumble V1.2.3 to connect with that server if I issue thi
  13. Thanks. It synchronized somehow. Now I see my edits on the wiki page here: https://wiki.mumble.info/wiki/ACL_and_Groups/English : )
  14. I just discovered Mumble URLs and I am using them with success on Mumble V1.3.0 with Manjaro Linux. Here is the "c" source code that I use to connect to the "root" channel of my Mumble server at LinuxAirCombat.com: popen ("mumble mumble://linuxaircombat.com/LinuxAirCombat?title=Root&version=1.2.0", "r") Cool, huh? Yes, it really is a ONE-LINER! If I want to go deeper into my channel hierarchy, I just expand that line a bit like this: [popen ("mumble mumble://linuxaircombat.com/LinuxAirCombat/Realm0/MissionNetworkBattle01/M1Red?title=Root&version=1.2.0"", "r"); That comma
  15. Something is wrong. It's been about 3 days now and I still cannot see my edits on the public-facing page, but I DO see my edits on the editor page as you describe. The cache logic must have failed. -bbosen-
  • Create New...