The TS-64 Transient shaper will induce latency.  Try pressing "E" to disable all FX, or delete the TS-64, and see if latency improves, then add the TS-64 when you've finished tracking.

The problem might be the PCI slot on your new MOBO. I had similar issues. Newer MOBOs tend to use a bridged PCI slot and it can slow things down. I personally just bought a more modern interface but obviously not everyone wants to drop the cash. I did manage to get my old interface working better after doing a bunch of system tweaks that were recommended by Cakewalk support. Fill out a support request form/email with all your system and interface details (this includes the make of your motherboard, what kind of drives you are using, RAM, etc...) and describe your problems. Then write down the ticket number the email generates and call up support referencing that number. This way they have all the details on screen and can get right down to the issue. I would normally say reduce your buffers to get rid of the latency but you said you are getting crackles as it is so that might just make the crackling worse... but it's worth a shot. As was already pointed out make sure you have the latest drivers for your system and interface installed and check all your software for any updates/patches as well. Good luck.

ro_ca_@hotmail.com


Processor: Intel core 7-3770 CPU @ 3.40 GHz
Memory: 8.00 Gb
64-bit Os
Win 7 Pro, Service Pack 1
Drive: WDC WD5003AZEX-00K1GAO ATA
Video: Intel Graphics 4000
Soundcard: M-Audio Delta 1010 in PCI slot, Driver ver 6.0.8; sample rate = 44100, ASIO/WDM buffer size=512 samples (same card as I used for CW9, though I did update the driver)
Sonar X2 Studio (X2 build 306) - don't know if 32 or 64-bit
Sampling rate=44100
Buffers in playback queue=2
Effective latency=11.6 msec
Playback I/O buffer size=128 Kb
Record I/O buffer size= 256 Kb
Plugins: FX Chain "Kick Drum Life 2" (Sonitux Equalizer, TS64 Transient Shaper) and Cakewalk Delay (on Vox)
No other programs running; computer has not internet connection, is dedicated solely to recording.
Not sure about direct monitoring, how do I find this out?
The project has 10 audio tracks (including guitar part I recorded yesterday)

Thank you SO much for the detailed reply.  As jb101 says, do try hitting the 'E' key on your computer keyboard to temporarily bypass all effects to see if that isolates the issue to a plugin. (hitting 'E' again will enable them all again).

I forgot to ask, are you using ASIO or WDM as the driver mode in Sonar?  Try using ASIO - you can change that in Preferences.

The direct monitoring would mean monitoring inputs to the audio interface, such as a guitar, using a feature on some interfaces, instead of monitoring the OUTPUT from Sonar.  This results in hearing near-zero latency from the direct monitoring, followed by the processed sound from Sonar, which will have some latency, resulting in an annoying echo sort of effect.

Bob Bone

im with beepster, the issue might be with your pci card.
read his post carefully.

I would download the X2a 64 bit update (build 351), it fixed a lot of my problems...

Tried bypassing efx with the E key, no joy.  I'm currently using WDM mode, though did try ASIO mode - made no difference either way.  As to "direct monitoring", still not 100% clear on that.  My guitar is plugged into my amp which is mic'd.  Mic goes into my Mackie mixer, which outputs directly to the Delta 1010.  All Sonar tracks output to Ch1/2 of the 1010, which then goes back to my Mackie then into my headphone amp.  Are you talking about somehow monitoring from the 1010 BEFORE it hits Sonar?

Sad reality is PCI is now a legacy connection so it doesn't get the attention from comp parts manufacturers it used to. They've moved on to PCIe and now those of us with quality functioning gear that relies on PCI have lost some power. I was pretty annoyed that after all my research into my comp build that the PCI slot was substandard. The good news though is that many folks around here are still using their 1010s with good results. Like I said it might just take some targeting tweaking. I used the Sweetwater Optimization Guide (but that includes some tweaks not recommended by Cakewalk so it's best to contact them for more details). There are lots of other optimization guides out there too like from Focusrite, SOS and I think there is a blog post somewhere here on site as well.

The other thing that you should look into is that 32 vs. 64 bit installation. Click the Sonar help menu at the top of the screen and select About. It will give you details on what installation you have running including the 32/64 bit status. If you are indeed running 32 bit you should install the 64 bit version to make better use of your RAM. You are using a heavy duty plug (transient shaper) while recording and it might be sucking up all your RAM. Not sure if this will cause drop outs but it's not ideal. You should actually remove it or freeze the track it's on until you are done tracking. That might help get rid of the crackles and hopefully then you can reduce your buffers to get rid of the latency. Generally you want as little plug ins processing signals as possible while recording and reduce your buffers then increase the again for mixing/adding effects.

You should still get a hold of support though for those optimization tweaks. They will help any system immensely even if it turns out not to be the cause of your problems.

ell, five months after buying my new computer and two months after buying Sonar X2 studio, I thought I finally had things up and running and figured out, and could try actually recording something.  Silly me!!

Latency comes from two sources... and only two sources.

• Your audio interface:

Set the ASIO buffer size as low as possible for minimal round-trip latency.
Better audio interfaces provide lower round-trip latency.  
ie:  The best units yield ~5ms total round-trip latency at a 64-sample ASIO buffer size/44.1k.    

• Latent plugins:

Plugins that use look-ahead processing (often "mastering" types of EQ/Dynamics), convolution reverb, etc... add additional latency.  
If they're inserted ANYWHERE in the project, Sonar delays all other audio (by an equal amount) to maintain sample-accurate sync. This is referred to as Plugin Delay Compensation.
When tracking, avoid using latent plugins... or in the Control Bar, use the global PDC bypass when tracking (making sure to re-enable it when you've finished).

There is no other source of latency.  IOW, Sonar itself is not a source of the 3-second latency to which you refer.

As far as glitches/etc, that's down to the configuration of your new machine.

Step back, take a breath, and think about the situation in a non-emotion manner.
You've just got a bunch of new gear.
With that gear comes a steep learning curve.
You're not going to master these things immediately (no different that trying to pickup a new instrument and expect to be playing like a virtuoso in short order).

First, I'd check your machine's DPC latency... and make sure it's performing well on a fundamental level.
Start with a rock-solid foundation (rock-solid machine)... and move out from there (software, plugins, etc).

I have the delta 1010 running fine with X2. My (cpu) system is a little older and slower than yours - I use a Q9550 chip with Win8. I would go crazy trying to record guitar at 512 samples. 

I record through X2 with the delta 1010 ASIO buffer size set to 128 samples for projects that already have several tracks recorded. (I start with 64 samples and then move up to 128 as the project grows)

If you want to do direct monitoring with no regard to buffer size - then you can do that by monitoring through the delta1010 mixer control panel. Your recorded source will not have the benefit of any plugin effects for you to listen to while recording, but you can go this route for close to zero latency. I tired this before but I went back to the 'thru sonar' approach.

Latency is largely introduced on my system through plugins. So I make sure I bypass any effects in the master buss and also bypass any resource hungry plugins or known latency causing plugs like perfect space or the cakewalk linear plugs while recording (this applies to playback tracks and busses as well). You can always do a temporary/permanent freeze of any vsti tracks. There is also the PDC button on your toolbar you can engage to compensate for plugin latency. But in my opinion that will be of little use to you until you get the buffer size lowered and playing nice with your daw - any daw.

With all that said, your answer may well be your new motherboard doesn't work well with pci cards. That should be easy to find out with a little googling or posting your motherboard specs here.

The delta 1010 is an older generation card and some day I will replace it. But the quality of sound from this card is still considered to be very good. I think it's worth a small fight to try and make it work.

Jim Roseberry

ell, five months after buying my new computer and two months after buying Sonar X2 studio, I thought I finally had things up and running and figured out, and could try actually recording something.  Silly me!!

Latency comes from two sources... and only two sources.

• Your audio interface:

Set the ASIO buffer size as low as possible for minimal round-trip latency.
Better audio interfaces provide lower round-trip latency.  
ie:  The best units yield ~5ms total round-trip latency at a 64-sample ASIO buffer size/44.1k.    

• Latent plugins:

Plugins that use look-ahead processing (often "mastering" types of EQ/Dynamics), convolution reverb, etc... add additional latency.  
If they're inserted ANYWHERE in the project, Sonar delays all other audio (by an equal amount) to maintain sample-accurate sync. This is referred to as Plugin Delay Compensation.
When tracking, avoid using latent plugins... or in the Control Bar, use the global PDC bypass when tracking (making sure to re-enable it when you've finished).

There is no other source of latency.  IOW, Sonar itself is not a source of the 3-second latency to which you refer.

As far as glitches/etc, that's down to the configuration of your new machine.

Step back, take a breath, and think about the situation in a non-emotion manner.
You've just got a bunch of new gear.
With that gear comes a steep learning curve.
You're not going to master these things immediately (no different that trying to pickup a new instrument and expect to be playing like a virtuoso in short order).

First, I'd check your machine's DPC latency... and make sure it's performing well on a fundamental level.
Start with a rock-solid foundation (rock-solid machine)... and move out from there (software, plugins, etc).

Well said Jim! If I knew you were responding I would have saved my thoughts. You had it all covered.