Support
Installation & help
Every StarVerb Audio plug-in ships as a ZIP holding the 64-bit VST3 bundle, and they all install the same way: unzip it, copy one folder. Anything not covered here, write to starverbaudio.support@gmail.com.
Installing on Windows
Close your DAW
A plug-in file that is currently loaded cannot be replaced. Close the DAW before you copy anything, or Windows will refuse.
Unzip the download
Right-click the .zip → Extract all. Inside there is a folder named after the plug-in — for example PixelVerb-sa.vst3 — plus the licence and a LEGGIMI-README.txt with these same instructions in English and Italian.
Copy that folder into your VST3 folder
Copy the whole .vst3 folder — not just the file inside it — into C:\Program Files\Common Files\VST3. Windows will ask for administrator permission: that is the ordinary prompt for a system folder, not a security warning. Click Yes.
Rescan in your DAW
Reopen your DAW and rescan plug-ins. In Ableton Live: Preferences → Plug-Ins → Rescan (hold Alt while clicking for a full rescan).
Each plug-in is one folder in your VST3 folder — by default C:\Program Files\Common Files\VST3, so PixelVerb-sa lands as PixelVerb-sa.vst3. That is the whole installation: nothing goes anywhere else, and there is no uninstaller to run. Presets you save yourself go under your Documents folder, in Documents\StarVerb Audio.
Frequently asked
What are the system requirements?
Windows 64-bit and any DAW that supports the VST3 format. The plug-in is 64-bit only.
Which DAWs are supported?
Ableton Live, FL Studio, Cubase, Studio One, REAPER, Bitwig — and any other host that loads VST3 plug-ins.
Do you offer VST2, AAX or a macOS version?
Not at the moment. The current release is VST3 for Windows only — no VST2, and no AAX for Pro Tools. Write to us if you need a specific format; it helps us prioritise.
Why a ZIP and not an installer?
An installer is a program, and a new program nobody has code-signed yet puts Windows on alert: sometimes it warns you, sometimes it quarantines the file on its own — even when there is nothing wrong inside. A ZIP with only the plug-in in it contains nothing that runs, so no warning appears at all. It costs you copying one folder. Code signing is on the list; when it is in place the installer comes back.
My DAW does not see the plug-in. What now?
First, rescan your plug-ins (in Ableton Live: Preferences → Plug-Ins → Rescan, Alt+click for a full rescan). If it still does not appear: check that you copied the whole .vst3 folder and not only the file inside it, that your DAW scans the folder you copied it into — by default C:\Program Files\Common Files\VST3 — and that you are using the 64-bit version of your DAW.
Why does it ask for administrator rights?
The standard VST3 folder lives inside Program Files, which Windows protects, so copying anything into it needs elevation. It is the same prompt you get for any file you put there, and nothing else on your system is touched: no other folders, no registry keys.
Can I put it somewhere else?
Yes. Copy the .vst3 folder into any folder your DAW scans for VST3 plug-ins — the standard one is simply the folder every host already looks at. Some DAWs let you add your own.
How do I uninstall one?
Close your DAW and delete that plug-in’s .vst3 folder from your VST3 folder. There is nothing else to remove, and each plug-in is independent: removing one leaves the others untouched. Your own presets live in your Documents folder and stay there.
How do updates work?
The plug-in checks once a day whether a newer version is available and lets you know inside your DAW. No personal data is sent — see the Privacy Policy for details. To update: close your DAW, download the new ZIP, and copy the .vst3 folder over the old one, replacing it. There is nothing to uninstall first.