Spectraforge Audio

Plugin workflows

AU vs VST3: which audio plugin format should you install?

Choose a format your DAW supports, keep project recall predictable and understand what plugin formats do and do not promise.

For Logic Pro, use the developer’s supported Audio Units build. For a Windows host that supports VST3, use its Windows VST3 build. In a macOS host supporting both, choose a supported format and keep that choice consistent for the same product within a project. AU and VST3 are communication formats, not sound-quality grades.

By Spectraforge Audio2 min read
Published

Guide review: Captum Records and AS Mastering. AI-assisted writing and source checks. How these guides are made.

Install the format your host and existing projects use

Check the exact host version, operating system and processor architecture. An AU cannot become a VST3 by renaming it, and one operating system’s binary is not another’s installer. Start with the developer’s supported installation route.

Prioritise recall over a speculative sound difference

A saved session identifies a particular plugin format and instance state. Installing AU does not guarantee that a missing VST3 instance will be replaced automatically with its settings and automation intact. Keep the original format available while preparing a migration.

The processing algorithm and settings determine the sound. A format comparison is uncontrolled if one instance uses a different preset, channel layout or quality mode. Before attributing a difference to AU versus VST3, check those details and consult the developer’s format-specific compatibility notes.

Suggested exchange test: one sound, one automated parameter

For a collaboration using a host available on Mac and Windows, agree a shared format and product version. Create a small project with a rendered source, one plugin instance and an obvious automated change. Include a clean audio reference of the result.

Open a copy on the other machine. Confirm that the expected instance loads, its parameter values match, the automation reaches the intended control and the result agrees with the reference. A successful scan alone does not test recall. If the exchange fails, fix that example before sending a large session; print essential processed parts if the plugin cannot transfer reliably.

Keep a record of the working setup

Write down host version, operating system, product version and format alongside important projects. Retain reference renders and the required installer where its licence allows. For an existing session, a missing format is first a compatibility or installation question; random format changes can make recall harder to diagnose.

When a plugin is visible but opens locked, follow its activation instructions. When it is absent or fails validation, use the missing-plugin guide. Distinguishing those states will get you to a usable instance faster than repeating the installation without knowing what failed.

Technical references

Listening exercises are proposed practice routines. Worked examples illustrate the stated setup; they are not reports of our listening tests. Editorial process and corrections.

Help

Spectraforge Audio support

Send us a message and we’ll reply by email. Zoho Desk handles your message and any attachments. Privacy policy

Form not loading? Email info@spectraforgeaudio.com.

Your privacy choices

With your permission, Google Analytics measures site use and Meta measures advertising performance. Both are optional. Privacy policy

Privacy settings

Choose which optional tools can run. Your purchases and licence access work with both turned off.