SUPPORT
Get help.
Answers, troubleshooting, and specs for ANVIL and FETCH.
Below you'll find complete system specifications for both ANVIL and FETCH, along with common troubleshooting steps for the most frequent issues users encounter. We've also included a comprehensive FAQ covering everything from DAW compatibility and installation to advanced features like pad linking, NAM integration, and the Leftover Scraper. If you don't find your answer here, you can reach out directly using the contact form at the bottom of this page.
CUSTOMER PORTAL
Manage your account.
Access your orders, license keys, and billing through Lemon Squeezy.
AT A GLANCE
Quick specs.
ANVIL
FORMAT
VST3 · Standalone
PLATFORM
Windows 10/11 · 64-bit
CPU
x64, SSE2 or higher
RAM
4 GB min · 8 GB recommended
PADS
16 velocity-sensitive
OUTPUT BUSES
8 stereo (Main + Aux 1–7)
POLYPHONY
32 simultaneous voices
SAMPLES
WAV, AIFF, FLAC, MP3
LICENSE
Proprietary
FETCH
PLATFORM
Windows 10+ · 64-bit
FORMATS
VST2, VST3, AAX, CLAP
ENTRIES
Unlimited plugins
THEMES
Dark, Light, 6 color accents
SCALE
50%–200% in 5% steps
DEPENDENCIES
None, fully bundled
STACK
Electron 30 · React 18
LICENSE
Proprietary
TROUBLESHOOTING
Common issues.
Verify the .vst3 file is in C:\Program Files\Common Files\VST3\, confirm your DAW is 64-bit, and rescan. ANVIL is fully self-contained and needs no Visual C++ Redistributable or other runtime.
Verify the .vst3 file is in C:\Program Files\Common Files\VST3\. Confirm your DAW is 64-bit. If your DAW scans a custom plugin directory, add that directory to your scan path and rescan.
Increase the buffer size in your DAW settings. Reduce the number of simultaneous NAM models running on different pads, since NAM processing is CPU-intensive. Lower polyphony if needed.
Go to Settings → Scan Paths. Add your VST directories (common paths: C:\Program Files\VSTPlugins, C:\Program Files\Common Files\VST3, C:\Program Files\Steinberg\VSTPlugins). Click Scan and wait for completion.
Review each found file individually. Nothing is deleted without your explicit confirmation. If a file is important, uncheck it before proceeding.
Verify write permissions on the original plugin directory. If restoring to a protected location (Program Files), run FETCH as Administrator.
FAQ
Common questions.
Any VST3-compatible host, including Ableton Live, Bitwig Studio, Reaper, Fender Studio Pro and Cubase. Tested directly in FL Studio, Ableton Live, Bitwig Studio, Reaper 7.73 and Serato Studio. ANVIL is not locked to any specific DAW.
No. ANVIL is Windows only (x64). Mac and Linux support is not currently planned.
Verify the .vst3 file is in C:\Program Files\Common Files\VST3\ and that your DAW has rescanned its plugin folders. ANVIL is fully self-contained and needs no Visual C++ Redistributable or other runtime, so a missing dependency is not the cause.
WAV (16-bit, 24-bit, 32-bit float), AIFF, and FLAC. Samples are automatically resampled to your host's sample rate on load. Mono files load correctly into stereo pad chains.
Pad linking assigns one pad to simultaneously trigger another, so both fire at once. Each pad keeps its own sample, volume, pitch, and full FX chain. They output to separate DAW channels and are independently mixable. Velocity layering (one pad, multiple samples based on velocity) is a completely different concept. Pad linking is about simultaneous, independent triggers.
No. Output routing is stored in your DAW project file, not in kit files. You can swap kits freely without affecting how pads route to your mixer. This keeps kits portable across different setups.
NAM (Neural Amp Modeler) lets you load neural network models of real guitar and bass amplifiers. In ANVIL, you can run individual pads or the entire master bus through a NAM model to add amp character to your drums. Any .nam model file works.
8 stereo outputs: Main + Aux 1–7. Set each pad's output assignment in the plugin, then configure your DAW mixer to receive the separate channels. Routing is stored in your DAW project.
Fetch supports VST2 (.dll), VST3 (.vst3), AAX (.aaxplugin), and CLAP (.clap) formats. You can configure custom scan paths for each format independently.
After uninstalling a plugin, the Leftover Scraper searches the preset and data folders of 13 hosts and audio applications for orphaned files the uninstaller missed: presets, cached database entries, and empty vendor folders. Every file it finds is shown to you before anything is removed.
No. Nothing is removed without your confirmation. The uninstall flow asks at every step, and the Leftover Scraper shows you each file it finds and waits for your approval. Anything removed goes to Quarantine, which moves files rather than deleting them, so you can restore them at any time. You can also back a plugin up yourself before removing it.
FETCH is DAW-agnostic. It scans the file system rather than a specific DAW, so if your software loads VST2, VST3, AAX or CLAP plugins, FETCH can scan, organise, back up and uninstall them, whatever you produce in. For leftover cleanup it additionally knows the preset and data folders of 13 hosts and audio applications: FL Studio, Ableton Live, Cubase, Nuendo, Fender Studio Pro, Bitwig Studio, Reason, Pro Tools, Universal Audio LUNA, Reaper, Cakewalk, Audacity and Sound Forge, plus shared VST cache locations.
Yes. Quarantined plugins are moved to an isolated folder, not deleted. Open the Quarantine panel, select the plugin, and click Restore. It will be placed back at its original path.
Backups are stored in a configurable directory (default: AppData). Each backup is timestamped and labeled by plugin name. You can set per-plugin retention limits and browse or restore backups from the Backup panel.
CHANGELOG
What's changed.
ANVIL
v1.0.0
May 2026
- Initial release
FETCH
v1.0.0
May 2026
- Initial release
Still stuck?
Send us a message and include your product name, Windows version, and steps to reproduce the issue.
Email Support