> For the complete documentation index, see [llms.txt](https://manual.minimal.audio/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://manual.minimal.audio/rift-manual/additional-settings.md). # Additional Settings ### Overview This section covers additional settings that customize how the plugin behaves and integrates with your production environment, including graphics settings, key commands, MIDI support, and more. ### Global Settings The [**Global Settings**](/rift-manual/additional-settings/global-settings.md) dropdown in Rift’s **Top Bar** includes useful options for initializing the preset, setting the plugin window size, adjusting how Rift responds to your DAW, and more. ### Key Commands Learn about additional [**Key Commands**](/rift-manual/additional-settings/key-commands.md) that can be used to access additional functionality or speed up your workflow. ### MIDI Learn Use [**MIDI Learn**](/rift-manual/additional-settings/midi-learn.md) to map the knobs and sliders on your MIDI controller directly to Rift’s controls, and save or load MIDI maps. ### MIDI Effect Routing Learn how to set up [**MIDI Effect Routing**](/rift-manual/additional-settings/midi-effect-routing.md) in your DAW so that Rift’s MIDI features respond to the notes you send to it. ### Parameter Locking Use [**Parameter Locking**](/rift-manual/additional-settings/parameter-locking.md) to preserve any parameter’s setting when switching presets. A common use is locking the dry/wet mix so it stays the same while auditioning presets. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://manual.minimal.audio/rift-manual/additional-settings.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.