Support

DARKSTAR Support

Setup guides, documentation and troubleshooting for DARKSTAR, and a direct line to the team when you need more.

01

Getting Started

Installation, first launch and getting DARKSTAR running in your DAW.

Install the VST3 build into your DAW’s VST3 plugin folder, or launch the Windows standalone build directly. If your DAW doesn’t detect the plugin right away, rescan its plugin folders.

DARKSTAR opens on the Init patch by default. Load a factory preset — Event Horizon (Lead) or Cold Orbit (Pad) — from the preset browser to hear the synth working end-to-end before building your own sound.

Add DARKSTAR as an instrument on a track the same way you’d load any VST3 synth, then feed it MIDI from a keyboard, a MIDI clip, or your DAW’s piano roll. No special routing is required to get sound out.

The Windows standalone build lets you pick an audio output; a full settings page for sample rate and buffer size is still being finished. For complete control over your audio device and buffer size today, run DARKSTAR as a VST3 plugin inside your DAW instead.

Inside a DAW, MIDI works the normal way: arm a MIDI input on the DARKSTAR track and select your controller as the DAW’s input device. Direct hardware MIDI input in the standalone build is still being finished. The browser demo accepts MIDI too, depending on your browser’s Web MIDI support.

02

Documentation

Specifications, platform compatibility and known limitations for every system inside DARKSTAR.

Voice, oscillator, unison and wavetable specifications live on the Docs page.

Envelope, LFO and modulation-matrix specifications live on the Docs page.

Filter types and ranges live on the Docs page.

How Singularities focus the interface around a sound-design intent — covered on the Docs page.

How Anomalizer generates bounded variations — covered on the Docs page.

How patch-to-patch morphing works, and where it falls back — covered on the Docs page.

View documentation
03

Troubleshooting

Fixes for the most common setup issues.

Confirm your DAW has rescanned its plugin folders after installation, and that DARKSTAR was installed to the folder your DAW actually scans. If it still doesn’t appear, contact support with your DAW and operating system.

Check that the correct audio output is selected in your DAW and that the track isn’t routed to a muted or disconnected bus. Also check DARKSTAR’s own Master level — there’s no limiter, so a low Master gain is a common culprit. If the issue continues, contact support with your audio interface and buffer size.

Make sure a MIDI source is armed on the DARKSTAR track and that your controller is selected as an input device in your DAW. If this doesn’t resolve it, reach out with your controller model.

Heavy patches — high unison counts, all three oscillators active, deep modulation, a full effects rack — ask more of your CPU than a simple patch. If you hear crackling or dropouts, raise your audio buffer size first, then reduce unison or voice count on the patch causing it.

Make sure you have permission to write to your DAW’s plugin folder, and that antivirus or SmartScreen isn’t blocking the installer or executable. If installation still fails, contact support with the exact error message.

04

Updates

Stay current with the latest build of DARKSTAR.

DARKSTAR is sold through our LemonSqueezy store. Your purchase confirmation email and your LemonSqueezy account page both link to the current download at any time.

Release notes accompany every update, so you know what changed before you install it.

V1 release

Installer & file integrity

The NSIS installer installs the standalone app and, by default, the VST3 in %CommonProgramFiles%\VST3. The extracted installer payload contains exactly the same signed VST3 as the separately distributed bundle.

SHA-256

NSIS
9462A4230F55CC527FA7EAAFCCA78323656EF45C0A564F6B6D70A2649C4B6E15
VST3 binary
7AA3B28DFB2DBD3DE81624D1781C8137F34D4BC51B7B08238CB696AE82A51AB8

Still stuck?

Contact support directly and we'll help you sort it out.