Hello I'm a new user. When it comes to using reverb programs I'm limited to using only small rooms and such because it seems I don't have enough cpu to handle some of the medium or large halls for example. Any tips or parameter tweaks I can perform to help me get more from my Nebula Reverb would be very much appreciated..
Macbook Pro 2.53 core 2 duo 4 gigs ram running Reaper
Hi, there. I was a newbie some time ago too, and picked up a lot of good advice and tips from reading and searching in this forum. Also lots of useful info in the FAQ.
OK, sorry if this is "old news", but I think the RATECNV is set to 500 ms by default. Raise this to 9000 ms (max). It doesn't affect latency, only the time it takes to load the reverb programs into Nebula, but I'm OK with waiting some seconds.
Note: raising the RATECNV value doesn't affect loading time for EQ's etc. It just let Nebula load the whole program file for the reverb which are often quite large.
Thanx for your reply. I will adjust that parameter . I have also played around with Kernel settings that being the freq parameter and has helped in reducing load, also I adjusted Prog Rate cranked up to 40ms this also really helped. Any more tweaks anybody
For reverb presets, the "lfreqd" setting on the MAST page in Nebula needs to be raised. I actually made a copy of my Nebula Reverb dll and xml file, renamed them both NebulaVerb, and made the changes. So now I have a dedicated Nebula instance for reverb presets. And yes, increase the RATECNV to the maximum setting, 9000 I think. But the "lfreqd" increase is necessary for reverbs, especially deep ambient ones with long tails. Check out the link, it is from the manual from a preset by a 3rd party dev who makes awesome reverb presets. The pertinent info is about 2/3 down the page.
MarcelKO wrote:Excellent tip thanx for that. The link is very helpful too. Is the dll file equivalent to the vst file in my vst folder . I would like to copy and rename the two files as you have.
I'm not sure what you mean by vst file. A dll is the type of extension it is, like a zip file says ".zip" or a rar file says ".rar" after it. In Windows, unhide the hidden extensions in control panel, folder options, view. Then look at the vst you have. The dll will say ".dll" after it, and the xml will say ".xml". See my attachments.