> For the complete documentation index, see [llms.txt](https://docs.convai.com/api-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.convai.com/api-docs/plugins-and-integrations/unreal-engine/microphone-settings/microphone-test.md).
# Microphone test
This document elucidates the procedures for testing your microphone using the settings widget that comes with the Convai plugin.
Follow the steps outlined below to conduct a microphone test: -
{% hint style="info" %}
The following steps work when you have set the parent class of the player blueprint to ConvaiBasePlayer.
{% endhint %}
* Press the `F10` key on your keyboard after you play your project.
* A window will open up as shown here.
* From `Input` select your microphone and click on `Record`. This will start recording your audio.
* Record your audio for a few seconds and click on `Stop`.
* If your microphone is working properly you must hear your audio loud and crisp.
* If the audio sounds to be low then adjust the `Audio Gain` accordingly.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.convai.com/api-docs/plugins-and-integrations/unreal-engine/microphone-settings/microphone-test.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
