Definity wrote:AHHH so you dont need an actual server to run it, seams tempting
No, you don't need to run the server locally to save RAM anymore. It is just an improved version of Nebula which saves RAM and uses less CPU (much less on i7 processors). In the package you also get the server which you can use in a second computer if you need, though.
i7 3770k :: Asus P8H77-V LE :: 16Gb DDR3 @1600MHz :: Geforce GT 520 :: OCZ-Vertex 128Gb :: WD Black Series 1Tb and Green Series 1Tb :: F*******e Liquid56 :: REAPER 64bit and StudioOne 64bit (both latest versions) :: Win 10 64bit
today we'll release experimental 1.3.499g for all platforms. On mac osx side we are sticky on intel ipp 5.3 because we need more checks on new libraries, there is something strange (anyway they are faster). Eventually, if someone is interested in betatesting ipp 7 on mac osx he should just send an email to me (server customer have a priority in this list). So he could compare them easily and report issues (I'll not provide an installer but a folder to copy and a vst or au to overwrite).
I load an instance of Nebula server 64 and then duplicate the instance, creating maybe 3 or 4 copies. At some point, after maybe 4 are created there is a BIG increase in volume (much more than you would expect from simply adding another of the same instance).
The volume increase can be removed by either deleting an instance or selecting a different library in any of the instances.
1.3.499g 64bit working fine in Reaper 64bit on Win7 here.
G, could you tell us what you have updated in this newest version?
Arne - I had a problem where Reaper was crashing with a previous recent release of Nebula. I re-installed the original version of Nebula Pro 3 which made sure all prerequisite code was installed and then upgraded to the latest available version of Nebula server. This solved the Reaper crash. You might wanna try that