I just can't find the Fire The Pump plugin in Studio One....

I have no idea if I did something wrong when installing the framework or when installing the plugin.
I am running on Windows 10.

Could someone explain to me exactly what I need to do to understand what I have done wrong?

I made a Folder in Appdata with Make_APPDATA_Acustica_Dir by R2R .
This Folder Exist and its Empty .


I have installed w_dpcpp_cpp_runtime_p_2024.0.0.49848 from R2R


I have copied The Files in the Folder : Acustica.Audio.Framework.2023.READ.NFO-R2R\Framework-R2R\Acustica\Framework to C:\Windows\System32



And i have made a new VST Folder on my C Drive for Acustica Audio Plugins that looks like this :


And i have Installed Microsoft Visual C++ Redistributable (2015-2022) x64 from here :
https://learn.microsoft.com/de-de/cpp/windows/latest-supported-vc-redist?view=msvc-170

in Studio one i have set this Folder as a VST Folder but i cant find the FIRETHEPUMP Plugin

 

Studio One does not support custom locations for VST3 afaik. Try to use VST2 plugin or put VST3 files under C:\Program Files\Common Files\VST3

 

Thank you very much Guys ! The Plugin works !

is there a method to get the other plugins from Acustica or do we have to wait for the R2R releases ?

There seems to be a discussion and somehow I'm a bit confused about it.

On the sister page under the post of the framework release someone says

Maybe these links will be handy once the hundreds of plugins pop up :

LINK :Acqua Reccomendations plugins

LINK: Acqua plugins guide

Another one : Might be a stupid question but apart from the Fire the Pump plugin, where do we get the other plugins?
Answer : Within the framework post.

 

I think the rest of the plugins will be released soon. R2R just releasing the Framework and one plugin to see if everything working nicely for everyone. If they just drop everything + framework, it will get confusing real quick because the installation isn't really straight forward.

So what we do for now, install the Framework, install Fire The Pump and give feedback, is it working, is it not, or any problem regarding the installation. Then we wait for other plugins to be released. I think the releasers are packing them up as we speak. It's 100+ plugins according to the NFO. Even uploading them will take time knowing Acustica's plugin is huge in size, some up to 3GB for just one set of plugins. It's going to take some time.

Those links above are important, keep them, bookmark and read them.

 

Last edited: Nov 20, 2023

Make sure you add the PATH to Environment Variables.

On Windows 11 (sorry I don't know 10) type in the search box (or on the Windows button) env. This should bring up the option to open edit environment variables. In the top part, click on PATH and select Edit. Next click New and put the C:\Program Files\Acustica\Framework path in there. Click OK and OK again on the other window. Reboot (maybe not necessary) and try loading your DAW again.

 

ive followed all the steps to install the plugin but when i load it all i see is a black bar any help please?

 

@KUSHSMOKERLIT
Not who you quoted but perhaps I can answer as I had this when I originally set it up...I didn't have the Framework-Official\Acustica\Framework files in System 32 and the plugin came up as a black bar. So double check that you didn't miss that step.

 

ive copied the acustica folder to the system 32 folder and i still get a black bar when loading the plugin : (

 

Don't put the folder there, put the contents of the folder there.

 

It's working thank you so much

 

crazy

 

i have a msg PLEASE AUTORIZE THIS PRODUCT
(solved) i was putting files in root of comnmon folder

 

Last edited: Nov 20, 2023

Sadly for me using Reaper 7, when I load any of the plugin files (specifically for Amber) it crashes the DAW. . It used to show a black bar but I just needed to restart to fix that issue.

 

do the work in a diferent daw?

 

Just tried loading in plugin doctor outside of host and the same thing happens.

 

I suggest everyone make a copy of this thread, so when others ask questions about setting up? there aren't loads spread all over the place!

 

Just tested The Pump and it crashed the same way. I see a grey rack looking plate for the GUI, it hangs, and dies.

 

you copied wrong
copy the vst2 OR 3 content to folder commons
means
besides the folder named FIRETHEPUMP
for Fire The Pump (looks different for different plugs)
there now should be 6 entries visible
FIRETHEPUMP folder
2 xml
2 dll
1 n2s

copy the complete Folder you are in now,(rename it from commons to Fire The Pump)
into your plugin directory
Done!

 

Last edited: Nov 20, 2023

Did you try Simlinking with "mklink /D" to another path?
I would be interested to know if this works for the !COMMON files.

 

Last edited: Nov 20, 2023