Example: Setting the AudioCaptureAllowedUrls policy via Windows Registry
To set the AudioCaptureAllowedUrls policy via Windows Registry, create a key for Software\Policies\Google\Chrome\AudioCaptureAllowedUrls and add a REG_SZ value for each allowlist entry (entries for list keys should be 1, 2, 3, ...):
Setting the AudioCaptureAllowedUrls policy via the Windows Registry
Configuring the default Audio Capture Policy
To configure the default allow/deny audio capture policies across all extensions/websites, use the following policies:
How do I determine my browser's default microphone?
To view your browser's default microphone, visit Settings > Privacy & Security > Site Settings > Microphone. The microphones available to your browser will be listed in a drop-down:
Why does PixieBrix show the tab picker to capture system audio?
Chrome's permissions model currently only allows automatic tab media capture if the user has invoked the extension on the tab by:
Clicking the icon in the toolbar
Clicking a native context menu action
Invoking a registered Chrome keyboard shortcut associated with the extension
Unfortunately, Chrome does not detect clicking an embedded extension element (e.g., the floating action button, text selection menu) as invoking the extension. Therefore, for UI/UX consistency, PixieBrix always shows the media source picker.
What audio codec does PixieBrix capture/stream in?
PixieBrix uses the state-of-the-art Opus codec in WebM audio format (MIME type: audio/webm;codecs="opus" ). For more details, see Mozilla's Audio Codecs Guide
Can PixieBrix capture audio from desktop applications?
ScreenCapture must be allowed.
Due to operating system restrictions, system audio capture is only available on Windows.
To capture system audio, select "Entire Screen" and toggle on "Also share system audio".
Troubleshooting
Error "Requested device not found" starting microphone audio capture
The "Requested device not found" error indicates the browser was not able to detect/access the default microphone.