> For the complete documentation index, see [llms.txt](https://docs.twintune.ai/twintune/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.twintune.ai/twintune/tips-and-recommendations/audio-recording.md).

# Audio Recording

In this section, you will find a complete list of tips and recommendations for making high quality audio recordings that can be used for both dataset building and inference.

* Use a quality mic with a wide frequency range (40hz-20khz).
* Set the recording sample rate to 48khz and the file type to lossless (.wav, .aiff, .flac).
* Limit breath sounds and try to capture a clean tone (avoid plosives, place the mic off-axis and/or use a pop filter if you sing in a breathy style).
* Avoid room reflections (record in a room with soft surfaces such as carpets and furniture to absorb sound, place microphones away from walls, move closer and reduce input gain).
* Control the recording volume and avoid exceeding -6 dBFS. Try to keep your levels between -12 and -6 dBFS.
* Once the recording is finished it is advisable to export your audio as true mono (instead of stereo with equal L + R channels).
* Avoid abrupt audio cuts (add a short fade out to avoid the clicks that occur when cutting audio before or after a zero crossing).


---

# 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.twintune.ai/twintune/tips-and-recommendations/audio-recording.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.