Support / Installation & activation
First-launch downloads — SURGE's bank and RAW's model
Two products fetch something on first use instead of shipping it in the installer. What gets downloaded, where it lands, and what to do if it stalls.
Why the installer is not the whole product
Two Nolvra products fetch a large file on first use rather than bundling it. SURGE downloads its sound bank; RAW downloads its de-reverb model. In both cases the download happens once, is verified against a published checksum, and is cached locally — after that the product works with no network at all.
SURGE's sound bank
SURGE's bank is a single container file holding the whole library. It is fetched on first launch, written to a temporary partial file, verified, and only then moved into place — so an interrupted download leaves nothing half-installed for the plugin to read.
If the download does not complete, SURGE tells you so and offers RETRY DOWNLOAD and OPEN HUB rather than opening onto an empty browser. Retrying resumes the same process; nothing is corrupted by a failed attempt.
RAW's de-reverb model
RAW's model is never downloaded silently or automatically. The plugin shows a DOWNLOAD MODEL button and the fetch starts when you press it — that is a deliberate rule, not an oversight.
While it runs, the progress figure is real: it is bytes actually written to disk, not an estimate against a timer. The speed and remaining-time readouts come from a smoothed measurement of the actual transfer, so if the connection stops, the speed genuinely falls to zero rather than pretending to advance.
Where the files land
- RAW model~/Library/Application Support/Nolvra/RAW/models/
- Nolvra support data~/Library/Application Support/Nolvra/
Checksums
Both downloads are verified after the fact. If the checksum does not match what was published, the file is rejected rather than used — a truncated or tampered file fails loudly instead of producing garbage audio later.
That also means a failed verification is not something you can work around by trying to reuse the partial file. Delete it and retry.
If a download stalls
Check that it is actually stalled
The plugin reports transfer speed honestly. A speed reading at zero for a sustained period means the connection has stopped, not that the plugin has.
Retry from the plugin
Use RETRY DOWNLOAD. A retry starts cleanly — the partial file is not reused.
Check a corporate or campus network
These downloads come from our CDN over standard HTTPS. Networks that inspect or block large binary downloads are the most common cause of a repeatedly failing fetch. A phone hotspot is a fast way to confirm whether that is what is happening.
Check free disk space
Both files are substantial. A download that fails at the same point every time on an otherwise working connection is usually a full disk.
Write to us
If it still will not complete, mail support@nolvra.com with the product, your macOS version and what the plugin showed. Do not send your license key.
Still stuck?
Nothing here matching? Write to a person.