Hi, I bought a nuclear Pc and now I am very happy to be able to use 50 instances of Nebula at the same time.
My problem is that I only know that I have reached the limits of my computer when the Reaper project crashes, because the Reaper performance meter shows me around 32% when I am about to crash .
Does it mean that the crash comes from another problem, or that the performance meter is not accurate on spikes which happen on loading a new Nebula instance? And in this case, is it possible to avoid Reaper from crashing on spikes when loading a new instance, so that I can go a bit further with more plugins, maybe with a buffer setting or anything of this kind?
Hello mitch. Nebula reverb use a intensive multi thread scheme so it's not easy to measure the right amount of CPU/RAM consumption. In addition CPU core should be latency compensated and seems that some sequencers fails in that topic. Can you restrict the amount of cores from 4 to 3 in Reaper? Did you Report this to reaper support, now we Have NFR Reaper license so we can bug hunting together.
Enrique Silveti. Acustica Audio customer and technical support.