dan le
Hey guys, remember CJ used to say it is the driver.
And he is right I think.
Left my 3 Delta 1010s 3 weeks ago for a new interface, and all the problems I had that I thought had to do with either Sonar or something else, disappear.
There is something weird going on with the old and defunct drivers.
So I feel guilty now for blaming Sonar (silently, of course at my studio) all this time.
And to CJ my man, you are right, never thought of you as a genius. But you are. You are ahead of your time.
dan
In my case, I don't think Cakewalk was to blame for my Dakota problems. They went the extra mile by contacting me to see if I could coordinate some exchange of information between Frontier Designs and them so that they could fix the problem, (I'm guessing) at some time in the future. But at that time it was clear to me by the lack of communication from Frontier that their hardware line was on the endangered species list and doomed for extinction. So maybe SONAR exposed a deficiency in the Dakota drivers or the drivers exposed an issue with SONAR. Who knows for sure?
To keep my work schedule, I switched to Studio One and took the same gear, same audio files, same plugins, same outdated soundcard drivers and finished the track as well as continued the project with other songs.
Does that imply anything? I would say, No. I have Samplitude Pro X, Studio One, Sonar X3, Pro Tools 10 and Pro Tools 11 on my brand new machine and I have the superhuman ability to crash every one of them at some time or another.

So I'm of the opinion that if you aren't crashing something, you aren't pushing the boundaries of your system and you are a DAW Wussie and you work on safe, little bitty 8 track projects with no plugins. <Just joking>