An Acustica commercial license carries five authorization slots, runs on two computers at once, and cannot be authorized offline at all. Those are not the specifications anyone reads before buying. They are the ones that decide whether your plugin works on the morning of a deadline.
Acqua is a platform rather than a plugin you drop into a folder. Everything installs, updates, and authorizes through Acustica's own desktop manager, and the manager has opinions.
None of this is a reason to avoid the plugins. It is a reason to spend twenty minutes on setup before you spend three hours wondering why a session loads slowly.
That gap catches people constantly, because 48 kHz is the most common working rate in the world. If the matching pack is not installed, your host asks the plugin to convert its files to the session rate instead. Load times get slower, and the result is less accurate.
This follows directly from how these things are built. Acustica's sampled model of the BAX hardware stores stores measured vectors rather than filter coefficients. Those vectors are tied to the rate they were captured at, so conversion on the fly is a compromise rather than a feature.
So check your frequency packs against the rate you actually work at, and install them before the session rather than during it. The manager lets you queue several products and formats at once, which makes setting up a new machine less tedious than it looks. While you are in there, leave the files it created alone. Deleting them breaks the product.
The two-computer rule is the one that bites. You can run a product on two machines at once, and going beyond that means requesting extra slots or paying for them. Free grants exist if you can show the previous slots were not used abusively, and approved slots land within seven working days.
Authorization is bound to your computer's identification code, so external and portable drives cannot hold one. Uninstalling de-authorizes automatically, and you can also de-authorize by hand to free a slot without removing anything.
Do that deliberately before you rebuild or sell a machine. Also remember that there is no offline mode, and subscriptions need to reach the internet every thirty days. If your mastering room is air-gapped, sort the authorization somewhere else first.
Zero-latency instances remove those buffers. You get immediate response, which matters when you are tracking through the plugin, and you pay for it in CPU. There is a high-latency variant that runs the trade in the opposite direction, adding delay to reduce load.
Buffer settings in your host matter just as much. Acustica suggests 1024 samples or higher for mixing and mastering work, because small buffers raise CPU load and hurt stability at the same time. Save the small buffers for tracking sessions.
Instance count is the other lever, and it is the one you control. Thirty of these across individual channels will hurt any machine, while two on a bus and one on the master will not. Treat them as finishing tools, and the performance question mostly disappears.
Hardware choices are less obvious than people assume. For this kind of work, the speed of each core matters more than the number of cores you have. The newest engines can use AVX512 instructions where your processor supports them.
One quirk is worth knowing if your DAW struggles. Since the seventh generation of the engine, multithreading happens outside the host application, and some hosts handle that badly. A plugin adapter such as PatchWork or Metaplugin takes the scheduling out of the host's hands. It is a strange fix that works often enough to try.
Acqua is a platform rather than a plugin you drop into a folder. Everything installs, updates, and authorizes through Acustica's own desktop manager, and the manager has opinions.
None of this is a reason to avoid the plugins. It is a reason to spend twenty minutes on setup before you spend three hours wondering why a session loads slowly.
Your session rate decides which files get loaded
Acqua products ship support for four sample rates, at 44.1, 48, 88.2, and 96 kHz. The base installation typically includes 44.1 and 96 kHz. The other two arrive as separate frequency pack downloads through the manager.That gap catches people constantly, because 48 kHz is the most common working rate in the world. If the matching pack is not installed, your host asks the plugin to convert its files to the session rate instead. Load times get slower, and the result is less accurate.
This follows directly from how these things are built. Acustica's sampled model of the BAX hardware stores stores measured vectors rather than filter coefficients. Those vectors are tied to the rate they were captured at, so conversion on the fly is a compromise rather than a feature.
So check your frequency packs against the rate you actually work at, and install them before the session rather than during it. The manager lets you queue several products and formats at once, which makes setting up a new machine less tedious than it looks. While you are in there, leave the files it created alone. Deleting them breaks the product.
Five slots, two machines, and no offline option
A commercial product gives you five authorization slots. A trial gives you three, and they are time-limited. Free products skip the protection system entirely but still install through the manager.The two-computer rule is the one that bites. You can run a product on two machines at once, and going beyond that means requesting extra slots or paying for them. Free grants exist if you can show the previous slots were not used abusively, and approved slots land within seven working days.
Authorization is bound to your computer's identification code, so external and portable drives cannot hold one. Uninstalling de-authorizes automatically, and you can also de-authorize by hand to free a slot without removing anything.
Do that deliberately before you rebuild or sell a machine. Also remember that there is no offline mode, and subscriptions need to reach the internet every thirty days. If your mastering room is air-gapped, sort the authorization somewhere else first.
Buffer size and instance type set the CPU bill
The standard instance is not the slow one. It runs internal buffers, and that buffering is exactly what keeps the processing load manageable. The buffered standard instance is what you want for mixing and mastering.Zero-latency instances remove those buffers. You get immediate response, which matters when you are tracking through the plugin, and you pay for it in CPU. There is a high-latency variant that runs the trade in the opposite direction, adding delay to reduce load.
Buffer settings in your host matter just as much. Acustica suggests 1024 samples or higher for mixing and mastering work, because small buffers raise CPU load and hurt stability at the same time. Save the small buffers for tracking sessions.
Instance count is the other lever, and it is the one you control. Thirty of these across individual channels will hurt any machine, while two on a bus and one on the master will not. Treat them as finishing tools, and the performance question mostly disappears.
Hardware choices are less obvious than people assume. For this kind of work, the speed of each core matters more than the number of cores you have. The newest engines can use AVX512 instructions where your processor supports them.
One quirk is worth knowing if your DAW struggles. Since the seventh generation of the engine, multithreading happens outside the host application, and some hosts handle that badly. A plugin adapter such as PatchWork or Metaplugin takes the scheduling out of the host's hands. It is a strange fix that works often enough to try.
