# Input and Pitch Range

***

### Overview

Use the **Input** and **Pitch Range** controls to clean up the input before any processing and to define how pitch detection operates across frequency ranges.

These settings help optimize Evoke for your input, but they typically don’t require frequent adjustment.

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

***

### 1. Input Gain

Set the input level before any pitch detection or processing. This is useful for gain staging or driving a preset. Raising the level of very quiet signals can improve pitch detection, although this is not usually necessary.

### 2. Input Gate

Set the amount of gating applied to the input signal before any pitch detection or processing. This helps remove unwanted noise that can cause unstable pitch detection and other artifacts.

Two **Gate Speed** options are included:

* **Fast.** Reacts quickly to level changes. Ideal for dynamic sources.
* **Slow.** Reacts more gradually. Ideal for sustained sounds.

### 3. Pitch Detector Range

The **Pitch Range** setting limits Evoke’s pitch detection to a specific frequency range. Match it to your input to reduce pitch flutter and other tracking artifacts. This setting also affects Evoke's total latency: lower ranges require more latency, while higher ranges can run with less.

Four **Pitch Range** options are available:

* **Full.** Detects pitches across the entire frequency range. Good for quick setup, but often less stable than the more restrictive options.
* **High.** Limits pitch detection to higher frequencies.
* **Mid.** Limits pitch detection to midrange frequencies.
* **Low.** Limits pitch detection to low/bass frequencies.

{% hint style="info" %}
While audio is playing, the circular indicator next to a range option highlights the recommended setting. This can help if you’re unsure which range to choose.

Note that a range that isn’t always recommended may still product good results. For instance, if both **High** and **Mid** are highlighted during different sections of a track, either will likely work. Choose the one that’s recommended more often.
{% endhint %}


---

# 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://manual.minimal.audio/evoke-manual/keyboard-panel/input-and-pitch-range.md?ask=<question>
```

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.