-
-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add ouput devices setting #4203
Comments
Ringing device we won't have control over, that'll just be whatever audio device the browser is outputting to, voip we should be able to direct to a specific output |
The voice output device is already a big step. |
We really need this, VoIP is unusable for some people without it. |
Apparently it has been implemented by the W3C for WebRTC : I don't know how well implemented this functionality is on browsers and electron though... |
It's definitely possible just missing someone to work on implementing it in react-sdk and js-sdk |
From my understanding we now have one audio output we can choose. Thanks ! Would it be possible to have two : one for the ringing and one for the communication. @t3chguy could you please reopen (since devices is plural in Add ouput devices) or should I open a new issue ? |
I don't know how feasibly that can be done given that it's just a Web browser under the hood which doesn't have such controls |
it depends on electron I guess (or any browser for the web app) but if you can't route 2 different signals on two different outputs at the same time, due to the technology riot is based on, first we could push a feature request to these techno, and then there is still the workaround to switch on two different outputs depending on if a conversation is currently occurring or no... I guess... no ? |
Current version allow only to set the microphone device. I think it would make sense to add a setting for the output device and optionally the ringing device.
Version
Homeserver is https://matrix.org
Identity Server is https://vector.im
matrix-react-sdk version: 0.9.1
riot-web version: 0.10.1
olm version: 2.2.1
The text was updated successfully, but these errors were encountered: