bbosen Posted August 28, 2019 Share Posted August 28, 2019 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 commands my local copy of Mumble V1.3.0 to connect with my murmur server at LinuxAirCombat.com, immediately accessing the channel I created there thru the path "LinuxAirCombat/Realm0/MissionNetworkBattle01/M1Red".Note, however, that those working Mumble URLs (retrieved from a working Mumble app by right-clicking on the associated channel) do NOT look like those documented in the Mumble Wiki here:https://wiki.mumble.info/wiki/Mumble_URLThis inspires a question about some funny behavior I observed when I tried to use my Mumble URLs with an older version of Mumble (V1.2.3). The same Mumble URLs that work well with new Mumble 1.3.0 automagically invoke ancient Mumble version 1.1.x instead of version 1.2.3 which I routinely use on that system. I am guessing this results from some old attempt at backward compatibility???If I try formatting those Mumble URLs as documented in the wiki (instead of the format given to me when I right-click on the newer V1.3.0 client), can I expect them to work better with users still tied to Mumble V1.2.3?Thanks!-bbosen- Link to comment Share on other sites More sharing options...
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now