I had Nebula 4.2 (shared) installed since before R2R released Acqua's, so that was already on my system. When I installed the framework for R2R's Acqua I did not do the 'easy' method, do the other method. This is how I've installed it and both are working together. I'm not sure if it's Neb 4.2 specifically or the order of Nebula first then R2R Acqua that allows it. I do theorize that doing the easy method overrides the Nebula framework so be weary of that. I fiddled with more Nebula installs today for around an hour now and I'm not sure I'm going to bother going up to 4.5 bc I'm not even sure what the benefit is for the libraries I'm using.

 

I'll have to look that "other" method up. To be honest I ended up installing the R2R aqua framework stuff from a guide provided in a thread on here somewhere. In the interim just for giggles, are your R2R aqua Framework files installed at c:\program files\acustica\framework\ or another dir?

 

you guys should share with the world the updated files as the ones provided by the witches are from the trial versions, I could help if someone figure which files to share...

 

After a lot of debating on which nebula version to install I finally decided on 4.5. The R2R acqua framework was already installed and working for months. In reading over the install "instructions" for Nebula 4.5 there didn't seem to be anything intrusive to the acqua framework being called out so went ahead with the install for Nebula 4.5.

After the nebula 4.5 install, the base Nebula VST, VST3, and AAX plugins were working in all my DAW's (Reaper, Cubase, Nuendo, and ProTools). At this point I decided to install a couple of the Nebula devices (namely the TP Vari-level STA and the Lexicon 480L). Ran a few tracks as a test and had the R2R Acqua Ocean processor and the Nebula Lexicon 480L running together with no issues at all. Seems Nebula 4.5 and R2R Acqua stuff will coexist just fine. From what I have seen you shouldn't have any issues with upgrading your setup to 4.5 if you wanted...

 

Last edited: May 8, 2025

right on, so nebula 4.5 and r2r acqua are working together on your system now?

 

Yep. Both R2R Acqua and Nebula 4.5 working fine and able to be used together - I had the R2R Acqua Ocean processor and the Nebula Lexicon 480L running together on a stereo test track.

One thing I haven't tried yet is installing a V3 Nebula library and running it with v4.5... You don't happen to know if Nebula v4.5 is capable of running V3 lib's?

 

Last edited: May 8, 2025

Very cool, thanks for reporting back. Yes 4.5 should have no problem loading V3's.

 

Hello All!

I recently D/L Nebula 4.5 (Sister Site), and Cupwise CupTone vol. 3 Tone Distortion. I follow the included instructions on where to place each file. The library loads from the 'Finder' window, but has limited funtionality (Sound plays, but buttons don't work).

When trying to save using the N4 'Settings' menu for the 'Cupwise CupTone vol. 3' library, I am met with this warning: 'Error Opening N4 VST Configuration File'. Why is this?

Also, there is a set of files that came with the Cupwise CupTone vol. 3 plugin that don't specify the Windows location for this set of files inside the included 'Nebula-Configs' folder.

Cuptone3-dyn-44khz

Cuptone3-dyn-48khz

Cuptone3-dyn-88khz

Cuptone3-dyn-96khz

Cuptone3-main-44khz

Cuptone3-main-48khz

Cuptone3-main-88khz

Cuptone3-main-96khz

^No clear definition on where these files get placed in the C:\nebula4temprepository folder.

*More questions:

1. Where is N4 Directory location? (Windows)

2. Where is N4 Setups directory location? (Windows)

Any help/tutorial/links on these matters would be greatly appreciated.

Thanks In Advance!!!

Sorry if I seem repetitive.

 

That error means your library isn’t installed or configured correctly. If you hear sound but all the sliders/buttons snap back, that’s always a library problem, not the plugin. Nebula can’t access the parameter files. Just check every slider, because sometimes they are not all going to do anything but snap back.

 

Oh... I'm still on Nebula 3 and thought about upgrading.
So it's not gonna be easy-peasy.
Maybe I wait another year or two
(how time becomes relative when one is an old fuck...)

 

How can I configure it correctly? Is there a guide or tutorial for this?

Is there a way to get Nebula to access paremeter files?

Cupwise CupTone vol. 3 Tone Distortion does have some knobs that work, and some knobs snap back...dam.

Is that the normal behavior of these libs, features may/may not work?

More Questions:

*The set of 'DYN' files inside the Skins>Nebula-Configs folder does not provide a placement location. I'm thinking these not-installed files may have something to do with functionality of this lib also. any idea where they belong?

2. Where is the correct N4 Directory location? Settings asks for path.

3. Where is N4 correct Setups directory location? Settings asks for path.

4. Where is the correct N4 VST Configuration File location/path? Settings says there is an "Error Opening the N4 VST Configuration File".

*I know I'm repeating myself, but I need literal answers to my literal questions for full personal clarification. Your reply, while helpful, is also very vague...no disrespect intended. I do Thank You Clone for your time/energy to help shed light on the issue.

 

The are two guides included with that package. One for the plugin installation and another for the skin install. You need to follow BOTH of these TO THE LETTER.

Start by opening the Cupwise-Tone3.pdf (found in the CupwiseTone3-Programs.ZIP archive) and do the two step install for the main portion of the plugin. Make certain you test it as they suggest with the N4 finder before moving on to the skin installation. Do not mess around at all with the skins stuff at this stage. Once you have that portion working as described in the guide, you're done with that portion. Move on to the skin installation.

Inside the main programs ZIP file (CupwiseTone3-Programs.ZIP) you will also find the cuptone3-skins.zip. Extract that archive and open the Cupwise-Tone3_Skin-install.pdf and follow the N4 skin install portion TO THE LETTER. DO NOT PROCEED past the N4 section. Once completed you should have various VST/VST3/AAX's ready to be used in any DAW. You wont need the N4 finder anymore to run the plugins - they will all be available in your DAW as VST/VST3/AAX or whatever you created during the install process.

 

Last edited: Feb 2, 2026

Thanks for the follow-up Saccamano!

I may have corrupted my install by moving things around while guessing.

The audio passing thru this thing caught my attention as being quite different but pleasing. I was very surprised.

I'm going to start from scratch and re-read those instructions carefully and report back.

 

The reason my answer is deliberately vague is because the solution is not the same on macOS and Windows. It’s not just different instructions; it’s a different approach entirely. I’ve seen the Windows “model” explained correctly many times here: you create a repository, place the right files in the right locations, and follow a fairly detailed, multi-step process. That part is well documented.

On macOS, especially when using third-party libraries like Cupwise, AlexB, or TimP, the more you manually move things around, the more likely it is to break. The macOS installs tend to fail because of over-handling.

Your specific error, “Error Opening the N4 VST Configuration File,” is a very well-known failure point. I’ve even seen it with Cupwise libraries on Mac, and later fixed it only by undoing file moves and restoring the expected structure. I’m not going to get more prescriptive than that here. You’ve run into exactly what many people hit with Nebula library installs.

The reason this matters: on macOS, after enough experimenting with the wrong approach, the file structure usually ends up so contaminated that the cleanest fix is to wipe it, clean up, and start over. That’s why I suggest searching this forum for Windows installs that are explained correctly. Search for things like “Nebula third party install Windows” or “Nebula AlexB install Windows.” Threads marked Solved are especially useful even if you’re on Mac, because they explain the underlying model clearly.

As for the parameters: conceptually, Nebula works like a convolution reverb. Instead of impulse responses, it uses vector files created by sampling hardware across different controls and behaviors. If a control snaps back, it usually means there is no vector file backing that parameter. That’s normal in some cases.

Think of classic hardware examples. An LA-2A has no threshold knob. A Fairchild 670 has no input control. If Nebula exposes a control that a library was never sampled for, that control will snap back because there is nothing for it to load. That’s expected behavior.

When a control should work but snaps back anyway, that’s different. That’s Nebula failing to find a vector file it expects. At that point, you’re looking at an installation problem: wrong directory, wrong permissions, or missing files. This one isn't a "push this button and it's gonna work". It's not.

This is why you will see people tell you that Skins will improve your workflow. The only parameters you care about have controls there like a normal plugin. They don't actually do anything besides that, and are just more files; so I never use them.

 

Last edited: Feb 2, 2026

Unfortunately, it's not that hard to break the Nebula stuff on the win platform either. In fact it's hard to keep it from breaking most of the time. It's just the nature of the structure of the nebula plugin platform. I will not mess with nebula stuff that doesn't have proper skins or install procedures included with it. It's way too easy to screw things up by trying to guess where/how the file structure should go without a proper install process. Properly constructed skins will pull the various program pieces of nebula plugins together so that they operate in basically the same fashion as any other vst or aax. Without them you're left with a crap load of cryptically named program files that can be grouped into vst's or aax's but that whole process, unless it's carefully outlined by the dev, can be a fools errand as well. You can also just open the individual programs via the finder, but that generally only gives one single parameter of an overall plugin that can have 10-20+ different parameters that were captured. The "skin", IMO, is the unifying factor and gives the user a proper perspective of the whole plugin so that it can be operated somewhat intuitively - as long as the skin was properly made in the first place and is installed correctly.

If the thing simply wont work properly even after installing per spec then IMO it's just a wash and time for the bit bucket. I have both R2R acqua and third party N4 stuff running fine on my production rig using the standard win based installs for both and they coexist successfully and can be used together without issue. There have been a few nebula third party plugins that haven't worked as expected for one reason or another and I ended up just deleting 'em and moving on. I have no time or interest in trying to fix stuff that's broken or incomplete from the start.

After using Nebula stuff for a length of time you'll find that they are just somewhat quirky and a learning curve can be involved to an extent with certain plugins even when installed correctly. It's just the nature of the beast. The same can be said to an extent about the more self contained R2R acqua stuff as well.

 

Last edited: Feb 2, 2026

programs go to programs
vectors go to vectors
properties go to properties
skins to skins
setups to setups

its really not that difficult! If a program does not have a skin / setups, the only two types of files you need to worry about will be programs and vectors. To create a setup with these, create a new setup, search for the files in nebulas finder, drag them to the new setup window you just opened, right click and select whatever one you want as the default, select your plugin type, name the plugin, enter a random magic id, save it and you are done. Now when you open your new plugin, it will open with the default, and you can use finder within the plugin to quickly switch between the rest of the programs for that particular suite.

 

To all involved in helping me with conquering this beautiful beast...Thank You!!!

I found a YT setup video and have gotten the N4 instructions, these are far clearer than the libs included instructions. This is very simple and yetvery hard simutaneously as I read the steps to get a functional setup. Very easy to ruin.

I have learned:

*The N4 directory is where the base N4 plugin is located/installed.

*The Setups directory is where the new setups will be saved. In most cases, both of these values will be the same.

In my case, they are not the same. I was doomed from the start. Time to read up.

I will keep this thread updated with my progress. I cannot Thank You all enough for stopping to assist me.

I want to see what all the fuss/hype is about.

May the wind always fill your sails, cheers!

 

Yeah... no. sans a proper working "skin" (or available skin) == bit bucket. I have no tolerance for the "default" N4 interface.

 

Can you share the YOUTUBE setup video, THX

 

Hi Iv created an account to bump this thread in hope to find some help getting Nebula 4.5 working on my WIN10 pc on Ableton 12 and feel I may also be able to provide assistance in troubleshooting vsts, etc for other members in future.
I have previously had some of the R2R Acustica/Aqua plugins working, Taupe, Ash, etc and not too bothered about keeping them - so used revo to uninstall all previous installs. Iv also never installed any legit acoustica products or aquarius.

1. I made sure Microsoft Visual C++ Redistributable (2015-2022) x64 was installed then I installed the R2R frame work [add all the framework .dlls to C:\Program Files\Acustica\Framework].
2. Then added C\ProgramFiles\Acustica\Framework to PATH in system environment variable by searching 'env' in win search bar and opening 'edit the system environment', clicking on environment variables box, then clicking on path under system variable at the bottom, the edit, then new then adding the line C\ProgramFiles\Acustica\Framework. Then installed w_dpcpp_cpp_runtime_p_2024.0.0.49848.msi.
3. Then I copied the nebula4temprepository folder to C:\, then ran Reg.reg file.
4. Then copied the vst3 to vsts3 folder and same for vst2.

After scan for new plugins in ableton, found both vst2 & vst3 for N4 and both would open and show UI but not response when clicking on any of the interface buttons and says 'Loading' on bottom of UI - nothing loads, lols. So I managed to get the VST3 only version working using Metaplugin, however on the UI it now says 'pls authorize this product' but does let me use the UI, finder, presets, etc. When I create a new setup in n4 for both vst3 or vst2, it successfully creates the plugin but when opened in ableton I just get empty default n4 UI that doesnt work. Same thing happens if I try using Metaplugin on the generated VSTs. So im now at a lost end and hoping someone can point me in the right direction or tell me where im going wrong.

[sidenote] In settings for the n4 directories I have them set to the same directory as my VSTS, like for for VST3 I have the N4 and setups set to that same directory is this correct?

I know this release is way before witches released the awesome new R2R system which I have fully installed an updated - I was wondering if this may be effecting the R2R acoustic framework on my system...

EDIT: Finally resolved this by installing a previous release - v.4.2.2.1...turns out the v4.5 was only an update so the .aut file was missing. Problem solved

 

Last edited: Mar 31, 2026