search

dchote / talkiepi

The talkiepi project is for a truly headless mumble client for the Raspberry Pi, utilizing static config and GPIO for status LEDs and a button for push to talk
Mozilla Public License 2.0
271 stars 107 forks source link

Intermittent Connectivity #10

Open AFstache opened 5 years ago

AFstache commented 5 years ago

Full install went perfectly, I'm connected to my personal mumble server but when I push the PTT, my connection window on my phone shows the pi intermittently transmitting. I've used my server between phones before, I've tested audio from my phone to the pi, but for some reason, the other direction isn't working.

MarceloCampos commented 4 years ago

@AFstache i was experiencing the same problem with Raspi ZeroW and moving to Raspi B / wired connection this problem was solved. But with Zero or B I´m having other problem: when press to talk is pressed in one board the other board leaves the channel, like losing mumble server connection... I´ll open another issue for this problem

mnoonan296 commented 4 years ago

I'm also experiencing intermittent choppy transmission when I press PTT with my Raspi Zero W. I have spent so many hours on it, determined not to be beat. Any ideas?

MarceloCampos commented 4 years ago

I'm also experiencing intermittent choppy transmission when I press PTT with my Raspi Zero W. I have spent so many hours on it, determined not to be beat. Any ideas?

@mnoonan296 I had experienced same problem with PiZW, and was solved doing the recomended by author here: https://github.com/dchote/talkiepi#pi-zero-fixes

mnoonan296 commented 4 years ago

Thanks so much @MarceloCampos. I tried the workarounds and then receive the following error when I try to connect to the mumble server:

/home/pi/go/bin/talkiepi: error while loading shared libraries: libsndio.so.6.1: cannot open shared object file: No such file or directory.

Is this something you've encountered?

mnoonan296 commented 4 years ago

Thanks so much @MarceloCampos. I tried the workarounds and then receive the following error when I try to connect to the mumble server:

/home/pi/go/bin/talkiepi: error while loading shared libraries: libsndio.so.6.1: cannot open shared object file: No such file or directory.

Is this something you've encountered?

I see this is picked up in another thread - libsndio6.1 required by workarounds but not installable. Seems a few people are stuck on this.

mnoonan296 commented 4 years ago

After lots of mucking around and workarounds, I got Talkiepi working. Here is a full description of my steps:

https://github.com/mnoonan296/talkiepi/blob/master/doc/README.md

DauTorsten commented 4 years ago

Hi mnoonan296,

you did it! It works flawless with my local pi Mumble server and with Mumla (Android) for testing. You saved the voicecard from being disposed. I bought it over one year ago for no other purpose .

I just had to add my mumble password ... maybe users even less experienced than me might get stuck here:

$$GOPATH/bin/talkiepi -server YOUR_SERVER:PORT -username YOUR_USERNAME -certificate /home/pi/mumble.pem -channel Root -password YOUR_PASSWORD

Thanks a lot! Best regards Torsten

dbeltjr commented 1 year ago

Back to the OP's original problem, I am experiencing the same issue. Rather than a Pi 3B+ I am running a Pi 3A+ (has a lot of the same components as 3B+ but without Wired NIC and only 1 USB port, perfect for the TalkiePi). I have 3 up and running on my home mumble server and it all works great, except the intermittent transmitting. On my android mumla app, I can see each TalkiePi transmit, but the red light flashes intermittently and the transmission is skipping (on all 3). If I adjust the mic input volume to around 50% ( amixer -c 1 set Mic 50%) it works pretty good, however it is very quiet compared to using the android app. Has anyone determined a cause or a fix?

zrdimetc commented 1 year ago

@dbeltjr. If you compare performance of talkiepi talking to another talkiepi - against Plumble or Mumla, you will surely find that all inter talkiepi communication is smooth. There is no breaking up. Breaking up will only be evident in the direction from talkiepi to Mumla. That means, the issue is in Plumble / Mumla decoding of talkiepi 16k audio. You will need to tweak either talkiepi or Mumla. You can check talkkonnect fork of talkiepi and try it with Mumla. Is talkkonnect breaking up in Mumla? Look at changes in gumble libraries between talkiepi and talkkonnect. Raspberry Pi 3A+ is capable enough to work with 48k audio. Raspberry Pi Zero is not, therefore the audio sampling rate was dropped to 16k in talkiepi. Which in turn, results with problem you reffered to with Android client. You need to tweak audio.go from gumble. This will be more easy. Or fix Mumla - more complex.