to everyone: the ram is cached in a better way among different instances, and that memory is read-only so your pc/mac CAN cache it. So it's possible you gain incredible cpu boosts. Anyway it's an experimental version, I suggest to check carefully if the situation is correct on your side testing those programs carefully: check that kernel length and samples number is the same as before. 3 more instances are reasonable, though. As you can guess, nebula engine is ready for being added to a daw/host code, especially eq, which are light on cpu.
First test of Nebula Server - experimental version 1.3.480.
I added 40 instances of Nebula client 32bit with AlexB console into Samplitude, it used less than 600 MB of RAM running it locally - close to 100 % CPU load with many other VST`s inserted as well.
However, after save Samplitude will not load the project without crashing. I disabled all Nebula client VST instances (control-alt-click), and saved the project again. I could now open the project, however, when enabling the Nebula VST track by track it does not show (or connect) with server - does not show instances on server. Please note that all inserted Nebula clients works, but now it uses way more RAM.It does not effect CPU use.
When deleting the Nebula client VST`s and reinstalling it again, one by one, the new instance shows in server, but none of the existing ones does.
This means that I have to reinsert, every single Nebula client VST`s and do all manual settings again. It seems like only way to activate the effective RAM use, is to reinsert the Nebula server client each time a project is loaded.
EDIT: I made a new project in Samplitude and added one (1) instance of Nebula Server Client. The server shows 1 active instance. Then I saved and reloaded the project. The server now shows zero instances and the Nebula client uses more RAM.
Thanks, did you check RAM usage in task manager, and number of instances on server?
In my case, the plugins shows up, and play without fault, but effective RAM usage is ONLY available upon initial install of the plugins. After save, and reload the RAM usage is far more, and the instance (plugins) does not show in server. When you disable and enable plugins like you did on screenshow, the connection to local server is lost and the plugin uses more RAM.