"Can you hear me?"
"I can't hear you."
"Let me change the microphone settings."
"Can you hear me now?"
*horrible audio feedback*
"Can you hear me?"
"I can't hear you."
"Let me change the microphone settings."
"Can you hear me now?"
*horrible audio feedback*
Anyway, I don't really get what problem WebRTC solves, except for the non-problem of having to run specialized software on the clients. Instead it adds another set of broken mic settings...
We're building a virtual classroom solution and we now always force every user to go through a wizard which checks their audio and video, clearly marks when there is no sound being received and connects them to a support person to help them resolve their AV issues before they can join the meeting.
It's a little annoying for the person who wants to join, but the experience for the people already in the meeting/classroom is much better.
One interesting part is that, just like in a real classroom, by default everybody is unmuted. So you can have discussions with 80 students and one or multiple teachers. This makes stuff like echo cancellation, reducing the noise floor etc. a big part of the problem we attempt to solve.