A number of Mumble clients have the following quality presets:
High: 72 kbit/s, 10 ms audio per packet
Balanced/Medium: 40 kbit/s, 20 ms audio per packet
Low: 16 kbit/s, 60 ms audio per packet
When building the MumbleClientGui example, I've discovered that when another client transmits with the Low preset, MumbleClientGui produces entirely corrupted audio playback for that user even when a jitter buffer is implemented. A few dozen ms of audio (perhaps a packet or two) can be heard between complete silences. Medium and High presets seem to work well with a jitter buffer.
I'm not sure whether it's the audio packet length or the bitrate that's responsible for this behavior. I'm also not sure if it's a playback implementation detail in MumbleGuiClient or if the behavior is intrinsic to MumbleSharp.
A number of Mumble clients have the following quality presets:
When building the MumbleClientGui example, I've discovered that when another client transmits with the Low preset, MumbleClientGui produces entirely corrupted audio playback for that user even when a jitter buffer is implemented. A few dozen ms of audio (perhaps a packet or two) can be heard between complete silences. Medium and High presets seem to work well with a jitter buffer.
I'm not sure whether it's the audio packet length or the bitrate that's responsible for this behavior. I'm also not sure if it's a playback implementation detail in MumbleGuiClient or if the behavior is intrinsic to MumbleSharp.