sonar is now clicky, slows down jittery.never did this

So just to see if it was my drum bus i added..i deleted bus sent drums to master..still does if when i start a/b ing effect in my pro channel..so i played back just snare solo...seemed ok then i expanded the eq in prochannel..sure enough starts the click clicl click

Ill check it sun..im running 2 delta 1010 pci cards and a sonatis mixer via fire wire..im wondering if it could be a clock issue..ill try latency first..its just odd cause it used to work fine and i havnt changed anything with comp

Check that the recording rate/depth (e.g. 44.1 Khz / 24 bit) under the time display matches what you've got set under File->Audio Data within Preferences.
 
I've found if these are different, Sonar has a hard time continually changing the rate/depth in realtime.
 

Hi guys...ty for responses...sample rates are the same..mouse and keyboard are hardwires..sample rate is
Buffer in playback que 4
Buffer size 200.0 msec 8820sanples
Effective latency 600.0msec

https://www.youtube.com/watch?v=eOVuzOja-yE&t=2s
 
The above is a link to how to use latency monitor. Maybe there is a driver getting in the way?

jude77
maybe be a wild shot, but when I get weirdness I sometimes try a system restore.

So do you mean system reset ? In win 10...then it give you options "keep my files" removes apps and settings but keeps personal files..and "remove all apps files ans settings"...if i do either will i loose all my work in sonar ?

Ok ty i watched video i will tryto download the latency tool and disable the things suggested in video...i will also try to find my buffer setting and post...thanks so much

Yes im pretty certain i installed the last driver they put out..i beleive they are no longer updating the driver for this card..theyre not the 1010 with all the wires hanging out..it has 8 t.r.s ins and 8 t.r.s outs on back..rack mountable

increase it and see if it gets better. :-)

Not that I know but in this vain.... Sonar works REF4 system wide...
you can have this issue. if you have SW Ref4 System wide you have to go into the Control panel / programs and features / Repair REF4 System Wide. If anyplace on your computer, something starts running odd and you are using System wide... try and repair....
 
ALSO. ProTools First will take over. you need to reboot after you use it.
 
I'm guessing we are all trying new DAWs and related software. We all know how software can be.
 
peace!

Perhaps this coukd shed some light on subject as im still dealing with the issue...im running delta driver 6.0.8..win 10 32bit..so if im playing back my recording it plays fine..my stereo master out is 1010A channel 1 and 2....if while playing back i open a plugin with alot of visual for instance the eq in the pro channel..that's when it starts clicking and the track actually slows down...so i changed my output in master to my 1010B..when i plug in my trs wires to the output of 1010B i get really bad buzz..loud buzz...but when i play track back i can just hear it enough to tell if it changes when i open eq...from what i can tell through the buzzing the project is not slowing down and clicking...does this tell anyone anything ?.i also tried to get that latency monitor but site is down

Not sure why your sync setting says internal. Sonar should sync to audio. Also, are there settings in the audio driver for clock source? The clicking and slowing sound like the interface is freewheeling and not running at a stable rate.

I've had this issue years ago running duel 1010's running on win 7.
 PCI audio interfaces seldom to never have latency issues as do external USB and Firewire interfaces do.
 Which pretty much narrows it down a physical failure and or corrupted drivers.
 
 I had solved my issues by covering as many of those bases by simply pulling out the 1010's cleaning dust from the cards themselves and blowing out the PCI slots as well, and swapping them out between PCI slots, which will force the drivers to install to the new locations.
 However uninstalling the drivers, rebooting the computer, and reinstalling the drivers fresh gives a better guarantee against driver package corruption.
 Certainly worth a try, but make sure you have and know where a saved your I/O patching and configuration settings to a user defined file to save yourself a considerable amount of extra work and frustration.
 
If problem persists I'd pull one and try running 1010 at a time to isolate the problem for component failure on one of the cards. Keep in mind these 1010's are at least 15+ years old.
 I was still running win 98SE when I installed my first Delta 1010 LoL. I'm actually shocked and amazed that M-Audio supported them all the way up to win 7x64!
 They do NOT offer support to win 10 where they may or may not be usable, 'tis a crap shoot.
 I've read reports of some using them without issues in win10, some reports that they don't work at all.  The last of my 1010's got extremely flaky and unstable in my living room computer which was just used for playing music and surround sound DVD playback, (nothing hooked to it supported ASIO drivers) went PITA after upgrading to win10 and would always default the clock setting to 44.1k/Hz upon boot up and have to be manually set to 48 k/Hz to get any sound at all.
 I'm thinking it didn't like the new and improved Windows sound drivers? Why does the clock need to be set to 48 k/Hz to even play CD's or .mp3's in Windows Media Player???
 And what even more confusing is how in the name of Zeus's butt hole did my grand daughter figure THAT one out?

Yup.. latencymon.

Do you have any other DAWs installed?
Completely uninstall any virtual drivers like ASIO4ALL as well (if installed). Reboot..

I'm leaving.. :)