Pay attention to those who experience issues with Daw being blocked or encountering a black GUI. The issue lies in how the files are copied. The most crucial point is not to copy the Framework folder into System32, but rather its contents, the DLL files. Then, copy the contents of the !COMMONS folder into Commonfilesvst3; again, it's the content, not the folder. I spent hours on this yesterday, and the problem was because I was copying the entire folder. That's the crux of the matter—copying the content. Similarly, for VST3, place it in CommonfilesVST3, and do the same for VST2.

 

oh, that would definitely cause you a problem because you are adding the folder to the correct directory, which means that your folder structure becomes /correct folder/extra folder/files The way you were doing it is the "neat" way you usually do want to do stuff, instead of just dumping a mess into there. this whole thing is confusing as hell on mac too. We have multiple ways to do this; like Crossover, Crossgridder, Parallels Desktop, etc. I am sure there are more. Depending on the method, it could seriously impact whatever performance you will get. It's virtualization of everything to add at least one more layer of doom. At least you are not the only one. Did you get it working?

 

Having absolutely zero luck with this. i've managed to get the plugins to list in the browser (ableton), but when I drop an instance into a track it is just an empty header / dummy device that displays that it can't find the vst3. when I try and load the VST2 version (which I thought might be better / more straightforward) it crashes ableton immediately. I've done all of the steps potentially twice now. THe one thing I;'m still not sure about is what to do with the N2S & N2V. or do they also go in the containing plugin folder ?

 

clear instructions at page 2 - working perfectly in latest Ableton R2R!
N2S + N2V go into the same VST3 folder (better make a subfolder there with Acustica -> Subfolder *Name of plugin*)

 

I tried a few plugins and deleted the unnecessary sample rate files, like for 44K, 88K & 96K. It reduced the size with no problems so far. Only on Taupe it seems that 96K is important for authorization of two plugins of the bundle. Haven't try many though. So far I'm not impressed by the quality/resources ratio.

 

"I had the same issue as you, even though I use S1, but I imagine the problem must be the same. Two essential things you should keep in mind, as I mentioned before: the content of the Framework/Acusitca/(DLL files) folder should be placed (only the DLL files) in Windows/System32, I repeat, only the DLL files, not the folder. Then, the content of the !COMMONS folder goes into the VST3 folder of Common files. Only the content, not the entire !COMMONS folder. For example, in the !COMMONS folder, there is a folder named "AMBER," and within the "AMBER" folder, there is a subfolder called "AMBER3" along with .N2S files. Copy the AMBER3 folder and the .N2S files into Commonsfiles/VST3.

 

It has to be this because i tried first with the dlls not placed right and got the empty black plugin

 

Exactly, I experienced both of these issues. When the DLL files were in the correct directory, Windows/System32, but the content of !COMMONS was not, the DAW would close. However, when the DLL files were not correctly placed in System32, as you mentioned, the GUI appeared black or empty. I'll speculate now: This led me to think that, with the DLLs in System32, it was trying to locate the GUI in Commonsfiles/VST3, and if it wasn't found, it would close. So, I placed the DLLs from Framework in System32 and the contents of COMMONS in the VST3 folder of commonsfiles, and it worked.

I don't understand anything about programming; I just speculated with my reasoning by associating the 'why' the GUI wasn't appearing. If an expert in the field knows more about it, please let me know if the files in the !COMMONS folder, especially the .N2S files, are part of the GUI or play a role in it (intuition, speculation)

 

Good reasoning but it says to do this in the instructions.

Following the instructions is actually very easy and this doesnt take much time at all, but it need attention to detail like you said, when you have to put the contents of a folder somewhere, dont put the folder there, just the contents. Otherwise its trouble

 

Fire the pump is a only test for installing other? Because he ask me to authorize the plug in.

 

I don't understand I can only see the VST3 it works and when "Acqua" appears in VST2 when I try to launch the VST2 version I have the gray GUI which closes just as quickly with the DAW. However, I followed all the information indicated in the AstralDis comment

Ok I managed to open the vst2 in ableton without the gui crashing the software launches fine.

Copy files from vst2 to vst2 and also all files from !commons" inside the folders of the plugin in vst2

 

Last edited: Nov 27, 2023

I cannot set PATH in system enviroment for some reason, I tried going into advanced system settings and using cmd but the path I added when I restarts my PC disappears. I clicked edit in PATH for "system variables" and clicked new and typed in "C:\Program Files\Acustica\Framework" and then OK. Restarted my system and the path I added is gone.

When I try to open the plugin in Ableton it's just a small black window with no GUI, any help?

 

strange.. maybe try it once without restarting the PC!

edit: maybe this link can help.. they say that sometimes there are too many entries in *PATH* and you should try delete some others (if you can..)
https://superuser.com/questions/237268/missing-environment-variables-in-windows-7

 

Hey, can anyone tell me where exactly I can download the framework?

 

I thought I did it the right way like you showed in your screenshot but when I tried your steps the Firepump plugin shows in ableton but its just a black bar. Can you help me understand what I am doing wrong? These are the screenshots from what I thought was the right way but is failing.

 

@AstralDis
Please help i can't get Lemon to work ....Lemon loads up then it crash right before the loading is finished it keeps crashing in Studio one and Fl studio......but i got Firethepump working and it loads up just fine

 

I'm sure it works either way but I found out that editing the enviroment path in Windows 10 is not necessary. The simplest way is to manually create the folder C:\Program Files\Acustica\Framework

 

THANK YOU AstrolDis!!!!
This post should be sticky!!
I installed most of AA plugins and all are working smooth, except Fire The Pump that crashes ProTools 12.5 HD, but it's all right to me!

EDIT: Fire The Pump issue fixed. Now, all work fine!

 

Last edited: Jan 9, 2024

@AstralDis PLEASE HELP ME I'M STUCK!

I thought I did it the right way like you showed in your screenshot but when I tried your steps the Firepump plugin shows in ableton but its just a black bar. Can you help me understand what I am doing wrong? These are the screenshots from what I thought was the right way but is failing.