- PAGE 9 - http://www.musicdsp.org/files/denormal.pdf 
 
3.2.5 Alternatives and efficient solutions
The methods below are derived from the previous ones and are close to perfection. They fit in
numerous common cases and are very fast. They are based on the addition of two alternative
values to the signal. As soon as the added value changes, the denormal apparition is prevented in
or for future feedback loops, for a limited number of samples. Value alternations just have to be
frequent enough to prevent most of the denormal apparitions.
Spectrum of the generated noise is quite rich. Moreover, by choosing 0 for one of the values, one
can create a DC offset while reducing calculations
To minimize calculations, one can also call
add_dc()
sporadically, for example one time every
20 samples, or even more. This produces random pulses, the spectral content of which is rich and
close to the white noise. However generating this random time component is not always obvious
and easy. One may just call
add_dc()
regularly to generate an impulse train. This method also
produces a lot of frequencies everywhere in the spectrum. It is especially adapted to block-based
processing. Of course block size should be carefully chosen depending on DSP algorithm
architecture.
+
Very fast.
Fills the spectrum almost uniformly.
Propagates to next stages.
–
It does not eliminate denormal numbers, but prevents their apparition.< if this is the negative then how promising is this )
To be maximally efficient, requires block-processing algorithms whose size should be
carefully chosen.
Alters the smallest numbers by quantifying them.

"mettelus:
Having an "audio engine troubleshooting" feature to hunt/kill bogus plugins would save some folks (literally) hours of troubleshooting time, alleviate the need to use "safe mode" when opening a project, and also supply a definitive answer from the right source (the audio engine itself) instead of trial and error or tribal knowledge from the end user(s). Such a feature has been hinted at before, and it is definitely one end users would find immense value in."
 
For a DAW like SONAR with so many anomalies and problems that constantly steal your focus from creating music, something like the above-mentionend "audio engine troubleshooting" in mettelus' comment, should have been implemented a loooong time ago.
 
We're now in the year 2017 but it seems like these problems aren't going anywhere. So I guess these problems are most-likely being migrated over to MacOS when that release finally comes out and that's a problem.

abacab

bitflipper
I never use the 64-bit option, either.

I'm surprised at the number of posts here and in various threads from Sonar users that have shut off the 64-bit option.
 
That can't be a good sign ...

Me too. I now habitually turn off the audio engine before adding a new plug-in - esp on buses - and since I've turned off the 64bit option, no melt-downs. 
 
+1 to the Audio engine processing thingie to hunt/kill misbehaving naughty plug-ins BEFORE they *u## things up. :-)

I have noticed this in past times using sonar...but, I also noted cpu spike when this audio level would pop to the extreme ...and then no sound.
or some kind of hard drive thrashing on the cpu /disk metering...at times...
 
That is why I dug into MS windows services....as I was not using any FX, or any of the on bus or track features..all were turned off in my templet , as someone said to do once upon a time to stop a new feature add in from causing this issue of pops...is to turn off...all channel strips...but it did not solve.
 
Thus seeking into the logs of event viewer ...brought me to ruin...and updated and more and more problems...trying to solve the logging....which I think, was caused by the secret arm of MS trace and track...of your data on all drives while working in or on the system...win10 does do odd things with the nic and cache.
 
Just saying...it may work out..it is a plug in...
 
So...I stopped using it..and wait for a more bugged less of Les OS....
 
 
Just smile..it might take a picture of your frustrations one day...and or any uttered words ....cortina cortana..did you ask the machine why this is happening?.....LOL
 
Just be cheery...I am sure, they will dig into the...hacking it out soon...if it continues...wait...
 
Now what works, while waiting a life time to use?...ah....Some say Cubase, some say Studio One 3, some say Reason 9.5...Pro tools is a monster daw...
 
and others say the free stuff works ok also....so, you can still make stems...and import when, and if the issues are fixed.
 
 
 
 
 

Can you please screen capture / audio capture the pop / spike problem you have , we realise it's too hard to re create but with video evidence cakewalk will have a better chance at fixing this .

My plugin list for the project that yields these symptoms about 50% of the time. All are VST2 except for the two marked with an asterisk.
 
FabFilter Pro-C 2    
ValhallaUberMod    
FabFilter Pro-Q 2
iZotope Ozone Exciter
TH3 *
Audio Assault HeadCrusher
Roth AIR
Waves RBass *
Nomad Factory Bus Driver
NI Replika
MeldaProduction MSpectralDynamics
iZotope Ozone Advanced 
FabFilter Pro-L
ValhallaPlate
 
Kontakt (3)
Omnisphere (2)
Trilian
Zebra2 (2)
Superior Drummer
 
 *VST3

My "problem" projects use the following VST3 double precision plugins:
Slate VMR (using VCC plugin - this is on every track)
Klanghelm SDRR (only one song uses this)
Slate VBC (only one song uses this)
 
Like I said though, I only get the problem when my ASIO buffer is set too low, an dit goes away when I make the buffers bigger - so I always assumed this is an audio interface driver (MOTU) issue, and not a plugin issue.

I use mostly vst3 plugins, if i can i will always choose vst3 so 90%+ of my project effects is always vst3.
 
Day before yesterday everything was going fine, then i inserted spire vst + CLA 3A vst3 + overdrive vst2 and the problem started and stayed random spikes and bleeps.
 
Also on a previous day everything was going fine then when i inserted a instance of kontakt 5 vst2 + pro-q vst 3 + the glue vst 2 , the problem appeared and stayed.
 
I am not saying anything other than inserting a instrument or effect is on the top of my radar list ATM.
This could be a vst3 issue ! and  i hope it is so it gets fixed faster.
 
Right now I am starting from the ground up at my end i am running latency mon with a big platinum project on loop playback and any drivers or conflicts are getting fixed ! I will also point out that during yesterday all day while platinum was on loop playback and NO other mixing was being done ( Nothing inside platinum ) the problem did not appear, even though latency mon is telling me to keep searching for a irq latency conflict.
This is good because it is helping the direction of what is causing or triggering this spike pop bleep problem which i believe we will find, or at the very least i will show you what happen at my end.
 
Once latency mon is sorted completely, i will then screen and audio record the platinum loop playback + latency mon  and then start doing inserts and try to trigger this problem so we can nail it down once and for all !
I believe WE ALL can help by putting in as much effort to try and locate this BUG and particularly NOW because we are all here with this problem so lets focus on it, and try and see if you can connect any of the dots at your end!
 
Thanks

PeterMc
 
In the past, this project did use the 64-bit engine, and also used Ozone VST3. Is it possible for the incorrect initialization problem to persist after plugins are deleted and the engine changed?
 
Cheers, Peter.

No I cant see how the problem could persist. It has to do with the initialization sequence when we set it to use 64 bits. Something was preventing the plugin from getting the notification for 64 bit processing and as a result it thought it was processing 32 bit data. We were able to repro this with our Adaptive limiter VST3 which led us to diagnosing the problem which was in SONAR not the plugin...

taccess
I just want to do what ever it takes to sort this and move on so i am willing to spend as much time doing what ever it takes to try and narrow or confirm this.
 
Will update results as they happen.
 
Thanks

 
'Appreciate the time and effort you're devoting to this, man!

Hey taccess - I started a different thread for my video example - find it here.
 
I'd be curious if this looks anything like your problem. I sometimes wonder if we're chasing more than one bug. My project doesn't use the 64-bit engine, and exhibits the problem without any VST3 plugins.
 
Can you put your video somewhere we can look at it?
 
Cheers, Peter.
 

Ok here is my Spike/Pop Video.
 
If you have the same or sililar problems please let me know.'
If you can help in anyway please do
 
http://forum.cakewalk.com...-m3632787.aspx#3632787