I notice that AAS session rhodes does this alot with sonar....then i noticed other VSTi's having added latency when there is a project load...the cpu multi core threads hover around 25 percent...so should be comfortably running the instruments fine. could be a way the aud.inii file or a multi core setting is in Sonar platinum... i have a fast computer (see specs below) and on a couple of projects, when i start stacking instruments, i start getting latency and the occasional 'ghost' note playing. I have tried difference buffer settings and with different sampling rates... this appears strangely in the update. However, i wonder if it has to do with multi core settings or the old RAM LEAKAGE issue that goes back WAY back to XP....i dont know - but it kind of behaves like that. Anyone have same issue and solution. Also, If i open a new project, during the same session with Sonar running and close the other just to test to see if it is a load...after about 2-3 mins, get minor added latency again...even on older non-cpu intensive plugins. any OS tweaks?, aud.ini? registry ram tweaks? this thing should run like a scalded dog...  
 
Sonar Plat 2016.12
win 7 64 bit sp1
Proc AMD fx-9590 8 core, 4.7ghz
Gigabyte 990fxa-ud3
Mushkin SSD 400g
16 gig G.skill ram
M-audio Delta 1010 PCI with 6.0.8 drivers...latest drivers
 

Latency should be a function only of the buffer size, the inherent hardware/firmware/bus latency of your interface, and plugins that induce Plugin Delay Compensation. It generally won't change unless one of those three sources of latency changes. If CPU and RAM can't keep up with the demand, that will generally manifest as pops/crackles or dropouts, not increased latency.
 
The first thing to check would be plugins that use lookahead buffers that induce PDC. Some common offenders are Cakewalk's Transient Shaper and linear phase EQs and compressors, convolution reverbs, guitar processors and any plugin classified as a 'Mastering' FX. AFAIK, AAS Lounge Lizard (either full and 'Session' version) doesn't induce PDC.

Not sure if my post will make any thing fix up for your problems...as Mine are still being tested.
 
I mean no harm to you or any other on the forums.
\Cake walk tech have remote viewed my system ((Mike)) trying to set things right in Sonar...and funny things happening all over the spectrum.
 
I would say...Check your event viewer for error codes in any of the selectable left hand pains for services and or applications.
 
If you are having issues with large projects...a caching issue may be in play? or some MS management...might be in error of a service not working right.
 
As MS was soon called in to my estate to remote view the error codes of...caching, and or driver corruption , and or update loops, or not installing because of...X not working services, which always restart up...causing interuptions in cpu, memory, or swapping...slowing down, and if too much hanging the process,.. of work...and crash/hang up my system, or spike the cpu, or thrash the drives on systems using windows MS OS...causing latency...spooling everything done on a system to a file on the c drive or other might be in play taking up lots of space...if making video, and or audio files large....the spooling of the data being collected in a cache or file might be getting over loaded with data...as mine was?...sure it was!...and the service to send, not sending it out or removing it....big issues eh? Yep!
 
The very first thing, is to, make sure that OS, has no issues....if it does...and window 10, being a spy bot spooling and sending app built in tracer, and tracker, and sending more so, than win 95-8.1....Your app for music will suffer all kinds of problems , the more you demand Drive use, memory, and cpu usage....in performance...the more you will suffer in trade offs.
 
 
This is where you should focus first to gain a working performance machine first....Then play with the setting for latency later on...in applications for music or video...all things must work in sync , and at their best level of performance....no errors or bad services, or issues with those things or managing of them.
 
 
Best of luck....and MS chat, can help if you got issue in ""event viewer"" of such things happening.
 
If you feel something is a muck....take notes of the time when it occurs....and seek the event view to see what is running at that time.
 
Not sure if payment is necessary for a remote view of MS....But it can help get a stable and robust platform if the issues of, or cause for a slow system...are solved first....Your experience with Sonar or any other platform might improve greatly.
 
and firmware...if it be driver..or something you must download for...do all of that if the latest os is updated...to x, then bios and other motherboard drivers along with any firmware for ssd, or other devices might help fix...slow performance on OS of choice.
 
 
Although My issues might be ongoing....And long winded in words....They hold merit...and good will for all.
 
Cheers....
 
 
Sir Les

How long have you been running that setup?  Have you always had these issues, or is it a recent development?
 
With a 15 year-old interface, I'm tempted to look there first.  (Not necessarily at the unit itself, but at possible driver or PCI slot incompatiblities).  See this recent thread:
 
http://forum.cakewalk.com/New-Build-Bad-Interface-noise-m3547049.aspx

Firstly, Thanks for any replies and suggestions. I appreciate your feedback...
 
I have been running this setup for a while, i did not have issues with x2 but upgraded my system when i went to platinum. The older platinum appeared to have the same issue.
 
**** -- just to clarify my problem, I dont have this issue UNTIL i start playing or hit record...THEN the delay starts...and progressively gets worse as the project plays on... I suspect it is a memory management issue or a setting. I have noticed it with Waves Rhodes...but also with the AAS Lounge Lizard Session... Does the same thing...
Here is an example - If I load the project and NOT hit play, all instruments have latency of 64 buffer. Very nice. Thats why i built the system to handle that demand. However, when i hit play, it has about a 5-7 ms delay added to it...not enough to make it unbearable but definitly changes the 'feel'. However, over time, it seems like its playing at 20ms and THEN random notes will play or release like ghost notes. Releasing and renewing the Engine does not reset the lag. Very strange - if its an OS issues then yes - will go to windows 10 - however, only if my M-audio Delta 1010 will work with it....which is why im still on win 7 64 sp1.

Check the size of the MIDI buffer in preferences. It tells Sonar how far ahead to process MIDI, essentially the same kind of thing as the audio buffer does for audio. If the buffer overflows result is dropped MIDI notes and/or garbled MIDI. By default its usually 250ms. If its set to 250 try 500ms or even higher. There's usually no negative consequence of increasing the MIDI buffer other than the transport is delayed by the buffer size when started.

May or may not solve your particular issues but it's worth trying.

benrecordingmusic
Firstly, Thanks for any replies and suggestions. I appreciate your feedback...
 
I have been running this setup for a while, i did not have issues with x2 but upgraded my system when i went to platinum. The older platinum appeared to have the same issue.
 
**** -- just to clarify my problem, I dont have this issue UNTIL i start playing or hit record...THEN the delay starts...and progressively gets worse as the project plays on... I suspect it is a memory management issue or a setting. I have noticed it with Waves Rhodes...but also with the AAS Lounge Lizard Session... Does the same thing...
Here is an example - If I load the project and NOT hit play, all instruments have latency of 64 buffer. Very nice. Thats why i built the system to handle that demand. However, when i hit play, it has about a 5-7 ms delay added to it...not enough to make it unbearable but definitly changes the 'feel'. However, over time, it seems like its playing at 20ms and THEN random notes will play or release like ghost notes. Releasing and renewing the Engine does not reset the lag. Very strange - if its an OS issues then yes - will go to windows 10 - however, only if my M-audio Delta 1010 will work with it....which is why im still on win 7 64 sp1.

For the phrases above modified with bold font, this is the exact behavior of an effect that has a required delay (i.e. requires Plugin Delay Compensation because it needs to look ahead in the audio stream), the third category listed above by brundlefly in post#2. This can't be fixed by a faster CPU or larger buffers. The "offending" plugin should be removed or replaced by a stand-in that does not do look-ahead. (Or you can turn off PDC.) Next step would be to see which reported problems remain. Plugins that require PDC can be put back in the project when you no longer need low latency.