Closed VasyaPupkins closed 8 months ago
Hmm, we already have #17610, but only for output device @Aokromes what do you think?
17610 gives 404 for me, maybe reporterer is banned.
Oops, it's #16710
maybe we replace that with this.
Ideally I'd rename this issue to have separate one for input, but since we can't do that, that seem to be the best choice, yeah
I really need an option to make Telegram respect default communication device, instead of choosing a device manually all the time. All other apps I use for communication use a default communication device, why not Telegram?
Well, there's no such API in the underlying library Telegram uses for audio output/input (https://github.com/kcat/openal-soft) and even if it was, people were constantly creating issues like "doesn't respect default device" or "doesn't respect ducking settings" back in the time when libtgvoip was used for calls which was using default communication device (as it has custom platform audio implementations).
Although, it's really offtopic to this issue, this issue is about having settings for non-call audio (which shouldn't use default communication device at all).
Looks nice! I think that the default option should be to use the same for calls. An option to respect a Windows "default communication device" would also be welcome, if at all possible.
This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.
Is your feature request related to a problem?
Inability to route Telegram input / output in systems with multiple audio devices or complex audio routing setups.
Describe the solution you'd like
Ability to choose / override system default audio input / output device.
Describe alternatives you've considered
Ability to choose / override system default audio input / output device.
Additional context
No response