Hi all,
 
Does anybody have any issues with the metronome?
 
I was tracking last night and the metreonome just started to decide on its own at what interval it would sound. I got a pretty cool groove idea out of it so thanks bakers, but how do I get it to behave as expected?
 
I tried restarting Sonar and restarting the system it didn't help.
 
Maybey worth mentioning that I have been having prob;lems with MIDI notes being missed and Rapture pro notes "hanging"(keeps on playing a certain note). The rapture pro issue I get passed by by reinsetring the instrument or by freezing and unfreezing. The missed notes are random and gets recorded when freezing a track.
 
Sorry if this is a stupid question or it has been adressed before. I have difficulties using the search box. (most other sites work fine though I use the lates IE and GChrome.)
 
Thanks

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.

Have you changed your project's time signature? The metronome plays back the "pulses" of whatever time sig pattern you have chosen. So 4/4 will have a high click on the 1 beat then three lower clicks. If you change it to a compound time sig this could end up playing back more "groovy/swingy".
 
If I am not sure what exactly I am writing and want just a straight click I'll go into the Metronome Preferences (right click on the metronome for easy access) and make sure all the clicks use the same sample. That way I can play in time but free form then change the time sig appropriately after the fact.
 
If it is out an out stuttering then you may have a playback problem which needs troubleshooting. If this is the case then you should provide your system specs, what type of audio interface you are using, driver mode, description of the project(s) this is occurring in, etc.

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
 
 
 
 
 
 

Dropped MIDI notes are almost always a sign of too small a playback buffer. Try increasing the "Prepare using nnn millisecond Buffers" setting in Preferences > MIDI > Playback and Recording. The default of 250 is often too small and increasing it to 500 or 750 fixes the problem. Some have had to go even higher.

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

I think Steve has you covered on the issue with dropped MIDI events. For the metronome issue, go to View > Meter/Key, and make sure you don't have different meters entered later in the project. If that doesn't account for it, check whether there's any difference if you have count-in disabled. What you're describing is pretty unusual.

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

Okay, I am not able to replicate the problem anymore......
 
I updated Sonar Platinum, I didn't have time to check the installations and everything so I can not confirm everything was installed properly. However the metronome's stuborn behavior disappeared!
 
To make it even more interesting, I don't have the missing midi notes problem anymore. I even (boldly) went in and tried to confirm my suspicions ...
 
I decreased the buffer to 125 msecs. No problem. Decreased to 100 a bit to ambitious (In a heavy project, does this matter?). 120 msecs good again.
 
I changed it back to 250 msecs just to be save or should I go for the lowest possible settings?
 
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.)
 
Just in case you may wonder I like to "master"/put plugins on my stereo out bus.
 
Can anybody confirm? Maybe I am a bit to oppertunistic and I will check back in a few days. But for now all seems wel and thank you for the helpfull replys:).

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