Skip to content
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

Remember audio input/output devices across sessions to skip repeated Echo Test #10127

Closed
antobinary opened this issue Jul 27, 2020 · 5 comments
Closed

Comments

@antobinary
Copy link
Member

Remember the last [successful] choice of audio input (microphone) and audio output (speakers/earphones) so that instead of showing Echo Test on initial page load, those pre-saved devices are automatically attempted (getUserMedia())

The data could then be shared between sessions across all subdomains of the same domain demo-one.bigbluebutton.org, demo-two.bigbluebutton.org, etc.

There needs to be a way to force-trigger Echo Test in case the pre-stored set of values is not the desired one for the current session.

@antobinary antobinary added this to the Release 2.3 milestone Jul 27, 2020
@hd42
Copy link

hd42 commented Sep 10, 2020

This would be useful even with echo test. Currently I always have to pass the echo test twice - once with the default values, ones after I've set my preferred room microphone and speaker for the video conference. If my choices were remembered, I'd only have to pass one echo test.

@jabelar
Copy link

jabelar commented Sep 15, 2020

This is actually quite a big issue as if you have a system (not uncommon) have headset, built-in microphone and a recording microphone, every connection needs to go through echo test twice. Furthermore, if you need to change your audio settings during the call you can spend a couple minutes interrupting the class/meeting.

At very least can you skip the echo test? or detect lack of audio? Also, the browser doesn't remember that I've given permissions (to use microphone) to the site (I guess because it is unique URL).

Overall this whole process takes WAY to many clicks and time for a usable UI...

@mariogasparoni
Copy link
Contributor

The device change without reconnecting audio is covered by #11813 (already merged in 2.3-beta-2)
Storing the current microphone/speaker for the same session/breakouts is being covered here #11663 (currently a WIP)

We can close this issue and treat these problems individually , in the mentioned issue/PR

@antobinary
Copy link
Member Author

We can close this issue and treat these problems individually , in the mentioned issue/PR

Closing

@antobinary
Copy link
Member Author

Likely relevant #15770 (link from @ramonlsouza )

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants