Metronome, making its own groove

Hi.  Do you have the latest drivers to your audio interface? Are you using ASIO drivers? What latency settings do you use?
Best of luck.

Thanks guys,
 
@Zargg71 I have the latest Asio drivers for my `focusrite 2i2. The buffers were at 128 but I already tried to change that up to 4096 with no possitive effect.
 
@Beepster Actually that sounds exacly like the issue I am having, I could here th the metronome was clicket @ 3/4 except that I didn't change it (als not per accident) I checked just yet to be sure. And it says 4/4.
 
Maybe worth mentioning it is with audio click.
 
I am sorry I thought my post also mentioned my setup;
 
Win 8.1 x64, 8GB RAM, 256 GB SSD, i7 4650U (MS surface pro 3), Focusrite Scarlet 2i2 (driver V3.1.10), Novation Impulse 49. 2 external HD's. Sonar Platinum x64. Is this sufficiënt?
 
I was hoping this to be a known issue with an equally wel known sollution or workaround.... How about the missing MIDI notes that "unmiss" when freezing? Doesn't that help to analyze my problem. Its like having ghosts in my system.
 
I have been using DAWs for over 20 years I know how stuff is supposed to work. I am new to Sonar so I assume my knowledge of Sonar is my bottleneck.
 
I "fixed" the issue to making a click MIDI track (A rim triggering everey beat). That workt correctly appart from missing some beats. Not ideal. I have the same problem in a new song I started for testing. It says 4/4.
 
Thank you guys for replying even when you got your new toys (SPlat update) awaiting you ;)
 
Thanks,
 
Reza
 
 
 
 
 
 

Okay, something deeper is definitely going funky. Your specs look good and if ain't a time sig issue (and combining that with dropped notes) I'll defer to the smarter doods like scook. However if you don't get it all working properly I would certainly not hesitate to call/email tech support (I would email them and open a support ticket, write down the ticket number then call the referencing the ticket... that way they have all your specs and problem details on screen and get straight to solving the issue).
 
It's the dropped notes that is bugging me in conjunction with the metronome. Sounds like data is being choked out somewhere. scook probably gave you the correct first path to explore (he usually does).
 
Good luck and update the thread so if anyone has similar issues there is a documented answer (and I'm curious as to what's going on myself).

Thanks Guys,
 
Installing the updates now, will report back on my findings ASAP.

rezab
 
I changed it back to 250 msecs just to be save or should I go for the lowest possible settings?
 

There is no advantage to running a very low MIDI playback buffer. The downside of too small a buffer is missing notes. The downside of too large a buffer is a slightly longer delay when starting playback.
 

rezab
 
Sonar is behaving a lot more responsive (at least on the two heavy projects) I have CPU overhead now as before the update my system would hang from time to time cause of the audio engine overloading/stopping . (I checked my latency buffers to be shure, It was set at 4096 to get the max. Now I set it at 1024 with some overhead.)
 

running extremely large or small ASIO buffer setting can be a problem

Thanks,

As you might have expected u had to change the buffer to 500 msecs. My system seems to behave properly now.

Its a small thing to fix but incredible annoying to live with. Thanks

I still feel the update made Sonar smoother/run faster.

@scooc what buffer Size do you reccomend?
So when hitting max cpu i should go with bouncing instead of increasing buffer Size?