简体中文
English
Website review
This review may include AI-generated content and is not individually verified. Domain, certificate and other facts come from the observed data on this page.
What is Airwindows?
Airwindows is a free, open-source collection of digital audio plugins made by a single developer, Chris. It focuses on bespoke, "human-made" audio tools—console emulations, EQ, saturation, and utility processors—rather than a large commercial suite. The plugins are released under the MIT license and supported through Patreon.
Its defining trait is a deliberately minimal, often no-GUI approach: many plugins are standalone or lightweight builds designed to run in a DAW or even on a Raspberry Pi. Newer GUI versions exist, but the core philosophy favors sound and flexibility over visual polish.
What you'll find there
- Console-style processors (for example, ConsoleX3) that emulate analog mixing behavior
- Standalone and GUI versions of plugins, including no-GUI builds for low-resource systems
- Customizable interface files, such as AirwindowsGlobals, so you can change the look
- Ongoing experiments and new algorithms, sometimes first appearing inside a larger plugin before becoming standalone
Who it suits
- Producers and engineers who want free, adaptable tools and don't mind a sparse interface
- Tinkerers comfortable with GitHub releases, manual installs, and file-based customization
- Users on unusual setups, like Raspberry Pi or surround workflows, where standard commercial plugins may not fit
Trade-offs
The no-frills approach means less visual feedback and a steeper setup process than typical paid plugins. Some releases are works in progress, and installation quirks—such as conflicts between GUI and non-GUI Audio Unit versions—require attention. In exchange, you get open-source code, unusual algorithms, and no cost.
If you're curious, start with the ConsoleX3 release page on GitHub, download the version number at the top, and try it in a simple mix session before committing to a full install.
How do I install ConsoleX3 from GitHub?
Go to the ConsoleX3 releases page on GitHub, open the release marked with the highest version number, and download the asset that matches your system and plugin format. The page notes that the intended release may not be flagged as "latest," so check the version number itself rather than trusting the badge.
Choosing the right download
- GUI version: Download the graphical build if you want the full interface. The release notes warn that its installer will refuse to run if a plugin with the same name is already installed, so remove any existing ConsoleX3 plugin first.
- No-GUI/standalone version: Choose this for lightweight or headless setups, including Raspberry Pi. It ships as AU and VST2.
- Surround use: You must use the
ConsoleX3MonoAudio Unit. It handles any channel count, but it does not do surround panning — handle that with a separate panner.
After installing
If you want the grey watercolor look or other custom styling, download the AirwindowsGlobals package. It contains a text file, a folder structure, and a JPEG. Place the Airwindows folder inside your Documents folder so the plugin finds Documents/Airwindows/AirwindowsGlobals.txt, with the image beside it. On systems where the plugin looks elsewhere for documents, put the folder in that location instead.
A practical sequence: uninstall or move any older ConsoleX3 plugin, download the correct asset, install it, then confirm your DAW rescans and lists it. If it doesn't appear, the duplicate-name conflict is the first thing to check.
What is the difference between the GUI and no-GUI versions of Airwindows plugins?
The GUI versions add a graphical interface for controlling the plugin, while the no-GUI versions are standalone builds without one. Both run the same underlying audio processing; the difference is how you interact with the controls and where the plugin can be installed.
GUI versions
- Designed for use inside a DAW as AU or VST2 plugins.
- Offer a visual interface, including the option to customize its look. Airwindows provides an
AirwindowsGlobalsfile and a grey watercolor texture; placing theAirwindowsfolder in your Documents folder (on Mac) lets the plugin find those files. - The GUI installer may refuse to install if a plugin of the same name already exists, so the page warns against installing the Audio Unit from the no-GUI package first.
No-GUI versions
- Distributed as standalone builds, including for platforms such as Raspberry Pi.
- No visual interface, so they suit headless setups, lightweight systems, or users who prefer host-native generic controls.
- Available in existing standalone plugin collections; ConsoleX3 is excluded from the Consolidated collection because it has too many controls.
Practical differences
| Aspect | GUI version | No-GUI version |
|---|---|---|
| Interface | Custom graphical window | None; host or generic controls |
| Typical use | DAW sessions where you want visual feedback and customization | Headless machines, Raspberry Pi, minimal installs |
| Installation | AU/VST2 installer, may conflict if same-named plugin exists | Standalone package, separate from the GUI install |
| Surround | Use ConsoleX3Mono for any channel count; no surround panning |
Same processing, but check the standalone build's channel support |
A useful next step: decide whether you need a visual interface and custom skinning. If yes, install the GUI version first and avoid mixing in the no-GUI Audio Unit. If you are running a Raspberry Pi or a headless rig, start with the no-GUI standalone. For ConsoleX3, the GUI release is on GitHub, and the page notes that the standalone no-GUI package is a separate download. Airwindows plugins are free and open source under the MIT license, with development supported through Patreon.
How do I use the ConsoleX3Mono Audio Unit for surround audio?
ConsoleX3Mono is the Audio Unit build of Airwindows ConsoleX3 that handles any channel count, so it is the version to reach for when you want surround rather than stereo. The trade-off is that it does not do surround panning: it processes the channels you feed it, and you place and pan the signal elsewhere in your host.
Practical setup
- Install the Audio Unit from the ConsoleX3 release you want, then insert ConsoleX3Mono on a surround-capable track, bus or output in your DAW.
- Confirm your host is actually running that path in multichannel mode; a mono or stereo instance will not exercise the extra channels.
- Do your panning with the host's own surround panner or a separate panning plugin, not with ConsoleX3Mono.
- If you also want the GUI version, install only one of the two builds — the GUI installer can refuse to run when a plugin of the same name is already present.
Choosing between the builds
| Build | Channel handling | Best for |
|---|---|---|
| ConsoleX3Mono (AU) | Any number of channels | Surround and multichannel sessions |
| GUI version | Standard channel layouts, with the full interface | Stereo work where you want the visual controls |
| No-GUI standalone | Fixed standalone formats | Lightweight or headless setups such as Raspberry Pi |
A concrete case: mixing a 5.1 stem bus, you would insert ConsoleX3Mono across the bus, keep your existing surround panner feeding it, and leave the GUI version out of that session entirely to avoid the duplicate-name install problem.
Next step: check the release notes on the ConsoleX3 GitHub repository for the current version number before downloading, since the newest build is not always flagged as the latest release.
How can I customize the look of Airwindows GUI plugins with AirwindowsGlobals?
AirwindowsGlobals is the customization layer for the GUI versions of Airwindows plugins. It works through a small text file plus an image file, both kept in a folder the plugins read at startup, rather than through settings inside each plugin window.
How the setup works
- Create or use an
Airwindowsfolder inside your Documents folder. - Place
AirwindowsGlobals.txtin that folder, withGreyWatercolor.jpg(or your own image) beside it. - On macOS the plugins look in Documents by default. If your host looks elsewhere for documents, put the folder where it actually looks.
- The text file ships with comments explaining the available options, so you can edit it without guessing at syntax.
What you can change
The main practical target is the background texture — the grey watercolor look — which you can swap for any image you like. Beyond that, the text file is the control surface for the appearance, and the page explicitly invites users to "make the Airwindows GUI plugins your own in this way."
A realistic workflow
Pick one plugin, copy the Globals folder into place, replace the jpeg with a simple image of your own, and reopen the plugin to confirm it loads. Once that works, edit the text file settings one at a time so you can tell which change did what. If your image is the wrong aspect ratio or very large, expect it to look stretched or to slow down plugin opening — keep replacement images modest in size and match the original's proportions.
Things worth knowing before you start
- This applies to GUI builds. The standalone, no-GUI versions (including the Raspberry Pi builds) don't have a look to customize.
- If you install the Audio Unit from the standalone package alongside a GUI version of the same plugin name, the GUI installer may refuse to proceed. Decide which one you want first.
- The same page notes that surround use requires the
ConsoleX3MonoAudio Unit, which handles any channel count but does no surround panning.
Next step
If you want the exact current file and folder layout rather than relying on memory, get it from the source: GitHub. The Airwindows site itself, Airwindows, is where new plugin announcements and the Globals notes appear.
Are Airwindows plugins free and open source, and how is the project funded?
Yes. Airwindows plugins are released as free and open source under the MIT license, and the project is funded through Patreon support rather than plugin sales or licensing.
H3 What "free and open source" means here The MIT license is permissive: you can use the plugins in personal or commercial work, modify them, and redistribute them. The source is published openly, and builds are distributed through the developer's own channels, including GitHub releases for newer tools. Airwindows is essentially a one-person project by Chris, so the open-source model and the funding model are directly linked — the code is given away, and listeners who find it useful are asked to support its continued development.
H3 How funding works Support comes from Patreon, which the developer describes as the mechanism behind the work. That is a voluntary patronage model: there is no paywall, no license key, and no requirement to pay to download or use a plugin. In practice this means the catalog's sustainability depends on whether enough users choose to contribute, not on sales volume.
H3 Practical implications for you
- Cost: no purchase step, so you can download and evaluate without a budget decision.
- Risk profile: if patronage declines, maintenance and new releases could slow, since there is no commercial revenue cushion.
- Flexibility: the MIT terms let you adapt plugins, bundle them into your own tools, or build standalone versions — the page notes standalone, no-GUI builds for platforms such as Raspberry Pi.
- Support expectations: with a single developer, bug fixes and feature requests move at one person's pace.
A useful next step if you rely on these tools regularly is to treat Patreon support as the ongoing cost of the software, the same way you would budget for a paid plugin you depend on. If you only need one or two effects occasionally, downloading freely and contributing later is entirely consistent with how the project is set up.
User reviews (0)