> For the complete documentation index, see [llms.txt](https://support.audacityteam.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.audacityteam.org/troubleshooting/solving-recording-problems/delay-and-echoes-when-recording.md).

# Delay and echoes when recording

## Causes

Audible input monitoring usually causes a delay (latency) of the live recording input due to the time it takes to reach your headphones.

## Fixes

To prevent this, turn input monitoring off. This can be done by choosing **Transport > Transport Options > Enable audible input monitoring** and clicking it to remove the check (tick) mark.

To listen to the live recording input without playthrough latency requires **hardware** monitoring - that is; the input signal must be routed directly through the audio device from the input to the output rather than being passed through software from input to output.

{% hint style="success" %}
If the troubleshooting steps aren't working for you, feel free to ask in our communities:

* [Forum](https://forum.audacityteam.org/)
* [Discord](https://discord.gg/audacity)
  {% endhint %}


---

# 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://support.audacityteam.org/troubleshooting/solving-recording-problems/delay-and-echoes-when-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.