You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Every now and then we receive feature requests that we think would be awesome if they were implemented but they'd require such a huge rework of how things currently work or just so much work in general, that at least for the foreseeable future the request is close to impossible (as in: implemented by a volunteer).
This issue is intended to act as a collector for such requests in order to not lose them completely. However we don't like to keep these requests around as separate issues, since we believe that issues should (in general) represent actionable pieces but considering the required amount of work such tickets can barely be called actionable. Therefore we'll close such requests and instead keep track of the ideas here.
This collection is mainly intended as a list of "Should we ever rewrite that part of Mumble, we want to do it in a way that allows these features to be implemented along with it".
If you want to comment on any of these ideas, please do so in the original issue (which will always be linked from here) in order to keep this as a pure overview issue.
Should you want to work on any of these issues, please comment in the original issue as well and we'll reopen it for you to indicate that there is active work going on.
The text was updated successfully, but these errors were encountered:
The idea would be to have the possibility to choose different audio output devices (sinks) for different kinds of audio output (e.g. speech vs. notification sounds).
The reasoning being that this would e.g. allow for
Applying external software noise filters to incoming speech
Have communication go through headset but have notifications through regular speakers in order to be able to lay the headset aside without unplugging it but still be able to receive notifications.
Every now and then we receive feature requests that we think would be awesome if they were implemented but they'd require such a huge rework of how things currently work or just so much work in general, that at least for the foreseeable future the request is close to impossible (as in: implemented by a volunteer).
This issue is intended to act as a collector for such requests in order to not lose them completely. However we don't like to keep these requests around as separate issues, since we believe that issues should (in general) represent actionable pieces but considering the required amount of work such tickets can barely be called actionable. Therefore we'll close such requests and instead keep track of the ideas here.
This collection is mainly intended as a list of "Should we ever rewrite that part of Mumble, we want to do it in a way that allows these features to be implemented along with it".
If you want to comment on any of these ideas, please do so in the original issue (which will always be linked from here) in order to keep this as a pure overview issue.
Should you want to work on any of these issues, please comment in the original issue as well and we'll reopen it for you to indicate that there is active work going on.
The text was updated successfully, but these errors were encountered: