3 May
2010
3 May
'10
3:33 a.m.
On May 2, 2010 10:22:29 am you wrote:
On Sat, May 1, 2010 at 8:10 PM, Tim E. Real
<termtech(a)rogers.com> wrote:
Yeah, now I'm wondering if MusE's basic DC protection level was simply
too low, at least for those two plugins in question.
It is currently fixed at
const float denormalBias=1e-18;
I will try raising it and report back.
At some point I will see if I can try those plugs in Ardour and report
how it fared.
Tim.
I tired a quick mod in MusE to do what the author
of the caps ladspa
suite did to handle de-normals. He said "A -80dB signal at the Nyquist
frequency or lower". No luck.
But yeah, obviously at some signal level and type, it should stop.
So I'll keep trying. Noise sounds like the best way. -100dB white to
start? OK...
Ugh. A new MusE options panel: Advanced de-normalization options, he
he...
You might want to check ardour. It has 3 denormal protection options (2
that are h/w based, setting processor flags, and 1 that is software based,
adding a very very very very tiny constant value ("DC Bias") to every
signal. See libs/pbd/fpu.cc to find the h/w stuff.
--p