Ok so I'm using a Focusrite 2i2 and I had to download asio4all in order to use my speakers to monitor, and I have 21 tracks total for a cover and the thing is,already having latency. I don't know why it is, but I can't use just 4 plugins I need more, but when I use at least 10 the damn thing starts skipping. I have the Asio4all settings at 2048samples and 20 for the buffer but it keeps skipping. Is there any way that I can fix this issue or ?

What version of Sonar?
 
What plugins?
 
I have 0 problems with ASIO4ALL on 3 of my machines where I do lots of testing. 2048 will give you latency if you are trying to record. I drop mine down to 64 without any issues and get 0 latency and can use quite a few plugins before things start to skip for me. At 2048, I have no problems playing huge projects of more than 21 tracks. We need to check into what your ASIO4ALL settings are as well as your Sonar options.
 
That said, I'm experiencing latency with 2 plugins using the latest version of Sonar Plat with 2 tracks. I've sent my findings to Cake support but have not heard anything as of now. I switched back to the last release and all is well again. That's why I asked what version of Sonar. A few others have reported plugin latency issues in another thread. So if it's the latest release of Sonar Platinum, that *could* be your issue and it depends on what plugs are used. Do you have any other version of Sonar to try things out on?
 
This may not help you, but this is how my ASIO4ALL settings are.
 
https://dl.dropboxusercontent.com/u/4909348/Sonar%26Asio4allSettings.JPG
 

 
Hope that may help a bit.
 
-Danny

Why not monitor directly off the Focusrite, through headphones? You wouldn't need to use ASIO4All, which may be actually calling the MME driver - lots of latency there! At any rate, latency isn't your problem. Dropouts are your problem.
 
If you're getting dropouts at 2048 samples, there's probably something interfering with your audio interface. The prime suspect: your laptop's wi-fi adapter. Disable it and see if the dropouts go away. (I'm just assuming you're using a laptop, your avatar looks like a laptop user.)

Don't use ASIO4ALL, uninstall. Focusrite supply perfectly good drivers and ASIO4ALL is likely to conflict with them.

Use your line outputs from your 2i2 for monitoring.

ASIO4ALL is for people who don't have ASIO supported interfaces, the clue is in the title. And in most cases you are better off running MME in that scenario (fortunately you aren't in it).

Ok so it is best to monitor through the headphones on the asio driver for the focusrite? How will I be able to monitor through my speakers?  Also my avatar is actually a desktop hp touchscreen kinda girl heehee so no laptop there. Should I turn off my wifi then? Am I better off doing MME rather doing ASIO4ALL?
 
 

i'M ALSO using the Jamaican Plain update? I suppose a picture of what my settings and project look like would suffice:) Also when I meant monitor by speakers I meant listen to it from my computer's speakers.
 
Here is what i am working with. Do I have too many plugins or tracks? Should i nix the ASIO4all and just use the Focusrite drivers? Are my settings ok? Do I have to start my project over? -sobs in despair
 
http://screencast.com/t/AK7gs7z0J
 
http://screencast.com/t/xHhiV3iAMxJ
 
http://screencast.com/t/7kuxEVGDFa
 
 
 
 
 
 
 

Just to clarify....what the others have told you about ASIO4ALL is correct. If you have a Focusrite there is no need for ASIO4ALL. I use it because my little internet test boxes do not have pro interfaces. They have stock Realtek cards in them and ASIO4ALL works perfectly for me.
 
Looking at your screen shots, take the checks out of the boxes for "read cache" and "write cache" unless you are using an older, slower hard drive. Anything 7200 RPM or faster will work fine without those checks in the boxes.
 
Also, you can change from "Full chase lock" to "trigger and freewheel" instead. There are no promises that stuff will work, but it's how Sonar should be set up and what has worked for me on all my machines.
 
Your Focusrite using ASIO should be great for you. If you are experiencing issues after using that, like I said in my initial post....it could be an issue with Sonar. Try reverting back to the last build and see if you still have the problem. That is what I had to do until the issue is fixed for my particular problem.
 
So just to be clear....since you have a good interface, use the Focusrite drivers using ASIO mode. Uninstall ASIO4ALL as you should not need that. In my 3 good recording computers, I do not use ASIO4ALL because I have great interfaces which allow me to use ASIO. I only use ASIO4ALL in my machines that do not have ASIO sound cards. Good luck.
 
-Danny

So exactly how could I go back to the previous version? I think sonar is,a problem cause I even tried MME and the,Focusrite driver and still had latency

Well looks like I have lost all faith in sonar. As much I want to say that things were going well they became worse. I took off asio4all and when I tried to use the focusrite driver I got latency again. I tried doing MME so I could have my computer speaker as an output but the latency was truly upsetting. I'm honestly thinking about ditching my focusrite and going back to using my blue yeti plug and play. It's either that and delete all my plugins in the project and start completely over...which I'm not doing(I worked too hard on that project)

Thinking about uninstalling Sonar from my system entirely. Run time terminated it before it could even start up. I went back to the Ipswich update and still the problem was the same. I'm honestly very disappointed and hate it came to this. Finding another software will take a lot of money and right now I just don't have the funds at all. I don't have any money to put up for a computer and will not let Sonar be the cause of it dying on me.

Thanks for all the help, but Sonar lost a fan tonight. I'm deeply depressed and disappointed.

So I just deleted every plugin from the project and it "magically" cut out the dropouts and latency. I reinstalled sonar but it's taking awhile for it to start up. It sucks because the waves plugins I have are cracked from a friend, but it seems I may have to restart my computer to factory settings and erase all of my work just to get sonar working properly.

Im trying to think of other solutions, but it's inevitable at this point I suppose. I got the waves plugins because they are really good but it seems they apparently cause too much latency.this makes my workflow a lot tougher and less motivating. I have Windows10 Hp Touch smart and honestly I'm not entirely sure how to fix this. asio4all was working "OK" but not great but at least my sonar didn't freeze,every 5 minutes