SONAR Locks up! Help!

[Aaron Cheney]

Well, I waited, and waited... until version 1.3.1 to take the SONAR plunge. I figured by then the bugs were worked out. Wrong.

Here's my problem....

SONAR was working just fine on my sytem (Win 98, Echo Darla 20, 256 RAM, pentium II)
This morning I was humming along just fine.
Then I needed to patch in Gigasampler. I started GS, called up the patch I needed, then opened SONAR from within GS. The GS patch played, but all the audio in my project shut off. Nothing.
I closed everything back down and reopened SONAR alone. Still no audio.
I verified that Multi-client drivers were enabled. I verifed that GS and SONAR were using different output drivers. Tried it again. No audio playback.
Reboot the machine. No playback.
Reboot the maching. SONAR locks up as it's opening the project file. It gets to about 2% and totally locks up the machine. Tried it again. Lock up.
Re-install SONAR. Reboot. LOCK UP.
So now I try to open other projects. THey get to around 2% and lock up.
Now I try just recording from the default project you get when SONAR opens. LOCK UP.
I went pack to Pro Audio 9, still installed on the computer. Works beautifully (as it has for years, stable as a rock).
What the heck?!
Aaron
http://www.aaroncheney.com

 

[Sus4]

Hmm... I hope that Sonar isn't as bad for MIDI as I have found Pro Audio 9 to be. I'm was just going to upgrade to it to get around constant lockups and blue screens in Pro Audio 9 with my MOTU interface drivers. Welcome to Cakewalk software! I've been using it since the beginning and I haven't seen a version yet that isn't buggy, sounds like Sonar has it's share as well.

 

[tcdave]

Sonar Locking up

I heard that Sonar is the most stable audio/midi software on the market. I have had PA9 and Sonar, I have yet to experience the problem of my computer locking up.

tcdave

 

[tvaillan]

let me throw this at ya...

say you recorded something on a specific chanel of your soundcard. Now usually, most people have the choice of several input devices. Bear with me ..

If you should happen to install some kind of virtual synth driver or something, then the order in which you pick input/output chanels can change.

Whereas where you had the choice of :

XXX Midi Left
XXX Midi right

Now you have:

YYYY Midi device
XXX Midi Left
XXX Midi right

Now when you load your project having changed your system configuraton (more i/o devices) .. is Cakewalk smart enough to recognize the change or will it puke on ya?

If you restored your driver configuration to it's original state, would you not be able to load your project without it dying at the 2% mark?

Have you tried removing your drivers, loading up sonar in a bare configuration, then loading your project to see if it pukes?

Have you tried removing the gigasampler stuff?

 

[Aaron Cheney]

Well, after monkeying around for quite a while I have it working again, however I never really figured out what was causing it, so it's bound to happen again.
I uninstalled Sonar and then reinstalled it. Then, after re-booting several times I finally managed to get it to actually load projects, but it wouldn't play them. It just stopped playback immediately after I hit the space bar, or it would play with no audio.
In the mainn project I had been working on, I had archived and hid all the MIDI tracks that I had already converted to audio. Out of curiosity I "showed" them all again, and the track that I had set the GigaSampler up on when Sonar went gaschintz was still set to GS. I switched it to my Alesis keyboard and hit play.
Viola! It plays. Obviously GS and Sonar are at odds somehow. Leaving all the settings the same I went back to PA9.03 and set up GS to play on a track along w/ my audio, and it's just fine, as it has always been.
Somehow GS and Sonar don't get along under Win 98 it seems.
Aaron
http://www.aaroncheney.com