Hey guys! I recently started using Nebula and I'm LOVING it but have a couple of really basic questions.
First, if the Reverb instance of Nebula is identical to the normal instance, only with worse latency, what reason is there to NOT use this if you aren't tracking while using Nebula?
Second, if I'm working at 48k and a program was built using 96k or 44.1 samples, am I messing something up? Everything sounds fine to me but would it sound better (more accurate to the original hardware) if everything matched?
That's really about it. Excuse me if these were answered elsewhere. I looked and couldn't find but it's always possible that I missed something.
I always use the Nebula Reverb instance over the non-reverb one. I'm unaware of any drawbacks to doing so (other than the latency, which you mentioned).
As far as sample rate goes, Nebula has an internal SRC for the programs so that it will always try to convert to the project SR regardless of what the program was sampled at. The one thing you have to worry about is making sure your RATE_CNV is set high enough that it has the time on load to do that. I leave my RATE_CNV setting around 3500 (you should find that setting on the MST page on the UI screen) and that seems to work for most programs (occasionally a very long reverb requires a higher setting). You can tell if your SR is converting correctly on the PROG page. You should see: FRT: ##### -> ##### Hz if it's working. If it's not, either the ##### will be incorrect or, more commonly, a second blinking arrow will indicate a problem: FRT: ##### -> ##### Hz <- If you do see the blinking arrow, usually adjusting for a longer RATE_CNV will alleviate.
OK, I think I have a question that qualifies as n00b. In the "Kern" menu you're (as far as I can tell) able to set the number of used kernels, fram "0 Max" to "10 (9th)". The default value seems to be "0 Max". What does this all mean? Should I set the value to "10" to get the most out of the programs or what?