> For the complete documentation index, see [llms.txt](https://docs.district.berlin/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.district.berlin/features/track-preferences.md).

# Track Preferences

Track Preferences can be found in the in-game menu under **Settings > Sound**.

## Analyzer

* **Max BPM** — Sets the maximum BPM of the analyzer's BPM range
* **Min BPM** — Sets the minimum BPM of the analyzer's BPM range

{% hint style="info" %}
The smaller the BPM range, the shorter the time it takes to analyze BPM.
{% endhint %}

* **Set First Beat Time At Current Position** — Sets the first beat offset time of the track on a deck at the current playback position

## Normalization

* **Normalization On Import** — Whether or not to apply audio volume normalization when a track is loaded to a deck
* **Target** — Sets the target volume of the normalization

## Streaming Quality

* **Bitrate** — Sets the bitrate of streaming audio (for tracks in the Online Library). A lower bitrate means shorter load times but reduced audio quality.

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


---

# 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.district.berlin/features/track-preferences.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.