normeughdge
Another thing I wanted to mention is that If I hook this Midi keyboard thru usb straight to my computer, how does it interact with my audio interface. I noticed that the Midi indicator is not on, on my audio interface, but I hear it fine through my desk monitors and can control the volume with my audio interface.

The keyboard won't be interacting with your audio interface at all. They are two separate devices.

If your audio interface has MIDI connections built in as well as audio then you could hook up an external MIDI device such as a synth and use the USB keyboard to control that synth by setting up a MIDI track in Sonar to receive input from the keyboard and output MIDI through the interface MIDI ports. To get the synth's audio to Sonar and your monitors you also need to commect the synth's audio output to the audio inputs of the interface.

MIDI and audio are two quite different things and Sonar, like all DAWs handles them as separate data flows. MIDI is simply instructions that tell MIDI equipped devices (hardware and software plugins) what to do. For example, "play note 100 at velocity 56 now.........stop playing it now".

MIDI can seem a bit overwhelming if you're new to it. Sound on Sound (magazine) have a good set of basic MIDI articles online. They were published 20 years ago, but MIDI was well enough designed in the first place that it hasn't changed much. Well worth reading if you're new to MIDI.

The first article is here http://www.soundonsound.c...aug95/midibasics1.html

normeughdge
It seems that when I open a soft synth, and play it by itself, it plays fine! But when hit the record button and try to record with the playback of the other tracks, thats when the problem starts.

Based on this, I'm going to go back to scook's original hypothesis that this is due to Plugin Delay Compensation. When you initially open a project and/or insert a new soft synth in a project that contains a PDC-inducing plugin, PDC isn't calculated and applied until you run the transport for the first time. This is why it suddenly appears when you start recording.
 
Depending on the FX, it may be that bypassing it is not sufficient to cancel the PDC. I suggest you completely remove any FX that are likely to be causing this (notably convolution reverbs, guitar FX processors, and Cakewalk's Transient Shaper and LP-64 plugins).

Also, Focusrite has some of the best ASIO drivers out there - so we should figure out how to get you back on ASIO with Sonar.
 
Can you post your system specs?

Agree with CJ.  I go to Preferences | Drivers | ASIO buffer and set the slider to a low number (like 3) while tracking/recording to reduce latency. Then when mixing the final product, I move it back up to 6 or 7 to ensure there are no clicks or drop-outs.  In the very near future, improved computing power and speed will eliminate this two-step process, but for now, I have found this to be a good method.
 
Also,the MIDI buffer, as said above, may be something else to check.  The problem could be either or both, but having the ASIO buffer too high during recording is a sure fire way to have lag.  Just don't forget to put it back.
 
I will say that, although I have noticeable latency problems with the wrong settings, an 1/8 note at 120 BPM is a LOT; however, it could be mechanical *and* human: it is hard to play in time when you don't hear yourself right.  Some singers and musicians rush badly when latency is too high, but the reverse could be true as well.

Thank you all for the responses. Let me see if I can answer some of the things you suggested. First Mr "Zargg": Yes I've downloaded the lates ASIO4all v2 drivers. isn't the latest version 2.12? And is that the right ASIO Driver? Mr "tlw", that example you gave of, "play note 100 at velocity 56.........stop playing it now!" To me, that's like speaking Russian! I can't begin to know what any of that means. But the sound on sound magazine you suggested sounds like be a good ideal. Mr "bundlefly," Pluggin Delay Compensation sounds kind of interesting. But how do I know what plugins are PDC induced, and what do you mean "run the transport for the first time?" Also, when I record, I record raw! No effects. I apply all effects after all my tracks are recorded. Mr "dwardzalz" that also sounds like a good I deal. Can you tell me exactly what you need from me concerning my specs. Or are you saying that I should get my ASIO drivers from Focusrite? Mr "konradh" I would like to do that, but I can't seem to get no sound at all, when I try using the ASIO drivers. And I have reset my midi buffer to 500 as suggested by "scook." You all seem so advanced and  educated in this, and this all is very simple for you guys, but so confusing to me. I kind of feel I'm close to resolving this, but also feel I'm still far away. So again, if there is anything more you can tell me, please do! I deeply appreciate all your input. Thanks for all the help.

Computer specs would be things that are shown in my sig - processor, memory, HDs, other hardware etc.
 
Yes you should get your ASIO driver from Focusrite.  And sorry to conflict with some other advice regarding ASIO4ALL but, you should disable that driver - it is a workaround for interfaces that don't have real ASIO drivers.  Your device does so you don't need it.  In fact, it can cause you problems by interfering with real ASIO drivers.
 
Regarding some of you other questions - running transport for the first time = pressing play or record to start the audio engine (the part of the software that "plays" your tracks) the first time after you load a particular project.
 
When you are recording "raw" do you have effects on your other tracks?
 
The people on this forum have a collective of centuries of experience with Sonar and solving these problems.  As long as you are willing to continue the dialog with us, we will figure out how to solve your problem so that you are recording and mixing using Sonar.

ASIO4ALL actually uses WDM drivers which "appear" like ASIO. They also can interfere with genuine ASIO drivers.

Best starting point is to download Focusrite's drivers. Completely uninstall ASIO4ALL, then install the Focusrite's drivers.

MIDI latency is terrible for me when using WDM (which is what ASIO4ALL truly is). Always use manufacturer drivers first.

Thanks guys. Believe it or not, but I got the Asio4all v2 to work for the first time yesterday evening after my post to this forum. I just kept playing around with the settings and it worked! But I am experiencing some "audio dropouts." And I didn't know that the "asio4all v2" driver is not real asio driver. And since I've already downloaded the focusrite drivers when I purchased the unit, then I already have a focusrite asio driver Right? I just need to uninstall the asio4all v2?

Oh I forgot! Yes when I record, I use no effects on any tracks. I add effects after I record all my tracks.

WDM is Microsofts "generic" audio driver model and is relatively high level.  It's good for steaming audio from youtube to your soundcard or game playing or other similar situations where latency down to a few miliseconds is not required.
 
ASIO is a low level driver that effectively allows software to talk directly to your sound card, bypassing most of your OS. It will allow guaranteed low latency based on the buffer size you specify.
 
ASIO4ALL is a "wrapper" that makes WDM appear to be ASIO to software that expects (or requires) ASIO.
 
Remove ASIO4ALL,  check the Focusrite  site for the latest drivers for your interface. Install the ASIO driver (or if it's one driver, make sure it's using ASIO mode)
In windows sound settings, ensure your interface is NOT set as the default option for audio.  Let windows use the built in sound on your motherboard for everything else and keep your Focusrite just for Sonar and other dedicated audio software.