Just get 1656. It is a very different beast in comparison with great SUM100a! Very creative and very (ultra) fast )) Vey good on drums (for those smashing parallel compression). The only thing i dislike - all Nebula compressors can't "eat" fast peaks (1.5 ms or less). But it is Nebula issue, right?
1.5ms is very slow, it wouldn't be that, it's not related to what you see in the ahead values . We are talking micro seconds here. The EVF are analog styled ones... I can actually go faster again, but was trading off sound and performance. It's at 0.044 program rate, which is the rate I've been using for around 2 years, that is also what around the program rate acustica have just started using for insane mode....
For using ahead parameter- Not sure but double check that your ahead values globally are high, reset at a high value,save, reload nebula, recheck value. For example 6.0ms will give you the headroom for other presets other than mine
I can also extend the ahead parameter to 6,ms for nebula server users.
Just a note to all customers Regarding compressors- The only tweaks I recommend is changing from stock is ahead. If you had changed your opttimed selection you potentially could of turned off timed mode. This would mess the compressors up, letting transients through and messing the whole emulation up
Its just if someone could of bought one of my comps and wondered why it was slow.
It's not necessarily related to the poster above but it reminded me.
Tim Petherick wrote: For using ahead parameter- Not sure but double check that your ahead values globally are high, reset at a high value,save, reload nebula, recheck value. For example 6.0ms will give you the headroom for other presets other than mine
hey tim. thanks for this reminder. after reading it, i took a look at my ahead parameter setting and saw that it defaults to 22.5 ms. i'm assuming that's good, but you tell me.
Tim I too was under the impression that around 6ms was about right. I think it was either TimC or AlexB that wrote that if the ahead time was too big it screwed up the compression quite badly. Maybe some one else can confirm.
^i stand corrected. i think there is some sort of bug in the gui. when i launch an instance of nebula and load a preset, i check the master page. next to "AHEAD" i have a value of 22.5. however, when i click on it, it changes to 6.0 with the corresponding fader all the way up. i guess it's a bug, and it seems as though all of my presets (including compressors) are behaving as they should be.
The max ahead time of a preset is set inside the preset. The master page setting lis just global, setting the amount of headroom. So if you set it to a large enough value it will cover the setting inside the preset.
The dev decides how much ahead is applied to the preset. For example in cal dl1656 the preset internal setting is 1.5ms, so even if you set the global master page to 6ms you'll still only get 1.5ms The reason I mention to set master page to 6ms was to cover any settings in other presets apart from this one.
About max ahead times and what works-
If you have the latest Nebula server 1.4.009 you can get up to 6ms without issues. In old nebula or regula neb pro had issues with going above 1.5
This is why I set the preset up internally to 1.5ms
On top of all this I should mention that the ahead in my comp presets are only to get to unrealistic attack times, the preset already runs as fast as the hardware without applying any ahead on the fader.
I'll add this to my FAQ I've just started to put together on my site. It will grow over time.