@AstralDis my file structure looks identical to yours but I keep getting a black bar when loading the plugins in ableton, fl studio and studio one. Can you please help me ? I followed your steps one by one and I am still getting a black bar. PLEASE HELP !

 

Last edited by a moderator: Jan 15, 2024

I'm getting the "Please authorize this product" message, anyone experienced the same?

 

I'm confused,

So i've created the file

C:/program files/common files/vst3/Acustica/FIRETHEPUMP with all the required files in the correct directory

What I'm confused about is... what exactly are the "framework" files? where do i find them?

and also how do i find w_dpcpp_cpp_runtime_p_2024.0.0.49848 from R2R? I don't think i have this file?

please excuse my dumb ass I'm just a producer

 

Just in case i need to know for future reference... How does one uninstall the R2R framework + R2R plugins if they need to switch back to legit? What are the steps & folders?

 

I used Acustica Audio Nebula3 back in 2007 when they first came out, supported them - bought the plugin, I think it was 60 bucks back then. Had to download large libraries and.. in the end it just wasnt worth it but it had potential. Then Giancarlo did me dirty.. Im glad I was able to test all their plugs ins.. and I am happy to say, they STILL arent worth it. Deleted. With modern plugins, there is absolutely no need for this rubbish.

Who the hell wants to install these huge, slow, latent monsters to try and replicate 80 year old obsolete hardware units? Idiots, thats who.

 

Trying to help m8's.
I noticed most of you didn't place folders & files in the right place!
Inside each plugin folder put the files like you see in graphic 2

 

Just resurrecting this post because it was helpful and will solve a lot of people's problems here:

 

The last post was the solution!

 

Last edited: Sep 6, 2024

I wanted to link the original message! This one is just too good, such an instruction was exactly what I was looking for and it deserves a "best answer" mark. It should be pinned also for future searchers. Thank you again so much my man, you saved me and made my day! It's so great to have a forum and people like this, without you one would be lost. I copied it and saved it for the future. It does work now. R2R should really supply an instruction like this with all their packages. Also, the paths as referenced in this thread need to be the correct ones, there's two screenshots that show the correct ones.

 

Copy contents of Framework-Official folder to C:\Windows\System32

 

I have done everything following @AstralDis instructions but Wavelab cannot load Jade plugin at all and with Patchwork I get a black GUI.
I have not copied the files from "\Framework-Official\Acustica" to System32 because I don't want to overwrite the existing files here to mess up my system. I have copied them to "C:\Program Files\Acustica\Framework" using the "Acustica" way from the NFO.

I have a line on my system variables with "C:\Program Files\Acustica\Framework". And copied the content of !COMMON and VST3 to my created AA VST3 folder. What am I doing wrong ?

EDIT: I'm a dumbo, I previously added the environment variable by adding a new line in System variables. I added the line "C:\Program Files\Acustica\Framework" to the PATH entry and now everything is working okay.

 

Last edited: Jan 23, 2025

Hey guys,

maybe this is useful to somebody thinking about symlinking the acustica audio plugins.

I am using VST3 with FL Studio and here is what I did:

At the path: C:\Program Files\Common Files\VST3 I made the folder Acustica Audio.
Inside the Acustica Audio folder (C:\Program Files\Common Files\VST3\Acustica Audio) I made a folder for each plugin I wanted to install.

Looking at the downloaded files inside the !COMMON folder you see a folder of the plugin's name written in capslock.
I copied that exact name and made a new folder at C:\Program Files\Common Files\VST3\Acustica Audio.

So as an example looking at Amber 3 I now have this path:

C:\Program Files\Common Files\VST3\Acustica Audio\AMBER3

At this path I then copied all contents of the !COMMON folder and the VST3 folder.
Meaning I would have all the Amber 3 related N2V files at this path: C:\Program Files\Common Files\VST3\Acustica Audio\AMBER3\AMBER3
And all the .vst3 folders at C:\Program Files\Common Files\VST3\Acustica Audio\AMBER3\

I did this for all plugins I wanted to try which comes up to quite a lot of gigabytes.

After that I made a powershell script symlinking the N2V containing folder (the second AMBER3 of the path) to another drive's location.
The powershell script checks the initial folder if it contains a subfolder with the identical name (which is true), then it moves this exact subfolder to the location written in the powershell script and after that creates a symlink at the location where the subfolder was.
At C:\Program Files\Common Files\VST3\Acustica Audio\AMBER3\ now contains a symlink to the AMBER3 .N2V files folder.

The script batch processes every plugin in the Acustica Audio folder automatically.
Most annoying is the initial folder creation which I did manually but might be automateable too somehow.

I put the script at the location: C:\Program Files\Common Files\VST3\Acustica Audio.
So you open up powershell, use cd to move to the location containing the .ps1 script file.
The script comes in "dryRun" mode which means you first are able to see what it does before it actually executes.
For it to do the processing you need to edit the 2nd line setting it from: $dryRun = $true
to: $dryRun = $false.


You execute the script using the following commands:

Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass
.\acustica_symlink.ps1


Here is the actual code of the powershell script:


# TRUE = only shows what would happen | FALSE = actually performs the actions
$dryRun = $true

# Source and target directories
$sourceBase = "C:\Program Files\Common Files\VST3\Acustica Audio"
$targetBase = "I:\VST\Acustica Audio"

# Create target directory (only in real execution mode)
if (-not $dryRun -and -not (Test-Path $targetBase)) {
New-Item -Path $targetBase -ItemType Directory | Out-Null
}

Write-Host ""
Write-Host "=== Starting Script (Dry-Run: $dryRun) ===`n"

# Loop through all top-level folders in the source directory
Get-ChildItem -Path $sourceBase -Directory | ForEach-Object {
$outerFolder = $_.Name
$outerPath = $_.FullName
$innerPath = Join-Path $outerPath $outerFolder
$targetPath = Join-Path $targetBase $outerFolder

if (Test-Path $innerPath -PathType Container) {
if ($dryRun) {
Write-Host "[$outerFolder] → WOULD move: $innerPath → $targetPath"
Write-Host "[$outerFolder] → WOULD create symlink: $innerPath → $targetPath`n"
} else {
try {
Write-Host "[$outerFolder] → Moving: $innerPath → $targetPath"
Move-Item -Path $innerPath -Destination $targetPath -Force

Write-Host "[$outerFolder] → Creating symlink: $innerPath → $targetPath"
cmd /c mklink /D "`"$innerPath`"" "`"$targetPath`"" | Out-Null
} catch {
Write-Warning "[$outerFolder] ❌ Error: $_"
}
}
} else {
Write-Host "[$outerFolder] ⚠ No matching subfolder found – skipped.`n"
}
}

Write-Host ""
if ($dryRun) {
Write-Host " Dry run completed. No changes were made.`n"
} else {
Write-Host "✔️ Done! All matching subfolders were moved and symlinked.`n"
}

Pause