ZeroFillMethod=4 not working

Hi Jon,
 
BUG !
ZeroFillMethod=4 is unusable at the moment, when combined with ( ZeroFillDB 0 to 300 > it has the same fill signal -48.0 ) and if ZeroFillDB cant push ZeroFillMethod=4 down to a tleast -300 then i cant be used to mix with.
 
 
Also it has been discovered that  :
ZeroFillMethod=4
ZeroFillMethod=2
Both have a constant "audible fill signal", these 2 settings need to be combined with a larger ZeroFillDB lets say double the current maximum amount to ZeroFillDB=600 or 900 if possible.
WHY ? because when using limiters and compressors and saturators on tracks this fillDB is brought up and becomes audible.
You cant test this without pressing playback also by :
A) changing your AUD.ini : ZeroFillMethod=2 + ZeroFillDB =0
or
B) put 1 limiters on a  bus !
Both of which will pull the  ZeroFillDB level up which then interferes with the MIX, which brings me to my last point!
 
 
ZeroFillMethod=2 + ZeroFillDB =300 which is the default for platinum, is currently breaching the MIX, randomly there are loud spikes and pops that come from this setting combination that are causing big problems throughout the community.
You can hear this by changing your AUD.ini : ZeroFillMethod=2 + ZeroFillDB =0 > which  will allow you to hear what sits under ever ones mix and what randomly breaches the mix and why this setting needs urgent revision starting with ZeroFillDB=600 which will push this buffers filled with alternating positive and negative values, alternating on each buffer switch / signal level down further for people using compressors and limiters on tracks, which i hope will stop these POP and SPIKE Breaches !
http://forum.cakewalk.com/A-loud-pop-and-a-maxedout-meter-level-followed-by-no-sound-m3628485.aspx
http://forum.cakewalk.com...no-sound-m3630088.aspx
 
I am trying to help and believe this is vital and Urgent information that can help Platinum's Stability !

Looking into it.  The range of values for ZeroFillDB is actually -60 to -300.
But it's specified as a positive integer, meaning 60 to 300.  0 would be clamped to 60 and > 300 to 300.
Too low of a value say -900 dB would result in denormals.
 
That is, a value of -320 dB when converted to power for dsp purposes yields a very small double value of
0.0000000000000001  just a few steps beyond and the power value can't be normally represented as a double, hence a denormal.  That would cause high CPU as the microcode would assist to try and help represent those really tiny numbers.
 
The default value of 300 should be working.  We'll check on the noise signal itself that's generated.
 
Keith