Jump to content
Mumble forums


  • Posts

  • Joined

  • Last visited

Everything posted by Krzmbrzl

  1. Okay then you can either create your own plugin that implements an arbitrary interfacing to your game or you can use the Mumble JSON bridge (see links above) and call the corresponding CLI from your game to pass down instructions via JSON. Note however that The current API does not yet support all of what you need. For instance creating a channel or joining/leaving a specific server is not yet possible. If you are interested we could make that work though. It shouldn't be too hard to add that In order for the plugin-approach to work the official Mumble client has to be running. This will most likely involve users having to start it manually. It would also mean that there is a GUI the user could interact with as there currently is no headless mode.
  2. Could you elaborate a bit more on what you have in mind specifically? Something like this would probably be what you needed for what you have in mind, but that particular project has never been completed and is now completely unmaintained. Thus this is not really usable at all. Unfortunately though there currently is not replacement. We are aiming to provide a library-like version of the Mumble client but as of now that does not work. Depending on what you need exactly though, you could either link to the "Link" plugin of Mumble (https://wiki.mumble.info/wiki/Link) or if you require more control and/or interaction with Mumble there is also a brand new general purpose plugin framework that got merged into Mumble master just recently. This will be part of the upcoming Mumble 1.4.0. As it stands there is no documentation on this yet, but you can either ask me (I am the author of that framework), have a look at https://github.com/mumble-voip/mumble/pull/3743 (though the changes in there are probably a bit too excessive), https://github.com/mumble-voip/mumble-plugin-cpp (if your game is written in C++) in combination with https://github.com/mumble-voip/mumble-json-bridge/tree/master/plugin, or if you want to see how a bare-bones plugin looks like that is using the raw C API, have a look at https://github.com/mumble-voip/mumble/tree/master/plugins/testPlugin.
  3. If you rephrase your question, turn down the font to a reasonable size and actually describe what is happening and why that is a problem then maybe we can help. Otherwise: No
  4. First of all: Don't cross-post here on the forums. This is the kind of action that makes me not want to help you at all. *Thread closed*
  5. FWIW we have received another report about this and there it turns out that the "minimum volume" setting was the issue. It currently defaults to 80% which seems to be barely audible. If you don't want to hear distant players at all, turn this down to 0%.
  6. @MilkMadeforFolding what you can do in order to troubleshoot this, is grab a friend and use the "Manual plugin" in Mumble instead. Select that plugin in the Plugins menu and click the Configure button. That brings up a new dialog in which you can manually specify your position. Note that you have to manually enter a context as well (which has to be the same for your friend) and then check the "Link" checkbox. After both of you have seen the message about the manual plugin having linked in the chatbar, experiment with the position and how that affects audio. With that you should be able to explore the full proximity chat options that exist and with that you should experience fading volume with increasing distance.
  7. In general you will get better help if you join the linked Discord for the Lunar Client and create a ticket on there. This is because this is almost certainly an issue on the Lunar Client side and not on the Mumble side.
  8. I just spoke with a Lunar Client developer and was told that the issue you are describing should have been fixed with an update about a month ago (see https://www.lunarclient.com/patch-notes/03-21-21/). Did you verify that you are using the latest version of Lunar client? EDIT: In order to make sure: Please make a screenshot of the commit-ID in the main menu and upload it here.
  9. Ah okay. In that case I think you'll have to report the issue to them. Given that you are able to hear the direction of other players, the transmission of positional data and its processing in the audio backend seems to work. My suspicion is that the Lunar client does not set/send the distance of different players for some reason. EDIT: I also joined their Discord and will try to figure out what's going on. But you should still report your problem yourself in order to receive proper support from the folks that actually know how their client works ^^
  10. Should be possible, yes. The -supw option is available on all OS.
  11. What "Lunar client"? Is this Minecraft related?
  12. Okay so this means that the plugin is able to link to the game and extract at least some information out of it. A few questions regarding this: Where did you get a Minecraft plugin for Mumble from? Afaik Mumble does not ship with one by default. Aka: What did you download from where and where did you put that in order to install it? Have you double-checked that you are running the same version of the plugin as your friends? Are you all using the exact same version of Minecraft (exact same patch-level)?
  13. Following up on this topic: There is now a fully-fledged plugin system coming with 1.4.0. See https://github.com/mumble-voip/mumble/pull/3743 for its implementation and its status.
  14. I assume you imported your certificate into the client? If you can't connect to your server anymore, then I assume the import has failed. Have you tried doing that again?
  15. Krzmbrzl


    Receiving and playing stereo streams is supported in 1.4.0. Stereo input might also find its way into Mumble (some people are actively planning on tackling this in the foreseeable future) but as of now it's not supported.
  16. Communication between the plugin and Mumble is easy. The plugin is presented with an API that it can use and it can also include callbacks that Mumble will call as appropriate. How you are going to talk with the plugin is completely up to you. You could either use shared memory, (named) pipes, sockets, ... The keyword you are looking for in this context is inter-process communication (IPC): https://en.wikipedia.org/wiki/Inter-process_communication
  17. That's still on my ToDo list. For now you can either place the DLLs in the proper directory manually (not recommended) or start Mumble from a command-line, providing the path to the DLL as the last argument. So for instance mumble.exe path/to/the/plugin.dll That should open the plugin installer that will install the plugin for you. After that, you will find an entry for it in Settings -> Plugins where you have to enable it.
  18. As of now the documentation lives in the source file of the original C headers in my fork: https://github.com/Krzmbrzl/mumble/blob/plugin-API/plugins/MumbleAPI_v_1_0_x.h and https://github.com/Krzmbrzl/mumble/blob/plugin-API/plugins/MumblePlugin_v_1_0_x.h. If you are using C++, then I recommend using https://github.com/mumble-voip/mumble-plugin-cpp instead of the plain C headers. If you are looking for a sample implementation you can have a look at https://github.com/Krzmbrzl/mumble/blob/plugin-API/plugins/testPlugin/testPlugin.cpp for the plain C interface. Note however that you have to build from my fork (from the linked pull request) as the plugin framework did not yet find its way into the main repo. As such it is also not guaranteed to remain unchanged yet. Thus if you want to test it out early, you might have to adapt a thing or two that might get changed in the meantime. As a further alternative I can also point you to PyMumble: https://github.com/azlux/pymumble This is a Python standalone implementation of parts of the Mumble protocol. You could either reimplement the relevant parts into your game or find a way to use the Python library directly...
  19. This sounds like that person that you are hearing normally does not have the positional audio feature enabled in their client. Did you double-check that?
  20. This line looks suspicious to me. I am not an expert in the shortcut system though. @davidebeatrici do you have an idea where the problem might be?
  21. Yes exactly. It defnitely is out of date and I am not even sure if it ever reached a working state.
  22. Are you or your conversation partner using noise suppression (RNNoise in particular) and/or echo cancellation? If so: Have you tried disabling either or both to see if the issue persists?
  23. This is an english forum, so please post your question in english.
  24. What is it now: Is the problem that shortcuts don't work in general or is it that only PTT does not work? It can't be both... Could you give me the output of Mumble's Developer console, please? (https://github.com/Krzmbrzl/mumble/blob/docs-developer-console/docs/DeveloperConsole.md)
  25. Does Mumble react to other shortcuts that you have set up or is this a problem specific to PTT? Well the shortcuts in TS have nothing to do with the ones in Mumble...
  • Create New...