I installed the new release and now the 1 kernel comp I tried (don't have the name handy) gives some static, it also says 2 kernels in the nebula3pro indicator. I have the feeling I'll just reinstall everything and try making a new Nebula Comp from scratch. I think the API2500 will sound really good if I can get it tuned up.
Can you point me towards the right direction on this: The „EX“, „NC“, „ME“ and „NL“ versions can only be used with Nebula Compressor (Self modified copy of Nebula) and are in HQ by default (using TIMED engine).
I remember reading about it back when the whole discussion on Nebula compression kicked in, but it's been a while.
I was reluctant at first but it's actually super easy:
-Copy your Nebula (not Reverb, just plain Nebula) .dll (Windows) or vst (Mac) and name them both "Nebula Compressor.vst/dll" and "Nebula Compressor.xml". -Open Nebula Compressor.xml in a text editor and add a line and change a value: "Open the XML and add
<UP> 1 </UP>
right below <MAGIC> xxx </MAGIC> Change <PROGRAMRATE> value from 2000 to 100 Save it. That's it. You can change skins and segregate off a /nebulatemprepository and all that or not. They're resource hungry little buggers. I didn't really have a chance to do any kind of comparison between the 'regular' 1k programs and the NC ones but the regular ones definitely sounded good. The line amp programs are not delicate so you actually get some of the sound from them; that's something Nebula has always been good at (compressor mojo/line amps). So far I've gotten really excellent results with some tracks and busses but I've yet to fall in love with it on the 2-buss the way I took to the 609 (that preference is not a reflection on this library but rather my tastes). And even if it never makes it onto the 2-buss I can see this getting some use particularly on the drum side of things.