> 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/lucid-manual/lucid-manual.md).

# Lucid Manual

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

### Welcome to Lucid!

Thank you for purchasing **Lucid** by Minimal Audio.

This manual covers the features, workflow, and philosophy behind Lucid, a granular effect plugin designed to help producers, musicians, and sound designers turn any sound into musical textures, harmonies, and rhythmic effects that stay in key, in time, and under control.

**PDF manual export**

You can export the latest version of this manual by clicking **Export as PDF** in the upper-right corner of this page. To download the **full manual**, select **All pages** in the export options.

Please note that PDF export is available on desktop only.


---

# 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://manual.minimal.audio/lucid-manual/lucid-manual.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.