I am finally trying to install and authorize the EAR libraries I purchased from AITB. I have a few questions, though - hopefully someone could help me:
1) I installed the 96kHz files, rather than the 44.1 kHz, figuring if I had the opportunity to do this once (given that they are closing) I may as well install the more detailed library. However, the 96kHz files are much bigger. Is there any audible advantage to installing the 96kHz library over the 44.1kHz library?
2) When trying a few of the programs I experienced crackling at the end of the sound. This seemed to disappear when I turned the "liquidity" knob all the way up. Is this normal? Is this a bad thing? Would turning my CNV rate up to 9000 be better than increasing the liquidity?
If You want to limit CPU, you have to limit program – that means limit tail ( in NEBULA go to KERN page > change FREQ D parameter and click SAVE) or limit kernels (KERN page > KERNELS parameter change from „0 Max” to „1 Clean” or „2 <1st>” ).
If You don`t hear full tail lenght go to Nebula MAST page and check *L FREQD parameter (increase it), click SAVE and reload Nebula.
If You have any problems with loading programs when You are not working 96khz – go to MAST page and change increase RATE CNV to min 6000 (i suggest max 9000).
dagovitsj wrote:Hi! I had the same problem. In addition to all that's already written, this is what really solved the problem:
<DSPBUFFER> 8192 </DSPBUFFER>
Yes, you have to raise the DSPBUFFER really high! Then I experienced no crackling or strange sound other that the lush sound of EAR
I was having a terrible time with the Acustica reverb library presets in that my CPU would just spike out of control when using the reverb dll and any presets that had a FREQD setting above 2000 ms. I just tried changing the DSPBUFFER setting as suggested by dagovitsj and now my CPU barley moves at all even with a reverb preset that has a FREQD setting in the 4000 ms range.
I couldn't do 8192 as I'm using Nebula inside Pro Tools (actually inside Nomad Factory MAGMA inside Pro Tools) and the delay compensation was outside of the maximum range Pro Tools can handle. I scaled it back to 4096 and Pro Tools is happy.