> For the complete documentation index, see [llms.txt](https://support.babylonwaves.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.babylonwaves.com/set-up-your-daw/how-to-set-up-in-digital-performer/key-switches.md).

# Key Switches

The key switches we use are identical to the trigger keys used in the output mapping of the Articulation Sets. This means if (for instance) E0 is used to switch to “Tremolo” in a particular library, we also use E0 to make the articulation map switch to Tremolo. For Spitfire libraries, the key switches follow the natural order of the articulation within the instrument. See below for more details.

In addition to this, we’ve consolidated the most important key switches into the first octave, starting at C-2. This way, all libraries behave the same regarding those changes.

There are a couple of instruments that do not follow this order. This is because they don’t contain enough techniques which fall into the categories in the diagram above. The name of the template of those instruments ends with a swung dash “\~”.

Here’s the layout:

<figure><img src="/files/Cx3hfks6dQEGyuoVc6ui" alt="" width="350"><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://support.babylonwaves.com/set-up-your-daw/how-to-set-up-in-digital-performer/key-switches.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.