Cueing up…

Skip to main content
Hardwave Workspace is liveHardwave Academy — join the waitlist
Back to Learn

Managing Hardwave Suite updates for multiple plugins

Managing Hardwave Suite updates for multiple plugins

Hardwave Pro users keep their plugins current through the Suite. The Suite checks the latest release tag for each plugin, compares it with the version recorded in its local registry, and offers an update when the two differ. The process works the same on Windows, macOS and Linux.

1. Open the Suite

Launch the Hardwave Suite application. The main view lists every installed plugin with its current version number. As of the latest release (2026-09-23) the stable versions are:

WettBoi - v0.4.5 Hardwave Analyser - v1.0.26 * Closed-beta Pro plugins (available only to Pro members) - KickForge v0.12.9, LoudLab v0.7.3, PumpControl v0.1.7, WideBoi v0.4.5

2. Check for updates

The Suite reads installed_versions.json and contacts the public releases repository to fetch the latest tag for each plugin. If installedVersions[slug] !== latest, the UI shows an Update button next to that plugin.

3. Download and install

When you click Update:

  1. The Suite downloads the binary from the GitHub release tag.
  2. On Windows it writes the VST3 file to the system VST3 folder; on macOS and Linux it writes to the per-user VST3 folder.
  3. The installer mirrors the build into the other standard location so any DAW scanning either folder will find the new file.

The install routine uses the Rust functions download_and_install, vst3_dir() and copy_dir_all (see the Suite source). After a successful copy, the Suite runs mark_installed to update installed_versions.json with the new version number.

4. Verify the update

Close and reopen your DAW, then run a plugin rescan. The DAW should list the updated version next to each plugin. You can also confirm the version inside the Suite's list - the number should match the latest release tag shown on the Hardwave GitHub page.

5. Updating closed-beta Pro plugins

Closed-beta plugins appear in the Suite only for Pro members. The update flow is identical to the released plugins: the Suite checks the beta channel for a newer tag, downloads the build, and installs it to the same system or per-user folder. Because they are not publicly released, the version numbers listed above are the current beta builds.

6. Troubleshooting common issues

Failed download - The Suite logs the error in sweep.log. Ensure your internet connection is active; the Suite needs to reach GitHub to fetch the latest tag. File in use - If a VST file is locked by a DAW, the Suite reports dl:cleaned and skips the overwrite. Close the DAW and retry the update. * Duplicate copies - The Suite's sweep routine removes non-standard copies after an update. If you have custom plugin folders, the Suite will leave those untouched but will not delete the active copy.

Following these steps keeps WettBoi, the free Hardwave Analyser, and any Pro-only beta plugins synchronized across Windows, macOS and Linux, reducing support tickets and ensuring a smooth production workflow.

Managing Hardwave Suite updates for multiple plugins | Hardwave Studios