Microphone and recording problems in Rhazes
What each Rhazes microphone error means and how to fix it, from blocked permissions to another app holding the microphone.
Updated
Rhazes tells you which problem it is
The error names the cause, and the causes need different fixes. Match what you saw to the list below.
Microphone access is blocked
Your browser or device is refusing permission.
Allow Rhazes to use the microphone in your browser's site settings, then reload. On Windows and macOS, also check the system privacy settings, since the browser itself can be blocked at the operating system level, which no amount of clicking allow inside the browser will fix.
Rhazes could not find a microphone
No input device is available. Connect or enable one, and if you are using a headset, check it is properly connected and switched on.
Another app or browser tab may be using it
Something else has the microphone. Teams, Zoom, another Rhazes tab, or a meeting you left running in the background are the usual culprits.
Close the other application or tab, then try again. On Windows this is far more common than people expect, because an ended meeting does not always release the device.
The page is not secure
Browsers only allow microphone access over a secure connection. Open Rhazes at an address beginning with https://.
If you reached Rhazes through a link that dropped the secure prefix, type the address properly instead.
Microphone setup was interrupted
Usually transient. Try again.
No sound was recorded
The microphone opened but captured nothing. Check that the right input is selected, that the device is not muted, and that a physical mute switch on a headset is not on.
Worth doing before a clinic
Record ten seconds and play it back. Finding out your microphone is muted takes a moment beforehand and an entire consultation afterwards.