Configurable audio packets interval about gumble HOT 6 CLOSED

Added in 334bf39.

from gumble.

Did a quick test using the audio-player.go example with config.AudioInterval = 40 * time.Millisecond added and the sound is badly mangled (same with 20 and 60ms).

My own knowledge of Go proved itself insufficient to locate the source of the problem, sorry!

from gumble.

The decrease in audio quality is likely due to Config.AudioDataBytes having a low value compared to the new interval. You can either:

1. Manually change Config.AudioDataBytes to a larger value, or
2. Use gumbleutil.AutoBitrate, which automatically sets Config.AudioDataBytes, based off of the server's maximum bitrate.

from gumble.

Adding client.Attach(gumbleutil.AutoBitrate) did change Config.AudioDataBytes value but did not help with sound quality.

from gumble.

Can you make a recording of the audio and share it? Also, what is the bitrate of your server? It's worth nothing that it was reported that audio transmission does not work well on low-end devices such as the Raspberry Pi.

from gumble.

Server bitrate is 72kb/s (hosted on a server with 10mbs bandwidth). For the purpose of testing I am running the program from my desktop computer so performances shouldn't be an issue.

30s recordings straight from mumble:

• 10ms interval (AudioDataBytes=43): http://vocaroo.com/i/s1gmev71Wv4j
• 20ms interval (AudioDataBytes=121): http://vocaroo.com/i/s0FAV5calQJ6
• 40ms interval (AudioDataBytes=258): http://vocaroo.com/i/s1mpcw1VfHW5

from gumble.