Hi Ed,
A bit of background:
When a user starts BigBlueButton, they are presented with the Audio Settings dialog. In this dialog, they can test/change their microphone or click Join.
Most users click Join, which causes Flash to query the user's OS and select the default microphone.
The problem:
The most common problem with using BigBlueButton is that default microphone isn't the active microphone. When this occurs, the user can hear others, but no one can hear them.
The solution:
Assuming they have a working microphone, the solution is to have the user open the audio settings dialog and choose the correct microphone. The steps are outlined in both the moderator/presenter and viewer tutorial videos.
As this is the most common problem, we're working on improving the Audio Settings dialog to make it very clear to the user which microphone they have chosen, whether their is any activity (energy) on that microphone, and warn them if the current select Microphone is working. See
A few more thoughts:
- If BigblueButton is not acting correctly, you can always refresh the browser. This will load the session anew and bring you back into the conference.
- It's best to plug in a new microphone *before* starting BigBlueButton. Flash queries the OS for the list of available microphones on startup, but not during the BigBlueButton session.
- One final suggestion, when using Google Chrome, the browser itself asks the user for permission for Flash to access the webcam/microphone. This means there are *two* areas a user must give permission: (1) the Flash Security Dialog and (2) Google's security prompt. It's easy to miss the second, and, if the user doesn't give Chrome permission as well, the microphone will not work.
Regards,... Fred
--
BigBlueButton Developer
BigBlueButton on twitter: @bigbluebutton