Parameter name: dB protection Description: Nebula audio engine can't go louder than +3dB. When output is louder it's "silenced" automatically. It's silenced only for samples which are louder than the protection value, so you get a sort of intermittent sound. MAST page name: - Master .XML name: PROTECTIONDB Factory value (in Master .XML): none Guru extra information: Actual default value when the key is not specified is exactly +3dB, use this parameter for reverting to old original behavior when protection was tuned to +24dB. http://www.acustica-audio.com/forum/ind ... =viewtopic
Enrique Silveti. Acustica Audio customer and technical support.
lowering the input has the same result here, but for me it doesn't make any sense...as suggested i always tried to hit nebula with input volume at about -18dbfs
when nebula is loaded into the vst analyzer it shows an input of ca. -36db which is way lower than needed AND every program of the se versions of clc and mlc and every other program (vcult, vm tube, doc fear, mammoth, draw her, behemoth, fate eq, vintage black eq) is working properly
MLC MBC exhibits the same "issue" because its PAD IN is at 0dB like Enrique said (just like CLC's). There are many other programs showing this graph (some of those you even mentioned). It is the PAD IN and VSTAnalyzer which is blowing the emulation out of proportions, that's why you have to lower its input (programs use different PAD INs). It may say -36dB but that's not true, it is hitting at 0dBFS!
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
well it seems that the program is hit way too hard, but nebula showing a wrong input level doesnt make sense at all... how should i use it in cubase? when i'm using it with -18dbfs input level it sounds wrong (thin with clearly audible resonances at the spikes in the graph)
don't go for the readouts inside nebula, concerning levels (there could be the pad in/out involved behind the scenes). place a reliable rms (not peak!!) meter before nebula and make sure you hit the plugin around -20 db rms, this should be safe. in vst-analyzer lower the input knob of nebula to -12 db and the graph should be ok.
system 1: windows 8 32 bit - samplitude prox, tracktion6, reaper system 2: mac osx yosemite - reaper(32+64bit), tracktion6(32+64bit)
both systems on: macbook pro (late 2009), core 2 duo 3,06 ghz, 4 gb ram, graphic: nvidia geforce 9600M GT 512 MB