Starweave

Support

Build help, audio setup, and plugin scanning. File bugs on GitHub issues.

Build

cd pre-ai-polyrhythm_daw
cargo test
cargo run --release

Linux packages need build-essential, pkg-config, libasound2-dev, and the X11/XCB libraries listed in the project README. Native plugin editors embed with X11; if a plugin returns BadMatch, the slot falls back to the parameter panel.

Audio glitches

VST3 and CLAP

Plugin Manager → Scan / Rescan walks the usual folders:

Use Add Scan Folder for anything outside those paths. A VST3 bundle is the .vst3 directory. Scan lists that bundle once — not the .so files inside Contents/. If the bundle includes Contents/Resources/moduleinfo.json, the list shows that name, vendor, and whether it is an effect or an instrument.

Loading probes the plugin in a short-lived child process before attaching it in-process, at the audio device sample rate (the SR readout in the status bar). A probe that fails leaves a bypass slot instead of taking down the session. Successful probes are remembered until you quit, so reloading the mixer does not spawn that child again.

Free Linux plugins to test hosting

Install the bundle directory, not a loose .so copied out of it.

mkdir -p ~/.vst3 ~/.clap
cp -a "/path/to/Surge XT.vst3" ~/.vst3/
cp -a /path/to/DragonflyRoomReverb.vst3 ~/.vst3/

Then Plugin Manager → Scan / Rescan. Expect one row per bundle, path ending in .vst3 or .clap. Load Dragonfly as an effect or Surge as an instrument.

License key rejected

Buy Flame or Eternal on iinventedlight.com (Gumroad checkout), then paste the receipt key. The machine ID in Settings → License has to match the ID an offline key was generated for. Offline keys do not transfer to another computer. See License.