> 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

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 <mark style="color:green;">`F10`</mark> key on your keyboard after you play your project.
* A window will open up as shown here.

<figure><img src="/files/jGdHRYOx1wfA0RYG47PC" alt=""><figcaption></figcaption></figure>

* From `Input` select your microphone and click on `Record`. This will start recording your audio.

<figure><img src="/files/uTCitYXHkmw9jcfwPNqU" alt=""><figcaption></figcaption></figure>

* 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 <mark style="color:green;">`Audio Gain`</mark> 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.convai.com/api-docs/plugins-and-integrations/unreal-engine/microphone-settings/microphone-test.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.