giancarlo wrote:it's like you increase gainin (input) about 24 db... if your input source is loud you are simply overloading nebula...
yeah i noticed this recently after i made a few 'trim' version programs of some things i have. the trim knob (called 'gdrv', i think?), goes from -30db to +30db, so what i did was lowered the pad-in to -30. that way you can crank the 'gdrv' (trim) and still not go past the loudest sample (unless input goes over 0db).
maybe the template or the feature you're adding to NAT should automatically add a pad-in?
it's correct if you don't padin. You use a positive trim if you have a quiet signal, otherwise it would not make a sense. If you have a loud signal you lower gdrive, if you have a quiet signal you increase gdrive. If you have a 0dB you input -18 and so on. This is the correct usage