Closed neckcen closed 9 years ago
Added in 334bf392186d083094a71c3062c18f0d8dfe0bdb.
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!
The decrease in audio quality is likely due to Config.AudioDataBytes
having a low value compared to the new interval. You can either:
Config.AudioDataBytes
to a larger value, orgumbleutil.AutoBitrate
, which automatically sets Config.AudioDataBytes
, based off of the server's maximum bitrate.Adding client.Attach(gumbleutil.AutoBitrate)
did change Config.AudioDataBytes
value but did not help with sound quality.
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.
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:
(Feature request)
Currently the interval at which audio packets are sent is hardcoded as 10milliseconds. This seems to produce choppy sound for me when using 10ms buffer in mumble. Would it be possible to allow custom audio interval values?