The audio interface is crucial because it's essentially a computer peripheral. I'm shocked at how many people use aN internal sound card with ASIO4ALL and then wonder why they have problems...that combination is like driving a car with the parking brake on.

Anderton
The audio interface is crucial because it's essentially a computer peripheral. I'm shocked at how many people use aN internal sound card with ASIO4ALL and then wonder why they have problems...that combination is like driving a car with the parking brake on.

while it's no magic bullet that works for everyone, it's not guaranteed to cause issues, which is always the implication on these forums, and it's definitely worth a try if your audio device doesn't have it's own asio driver... if you check the history at http://asio4all.com/ you'll see there have been specific issues with sonar in the past, but not recently... anyway, the op never mentioned asio4all, that was bob ;-)
good luck!
/fwiw

pwalpwal
 
while [ASIO4ALL is] no magic bullet that works for everyone, it's not guaranteed to cause issues, which is always the implication on these forums, and it's definitely worth a try if your audio device doesn't have it's own asio driver.

Yes, I usually add that disclaimer however in this case since there is a problem, it seems if ASIO4ALL is present, that would be a good place to start. But it's also worth noting that if ASIO4ALL is installed, it can still interfere with dedicated ASIO drivers for specific interfaces even if ASIO4ALL is (theoretically) not in use. I would suspect the greatest odds for success with ASIO4ALL occur if there are no other ASIO drivers installed.

yeah the op never mentioned asio4all (bob did) - if a soggy melon is present that could also cause trouble... 
i've had asio4all installed alongside edirol ua-1000 asio drivers for years, no trouble, go figure...

it's also worth noting that if ASIO4ALL is installed, it can still interfere with dedicated ASIO drivers for specific interfaces even if ASIO4ALL is (theoretically) not in use

i find this the most curious repeated statement - how could one driver "interfere" with another? it might be worth posting this assertion on their forum to find out?

I suppose its a collective wisdom from many years of experience. I have seen too many people using ASIO4all also have some issues. When those having problems do remove it magically things seem to work better.
 
That doesn't mean some do use it without any trouble at all. I think one big reason we often recommend not using it is most audio interfaces that are bought for music creation have good drivers that work. Further because Sonar supports all windows audio drivers the need for using it with Sonar seems limited. No one is able to say with Sonar that its needed at all.  Cubase for example may need it. Sonar doesn't.  

ASIO4ALL did nothing but reek havoc of my system and all it did was crash.
it ran okay on windows xp years ago, but I tried it as a GNC supplement on windows 8
and dan near gave me hermmy's.
 
there does seem to be an ever so recent issue though with sonar crashing when not having a soundcard connected.
not sure what this about. possibly a setting in device manager / soundcard.

On the very rare times I forget to turn my audio system before running Sonar all it does is remind to do so. I have to restart Sonar to account for having my audio up and ready but no big deal there. 

pwalpwal
i find this the most curious repeated statement - how could one driver "interfere" with another? it might be worth posting this assertion on their forum to find out?

I know this can happen because I was doing a presentation for New Bay Media, and there was another presenter who had just installed drivers for a new interface (a TASCAM US-366) on his laptop. He had previously used ASIO4ALL on the laptop and it was installed. He had to set the latency at 1,024 samples for the US-366 to avoid crackling, and he just assumed the 366 had horribly written drivers. Interestingly I was also using a US-366 on my laptop, but was getting about 18 ms of latency. When I saw he had ASIO4ALL on his machine I uninstalled it, and then he got the same performance with his US-366 as I did.
 
Why? I have no idea. I've mentioned this to a few other people and some of them recall having similar issues happen, albeit rarely. Granted this was a while ago, maybe there is a new version of ASIO4ALL that solves this but to me, the optimum situation seems to be:
 
If you don't have dedicated ASIO drivers, use ASIO4ALL. 
If you have dedicated ASIO drivers, don't use ASIO4ALL. 
 
At one point I had ASIO4ALL installed on one of my laptops and the only problem I had with it was no matter what I set the latency to, eventually there would be crackling and dropouts. If I changed the latency, even if I made it faster, the problem would go away but then it would always happen again 5-10 minutes later. I've used ASIO4ALL in many setups over many years, and I'd guesstimate that it was fine 25% of the time, and problematic 75% of the time.

John
On the very rare times I forget to turn my audio system before running Sonar all it does is remind to do so. I have to restart Sonar to account for having my audio up and ready but no big deal there. 

it used to do this with me as well, but now for some reason, it wont even go that far. it just crashes.
no big deal though. like you i don't often remember not to turn on my system/audiocard.

pwalpwal
yeah the op never mentioned asio4all (bob did) - if a soggy melon is present that could also cause trouble... 
i've had asio4all installed alongside edirol ua-1000 asio drivers for years, no trouble, go figure...

it's also worth noting that if ASIO4ALL is installed, it can still interfere with dedicated ASIO drivers for specific interfaces even if ASIO4ALL is (theoretically) not in use

i find this the most curious repeated statement - how could one driver "interfere" with another? it might be worth posting this assertion on their forum to find out?

Apologies to ALL, for any confusion my earlier question to the OP may have caused, regarding ASIO4ALL.
 
Here is the text from my earlier list of questions to the OP (of which ZERO were answered by the OP):
 
"3) I think I saw in one of the above posts, that you have done an install of ASIO4ALL.  IF that is correct, am I to understand you do not currently have a separate dedicated audio interface for your system, at this time, and that is why you are running with ASIO4ALL?  OR, do you actually have an actual audio interface, and if so, which exact one, and what driver levels is it running on?"
 
So - in the above question, I was soooo tired I did not go back up and read the entire post again, and that was why I indicated that the OP MAY have installed ASIO4ALL, and then based the next sentence on IF that was the case.  I also had asked specifically what actual audio interface was being used, as well as for specific information as to what driver levels the potential audio interface was running on.
 
I had asked the OP the above, and about 8-9 other questions, and got ZERO response to a single question.
 
We still do not know if the OP actually DOES or DOES NOT have ASIO4ALL installed.  He did indicate in one of his posts, that he had tried multiple driver modes, and his own wording included trying ASIO mode, in addition to the others, without success.  IF the OP has no audio interface, and does not have ASIO4ALL installed, then where in the world would he have gotten ASIO drivers to try as the Sonar Driver Mode?
 
There have been, I believe, multiple folks who have asked for some information, and so far the OP has not provided much, if any, of the requested information.
 
When the OP wishes to actually engage in figuring out what is going on, and willfully responds to questions about his system configuration, then I will stand ready to assist.  Until that happens, NONE of us can help this individual get his stuff straightened out.
 
To the OP (Original Poster of this thread): If you really DO wish assistance to your issues, I believe there are plenty of qualified folks here in the Sonar forums that can assist with getting to the root of your issues, and quite likely come up with some sort of solution for you.  That CANNOT happen if you do not engage in this thread, responding to questions about what you have done, what you have running, and what you even HAVE for hardware.
 
Bob Bone