> 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/welcome-to-rift/why-multipolar.md).
# Why Multipolar
### Overview
Rift's distortion engine is built around a technique that we call multipolar processing. This method allows you to manipulate the positive and negative portions of a waveform separately and **blend** the two halves in unique ways.
***
In practice, multipolar processing sounds different from and often much clearer than standard parallel or serial techniques, especially when used to fuse two distinct distortion effects. It also presents us with several ways of combining the two processed signals, allowing for exciting variations and movement inside the waveform.
***
One of the great things about Rift is that you don't need to understand what is going on under the hood to start creating extraordinary sounds. Virtually all of the presets make use of the multipolar distortion engine, and you can start combining different effects right away in the **Play View.**
---
# 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/welcome-to-rift/why-multipolar.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.
