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

# System Requirements

Check the system requirements to run Eclipsa Audio Plugins smoothly, including OS, hardware, and DAW compatibility recommendations.

The Eclipsa Audio Plugins are currently supported for **Avid Pro Tools and REAPER** on macOS and Windows; and **Logic Pro and** **Premiere Pro** on macOS. To ensure optimal performance, please verify that your system meets the following minimum requirements.

### Supported Digital Audio Workstations

* AAX Support (macOS and Windows):
  * Avid Pro Tools 2021.9 or later.
* VST3 Support (macOS and Windows):
  * REAPER 7.39 or later.
* AU Support (macOS):
  * Adobe Premiere Pro 25.3 or later.
  * Logic Pro 11.2.2 or later.

### Minimum Requirements

* Operating System: macOS 14.0 or later; Windows 11 Professional / Enterprise.
* Processor:
  * macOS:
    * AAX / VST3 / AU: Apple Silicon M1 or later.
    * Logic Pro: Apple Silicon M3 or later.
  * Windows:
    * AAX / VST3: Intel i5 or higher.

***

<mark style="color:yellow;">**Note:**</mark> Intel processors for macOS are not supported

***

### Recommendations

* Memory: 16 GB RAM or higher.
* Storage: 1 GB of available disk space for installation and project files.
* Audio Interface: Professional-grade Core Audio-compliant device.

***

<mark style="color:yellow;">**Note:**</mark> The VST3 and AU versions of the plugin are only officially tested and supported on the DAWs listed above. It is not guaranteed that the plugin will load in other DAWs and some features may not work correctly.

***


---

# 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://docs.eclipsaapp.com/system-requirements.md?ask=<question>&goal=<user_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.
