For anyone seeing such issues can you confirm whether you have any VST3 double precision capable plugins in your signal flow? We found a case where VST3 plugins could be initialized incorrectly when using the 64 bit engine.
To clarify, this is exclusive to VST3 not VST2. This issue will be addressed in the next update.

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

New symptom: the same project opened today with a clearly audible pink noise going on, and the meter on the reverb bus (containing one plugin, ValhallaPlate) is pegged. The master meter is normal.
 
After muting one particular track, or bypassing its fx bin, the noise goes away and the reverb bus meter returns to normal. That (audio) track is connected to a frozen instance of Kontakt. There is a loud bang when I re-enable the bin. 
 
After enabling and re-enabling this fx bin a few times, the project went into the no-sound-meters-pegged mode. Nothing I did would bring the project back to normal, including stopping and restarting the audio engine and completely deleting the Kontakt track. Only after completely exiting out of SONAR and reloading the project was everything functioning correctly again.
 
I have not seen any of these symptoms in other projects, even though most of these plugins appear in them as well. The exceptions are Roth-AIR and Replika, which I normally don't use. Both are in the bin of that Kontakt track. I have removed Roth-AIR and am now waiting to see if the symptoms return.

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.

Noel Borthwick [Cakewalk]
For anyone seeing such issues can you confirm whether you have any VST3 double precision capable plugins in your signal flow? We found a case where VST3 plugins could be initialized incorrectly when using the 64 bit engine.
To clarify, this is exclusive to VST3 not VST2. This issue will be addressed in the next update.

My main problem project doesn't require the 64-bit engine. The only VST3 plugin is SPAN. All other plugins are Sonitus. It does use audiosnap.
 
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.

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

So if you are seeing it with VST3 and the 64 bit engine its very likely the problem we found.
If you can repro with a project containing NO VST3 plugins then its some other issue.

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...

LatencyMon sorted , if you have a z800 or a setting in your bios called "Enhanced Memory Performance "! TURN IT OFF , it was giving me Highest measured interrupt latency to process Red bars of 3k to 21K , anyway now it is disabled it is idling around 10 - 30 us with the highest at 600us SOLID ! WAPITA that was to find.
 
Regarding testing this vst3 or not problem, i have an idea which i am going to try.
 
I am going to fire up my big project and continue mixing until the spike/pop appears, i will have latency mon running continuously also and will monitor it and video and audio record .
If the spikes/pops appear i am then going to stop and start from track 1 to the last track ( top to bottom ) and swap out all vst3 effects and instruments with vst2 . Then i will save this big project as vst2 test save and restart computer and then fire up the vst2 test save project. I will then continue to mix and see if the spikes /pops re appear!
 
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
 

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!