Support / Installation & activation
Installing PRISM PRO
PRISM PRO installs through the Nolvra Hub, into your home folder on a Mac and into Program Files on Windows. What it runs on, and where the files go.
One installer, no password
PRISM PRO is delivered by the Nolvra Hub, the free app that holds your account, your licenses and your downloads. The Hub fetches the signed and notarised package and runs it. On a Mac the package installs into your home folder, so it never asks for an admin password and never shows you a destination picker. On Windows it writes the VST3 to C:\Program Files\Common Files\VST3, which is a system location, so Windows asks for permission once. PRISM PRO is this plugin's name from version 1.2.2 on; it was called PRISM up to that release, so an older install still reads Nolvra PRISM in your plugin browser. The bundle identifier did not change with the name, so a saved project finds it either way.
From a fresh machine to a plugin in your DAW
Install the Hub and sign in
Download the Nolvra Hub from nolvra.com and sign in with your email address. There is no password: you get a six-digit code by email and enter it. The same sign-in works on the site and in the Hub.
Install PRISM PRO from the Hub
PRISM PRO appears in the Hub's product list once your account can open it, either through an All-Access membership or through a purchased license. Press install and the Hub does the rest.
Let your DAW find it
Most hosts pick up a new plugin on their next launch. Logic scans Audio Units when it starts. Live rescans when you open it or when you press Rescan in Preferences. FL Studio does not scan on its own: open Plugin Manager and press Find installed plugins, or PRISM PRO will not be in the list.
Open it on the vocal track
PRISM PRO is an audio effect, not an instrument. It goes on the track that already carries your voice. The quickstart article covers the first sound.
What it runs on
- FormatsAU/VST3 (macOS) · VST3 (Windows)
- macOS11 or later
- ArchitectureApple Silicon
- Windows64-bit, VST3
- InstallerNolvra Hub
Why the macOS row says 11, and where 14 comes in
PRISM PRO states macOS 11 or later, and that is the plugin's own baseline. It can be, because for this product the plugin is a thing you can hold on its own: it is licensed, the plugin takes your license key directly, and a Mac on 11, 12 or 13 runs it with the package installed by hand.
The Nolvra Hub is the easy route and the Hub needs macOS 14. If the Hub is how you install, 14 is the number that decides it for you, and that is the row printed next to the Hub download rather than here.
PRISM MINI is the opposite case, and its row says 14 for that reason. It has no license key and no activation field, so the Hub is its only door and the Hub's floor becomes the product's floor. RAW's row reads 14 for a third reason, its own: it carries a runtime that needs 14. A product's effective baseline is the highest baseline of everything its chain contains, and which parts are in the chain is a different answer for each of the three.
Where the files land
On a Mac the AU goes to Library/Audio/Plug-Ins/Components and the VST3 to Library/Audio/Plug-Ins/VST3, both inside your home folder rather than the system one. That is what makes the admin password unnecessary, and it is also why an installation belongs to the account that ran it: another user account on the same Mac has its own plugin folders and will not see PRISM PRO.
On Windows there is no AU and no home folder copy. The installer writes the VST3 to C:\Program Files\Common Files\VST3 and does not show you a destination picker. That is the standard VST3 location and every Windows host scans it. Because it sits in a system location rather than inside your account, Windows asks for permission once while the installer writes. If your host also scans a custom folder, point it at that path or copy the plugin across.
Windows
PRISM PRO runs on Windows as VST3. The Hub installs it there the same way it does on a Mac, the license is the same license and the two machine limit is the same limit. The one real difference is the format: Audio Units are an Apple format, so Windows has VST3 only. The installer places the VST3 in C:\Program Files\Common Files\VST3, the standard location every Windows host scans.
Updates
Updates arrive through the Hub, the same way the first install did. Nothing in the plugin phones home for a new version and nothing installs itself behind you. If a session is open when an update lands, finish the session first: replacing a plugin binary under a running host is how you lose a take.
Still stuck?
Nothing here matching? Write to a person.