Tips & tricks, working results, technical support
My "crash" problem was related to IP setting in XML file. I had to remove the server IP address in XML file. When I did, both Samplitude and REAPER was able to load Nebula without problem. I deleted my previous "crash" related post to avoid confusions
no the code is still there...darren wrote:Hi folks,
A previous recent version of server prevented the nasty stutters and glitches you hear when loading another library into the instance. .499g seems to have taken a step back in that regard.
Why the 20 kernals? I'm i missing something.I am looking forward to the 20 kernal .But its not here yet right?tbentley wrote:Hi,
On the next version, could you please make the max kernels 20? I have to edit the text file every time i update.
Some Programs are 11. If you have it set at 20 you future proof your self as more programs start using higher kernels.Also you don't have to adjust the configuration file. Know thinking about it you might as well set it to a 100. I just don't like messing with the configuration file to use all the kernels that library developers sampled.
if you use an higher value you waste more ram, even if it will not be used because nobody is releasing libraries based on more kernels. It happens because actually all buffers are created during startup, even for unused kernels