Plugin workflows
Audio plugin not showing in your DAW? Check these causes in order
A reversible troubleshooting workflow for missing AU and VST3 plugins, scan failures and format mismatches.
An absent browser entry, a failed validation entry and a plugin that opens with a licence overlay need different actions. Search the product and manufacturer in a blank project with browser filters cleared. If it loads there, inspect the original session’s expected format. If it opens locked, the host has already found it; rescanning is not activation.
By Spectraforge Audio3 min read
Published
Guide review: Captum Records and AS Mastering. AI-assisted writing and source checks. How these guides are made.
Identify absent, failed or locked before reinstalling
Check the build and expected location
Compare the developer’s requirements with the exact host, operating system and processor. Confirm the installed AU or VST3 format. A sample library or licence file is not the plugin binary. Use the official installer and note its version rather than changing several files at once.
VST3 has standard scan locations defined by Steinberg. For Silk, its manual lists /Library/Audio/Plug-Ins/Components/Silk.component and /Library/Audio/Plug-Ins/VST3/Silk.vst3 on macOS, and %CommonProgramFiles%\VST3\Spectraforge\Silk.vst3 on Windows. Check the expected file; do not copy a plugin into arbitrary DAW folders to make it appear.
Use the host’s scan controls and read its result
Close the host fully after installation, reopen it and allow the scan to finish. In Live, enable the relevant AU or VST3 source; if the normal scan fails to find the installed device, its documented Alt/Option rescan is a later step. In Logic, inspect the Plugin Manager’s active/validation state and use its documented rescan option.
If a validation error remains, capture the exact text. Check the developer’s compatibility advice before deleting caches or changing operating-system security settings. One complete scan and one clear error give support more useful evidence than several simultaneous reinstalls.
Suggested diagnosis: Silk is visible but sounds unchanged
Load it on a short source in a blank project, check the input meter and read any licence overlay. Silk 1.0.2 and 1.1.0 pass latency-aligned dry audio while locked; versions before 1.0.2 may mute. Import the valid signed offline licence through the plugin’s documented flow, then test processing and Bypass again.
Current purchase downloads include Silk 1.1.0. Check Information for your installed version. Keep a previous working installer and licence private if you need rollback. Do not publish a licence file or purchase key with a support screenshot.
Escalate with a compact reproducible report
Send official support the host and OS versions, product build, format, installed path and exact error. Say whether it is absent, fails validation, or opens locked, and whether the same thing happens in a blank project. List the restart/rescan actions already tried.
Once the device loads and processes a known source, return to the main project and compare its state against a saved reference. If only that project fails, troubleshoot its recall or routing; a successful installation does not automatically repair the project.
Technical references
- Ableton: missing plugins, compatibility and rescanning
- Steinberg: standard VST3 plugin locations
- Apple Logic Pro: Audio Units validation and the Plugin Manager
- Silk manual: installation and version-specific activation
Listening exercises are proposed practice routines. Worked examples illustrate the stated setup; they are not reports of our listening tests. Editorial process and corrections.