Mumble: Feature request: "Sidetone", monitor/hear own voice in headphones

Created on 17 May 2018  路  4Comments  路  Source: mumble-voip/mumble

When using well-insulated headphones, it can be greatly beneficial to be able to hear yourself speaking. While this function is provided by some OSes, this essentially sends raw recording input to output. A native monitor feature could allow monitoring after filtering and normalized with the rest of the application (other users). It would also allow automatic toggling upon headphone insertion/removal.

A similar feature request had been filed on SourceForge long ago: https://sourceforge.net/p/mumble/feature-requests/1074/

client feature-request

Most helpful comment

In broadcast and telecom this kind of self-monitoring feature called Sidetone is very common. It usually can't be implemented server-side due to delay reasons. But implementing it locally in the Mumble client shouldn't cause severe delay issues if done properly, right?

Extensive tests have been done with in-ear monitoring systems commonly used by musicians on stage. Especially singers and musicians with absolute absolute pitch suffers when exposed to delayed self-monitoring. The tests show that an end-to-end delay path of about 5 ms (between microphone and headphone) is tolerable to most people. This might give some clue to the amount of self-monitoring delay that could be acceptable to Mumble users as well...

All 4 comments

As far as I know, a software solution has to much latency. I recommend a hardware solution like a USB audio interface with direct monitor function or a small audio mixer.

Ya, the delay would be debilitating. If you have a high-end _low latency_ audio interface it will be a built in feature.

The trouble with hardware or OS solutions is that these can't output your voice after Mumble's filters, and won't be normalized to the rest of the application, they generally only output raw input.

What level of intolerable latency are we talking? Even Mumble's loopback mode during configuration is more tolerable, to me at least, than being barely able to hear my voice.

In broadcast and telecom this kind of self-monitoring feature called Sidetone is very common. It usually can't be implemented server-side due to delay reasons. But implementing it locally in the Mumble client shouldn't cause severe delay issues if done properly, right?

Extensive tests have been done with in-ear monitoring systems commonly used by musicians on stage. Especially singers and musicians with absolute absolute pitch suffers when exposed to delayed self-monitoring. The tests show that an end-to-end delay path of about 5 ms (between microphone and headphone) is tolerable to most people. This might give some clue to the amount of self-monitoring delay that could be acceptable to Mumble users as well...

Was this page helpful?
0 / 5 - 0 ratings