Connection failure: Connection terminated When running Mic_Over_Mumble Script

[gatordevin]

Hello,
I moved the mic_over_mumble script into my home directory and tried to run it. It starts up the server immediately and lets me log in with my username however it then gets to Adding a virtual microphone in the terminal and the entire script stops and it says Connection failure Connection terminated. Any Ideas? I am on Ubuntu 18.04
Thank you

Starting Mumble server (murmurd)...
12553
Starting Mumble client...
Fetching PulseAudio configuration...
Changing PulseAudio configuration...
Adding sink...
Fetching current configuration to redirect Mumble...
No sink input found with this index.
Adding a virtual microphone...
Connection failure: Connection terminated

[gatordevin]

My Audio output on Ubuntu 18.04 has also failed

[pzmarzly]

No sink input found with this index.

That shouldn't have happened.

Could you run pavucontrol (you may need to install it first with sudo apt install pavucontrol) and observe what changes when you try adding a device manually via pactl load-module module-null-sink, and if that doesn't work, pacmd load-module module-null-sink?

[gatordevin]

Here was the result

[hamishmb]

I seem to have this problem as well

EDIT: I'm using Mint 19.3 with Cinnamon in case that's relevant to the issue.

EDIT 2: Adding a null output worked for me as well, with similar results to @gatordevin, except displayed differently because I'm using Cinnamon.

[rdrkr]

me too :(

[hamishmb]

Seems to work for me (not fully set up yet), but has a bug with cleanup - references a variable before use

[hamishmb]

Also is there a Mumble app for Android that's newer than Plumble? Seems to work but probably full of security holes cos it's so old

[pzmarzly]

Also is there a Mumble app for Android that's newer than Plumble

Wow, I had no idea that Plumble hasn't been updated since 2014. Sadly, I'm not aware of any other Mumble client.

Back when I got the idea about this script, I initially thought of Skype, but quickly realized that Teamspeak and Mumble server would have lower latency. Mumble seemed to be simpler to setup between those 2. OTOH since March I'm regularly streaming audio between devices via Discord (you need multiple accounts for that), and the delay is reasonable, too.

Anyway...

I think I solved our mystery.

$ pacmd list-sinks | grep -F -e "index: " -e "name: " | awk 'ORS=NR%2?" ":"\n"'
    index: 0    name: <combined>
  * index: 1    name: <alsa_output.pci-0000_00_1f.3.analog-stereo>
    index: 2    name: <null>
    index: 3    name: <Loopback_of_Mumble>

See that asterisk (star) that represents the default (current) device? I think that's what breaks everything (since @edaegonis 's fork fixes the issue by using the third column instead of the second).

Could you try changing your default device to something else than Loopback_of_Mumble? You can use pavucontrol, or just GNOME Settings. Change it while the script is running, and then reset the script (PulseAudio should remember your settings, but I may be wrong about that).

[hamishmb]

I'll have a go and let you know if it works for me.

[pzmarzly]

I pushed changes to master that make the script ignore that asterisk.

This should be fixed now, but I'll wait for a while for a confirmation.

[Maxcrazy1]

I have same mistake. 😥