# Microphone and Audio Capture Configuration By default, the browser will prompt the first time PixieBrix requests to use the microphone. ### Manually Allowing/Blocking Microphone Capture Navigate to Settings > Privacy & Security > Site Settings > Microphone > PixieBrix. For the Microphone permission, select "Allow" from the dropdown.

Setting the Microphone Permission

### Allowlisting PixieBrix Audio Capture via Policy {% hint style="info" %} If you are an Enterprise customer with a custom extension build, provide the extension ID of your extension {% endhint %} To automatically allow audio capture using PixieBrix, use the following Chrome policies: **Microphone Capture** * [AudioCaptureAllowedUrls](https://chromeenterprise.google/policies/#AudioCaptureAllowedUrls) **Screen/Window/Tab Audio Capture** {% hint style="warning" %} Provide at most one of the following screen/window/tab capture policies. For example, setting the TabCaptureAllowedByOrigins policy [causes the browser to not consider the ScreenCaptureAllowed policy](https://chromeenterprise.google/policies/#TabCaptureAllowedByOrigins:~:text=If%20a%20site%20matches%20a%20URL%20pattern%20in%20this%20policy%2C%20the%20following%20policies%20will%20not%20be%20considered%3A%20WindowCaptureAllowedByOrigins%2C%20ScreenCaptureAllowedByOrigins%2C%20ScreenCaptureAllowed) {% endhint %} * [ScreenCaptureAllowedByOrigins](https://chromeenterprise.google/policies/#ScreenCaptureAllowedByOrigins) * Allows Desktop, Window, and Tab capture * Enabling Screen capture is useful for recording audio from other applications, e.g., desktop telephony applications * Operating System Compatability: desktop audio capture is not available on MacOS due to OS limitations * [WindowCaptureAllowedByOrigins](https://chromeenterprise.google/policies/#WindowCaptureAllowedByOrigins) * Allows Window and Tab capture * [TabCaptureAllowedByOrigins](https://chromeenterprise.google/policies/#TabCaptureAllowedByOrigins) * Allows Tab capture only For more information on URL patterns, see Chrome's documentation for [Enterprise policy URL pattern format](https://chromeenterprise.google/policies/url-patterns/). #### Microsoft Configuration {% hint style="info" %} If you have a custom extension build, replace the entry with your extension ID {% endhint %}
Registry PathTypeEntries
Software\Policies\Google\Chrome\AudioCaptureAllowedUrlsList of strings

PixieBrix: [*.]mpjjildhmpddojocokjkgmlkkkfjnepo

PixieBrix BETA: [*.]mpapkmgkphbggmlekkfnoilmafnbfile

Software\Policies\Google\Chrome\TabCaptureAllowedByOriginsList of strings

PixieBrix: [*.]mpjjildhmpddojocokjkgmlkkkfjnepo

PixieBrix BETA: [*.]mpapkmgkphbggmlekkfnoilmafnbfile

#### 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: * [AudioCaptureAllowed](https://chromeenterprise.google/policies/#AudioCaptureAllowed): microphone * [ScreenCaptureAllowed](https://chromeenterprise.google/policies/#ScreenCaptureAllowed): tab audio If set to false, only allowlisted extensions/origins will be able to capture audio. See the previous section:[#allowlisting-audio-capture-via-policy](#allowlisting-audio-capture-via-policy "mention") | Registry Path | Type | Value | | ---------------------------------------------------------------------------------------------------------------------- | ---------- | ----- | | [Software\Policies\Google\Chrome\AudioCaptureAllowed](broken://spaces/ommcSgrw3Ur9tewdME1S/pages/k06Mma6CgISQWO3WB62E) | REG\_DWORD | 1 | | [Software\Policies\Google\Chrome\ScreenCaptureAllowed](https://chromeenterprise.google/policies/#ScreenCaptureAllowed) | REG\_DWORD | 1 | ### Frequently Asked Questions #### 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: ``` chrome://settings/content/microphone ``` #### 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. We're [working with the browser vendors to adjust the requirements](https://github.com/w3c/webextensions/) #### What audio codec does PixieBrix capture/stream in? PixieBrix uses the state-of-the-art [Opus](https://opus-codec.org/comparison/) codec in WebM audio format (MIME type: `audio/webm;codecs="opus"` ). For more details, see [Mozilla's Audio Codecs Guide](https://developer.mozilla.org/en-US/docs/Web/Media/Guides/Formats/Audio_codecs#opus) #### 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. Verify your browser's default microphone setting. See: [#how-do-i-determine-my-browsers-default-microphone](#how-do-i-determine-my-browsers-default-microphone "mention") --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.pixiebrix.com/enterprise-it-setup/browser-extension-installation-and-configuration/browser-extension-configuration-policy/microphone-and-audio-capture-configuration.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.