Sonar recently started sh*tting the bed. everything seems peechee til i hit record & then things start glitching out every couple measures. i been running thru my settings making sure i didnt tweak something in a moment of demonic possession. i'm way overdue for a new system, but this old thing was worked great for many years. i'm wondering if the word clock might be throwing monkeys in the gears. i tried switching it back to strictly adat & it seemed to have no effect on the glitchyness. any tips on where to start with the trouble shooting?
when Sonar has been used for a long time, the picture cache gets full, full, full. sometimes delteing all the picture cache contents(Sonar will rebuild pictures for any projects that require it) really helps....
Ha - wow. What a blast from the past. Not that it matters much but here's an update from me on the subject.
I have given up on Sonar and made the switch over the Samplitude (at the beginning of this year) and am not looking back. I have the latest version of both programs installed and running on my machine. There is no contest. Hands down Samplitude runs like a well-tuned BMW and Cakewalk runs like a broke down Chevy. Samplitude ran great out of the box with almost no tweaking needed. Not a single crash in over a month of serious recording.
I had been back and forth with Cake TS so many times. The answer was always the same: it's your soundcard. So I took that to mean they simply didn't know wtf was going on and decided enough was enough. I would abandon Sonar for good except I now have many years of projects built up with Sonar and a few still in the works that I'll finish up with. But all new projects are being done in Samplitude. I finally got my head around it well enough to run sessions with confidence. I can deal with almost any software quirk but not crashing. That is a deal breaker.
Anyway, if you're having nagging problems with Sonar, dump it and get Samplitude.
thanks Gary. i'm running a defrag & some other maintenance on it, if that has no effect i'll drag it out to OC next time i get a chance.
you still at PME?
finally worked it out on my own. the "playback timing master" setting in sonar had somehow managed to unpopulate itself.
i reclicked output drivers, reopened the program, enabled scope as playback timing master & once again all is right with the world.