Can a project file become corrupt and cause Sonar to drop Drivers?

hmm- I have not had a corrupted cwp file (cakewalk project file) in years. There were a few versions that were bad with this, especially if autosave was on, but I havent seen them, again, in years.

You situation definitely seems unorthodox.

What are your computer specs, namely your audio interface or sound card?

Lance

HSCIII


I'm going to try to describe the environment under which my issue(s) is occurring


I was  manually versioning my first real project/song in Sonar. I had been slopping in creating instances of soft synth's i was no longer using and thought i had deleted  the no longer used instances.
The project started to take a really long time to load and I would get message about 5-6 midi drum patterns not being found; I would have to ok  each of these messages 3-4 times.

I then realized I still had too many instances of Session drummer in place and deleted all unused

At some point, Sonar crashed and reopened in recovery mode. I wasn't prepared for the choices to make, and am not sure what i selected but  the project loaded without the plug ins. This not an issue.

But since then I have issues with Sonar losing/ loading the drivers when I load any version of this project. And after that, no project will play

• Today i have reloaded my sound card drivers 4-5 times.
• I have opened and closed other projects without any issues ( prior to accessing the project in question)

• I have unloaded the midi patterns in all  instances of the drum synth but  Sonar crashes at some point when I go to save this verasion of the project

• I have gotten one error message about the   session drummer 64 saying it could not be opened, but this has only happened 2 times and the program has since loaded in projects and worked correctly.

My questions are
      How exactly does Sonar establish and maintain the driver associations?

Is it dropping them from my registry?

Are they part of some text config file sonar read when opening every time?

The Drivers are working for other programs when i have this issue, but in the preferences ,I can not even select them;I have to uninstall and re install

I have been using this version of sonar for a couple of moths and this is a new issue.
It seems like it is related to the one project.

I'm willing to start over if necessary. I did look to see if I could export the midi tracks so I could import them into my new project, but no options  that would do this seem to be enabled in the file menu 


Any thoughts or similar experiences?

Hi HS,
 
One thing I always do when I install soundcard driver is to allow Sonar to create a new aud.ini file. 9 times out of 10 this fixes just about all my issues or weird anomalies and I seem to do this once per year or two anyway whether I get a new soundcard driver or not. But that is what I would try first just to see if it helps anything. It won't hurt anything, that's for sure. I'll tell you how I do it and you can try it if you want.
 
Shut down Sonar completely. Find a file called aud.ini or depending on what your system is set for, it may just say AUD. Mine is found on Win 7 (for the 32 bit version of X1) here: C:\Users\Danny\AppData\Roaming\Cakewalk\SONAR X1 Producer
 
What I do here is I right click on this file and select rename. I change the A in AUD to an M so it says MUD.ini. All this does is back up my original in case I ever need to revert back or check on a few settings that AUD.ini doesn't need to physically run Sonar. Like it may have some folder options in it that I customize....but that's a discussion for another time.
 
So you make that change, and then close out of all windows there. Then open Sonar and what it will do is, it will create a NEW file for you here called AUD.ini. It profiles drivers and sets everything up. I can't tell you how many times this has fixes little weird issues for me. If I ever start experiencing weird things where nothing else I try can fix them, this usually does it unless of course there is something serious wrong to where I just know AUD.ini won't fix it. But this really helps with audio and other issues you may experience in Sonar. As a matter of fact, in some situations for me, this improved things so much, it made Sonar work like it was brand new again.
 
Now, you may have to go into your Sonar preferences here and adjust a few things. So make sure after you do this, that you take a look at your settings and make sure the right timing and playback drivers are selected....de-select any drivers that are not being used in the drivers tab, check that your folders are set to the right drive for audio etc. This new AUD.ini uses all the Sonar defaults so you'll definitely have to make a few system specific changes here. It may default to 16/44 instead of what you use which may be 24/48...stuff like that may need to be changed.
 
If you have your audio on another drive, you'll have to change the folder options and point it to that drive. These are the little things you may have to alter. But it will profile your card drivers the right way and like I say, you should really do this with each update to a soundcard....and even if you update a version of Sonar just to keep things tight. Honest this little trick can make a world of difference in how Sonar performs *MOST times*. I can't promise you it will fix your issues, but that's definitely where I would start if I were you.
 
If the new AUD.ini file fails and you're worse off than you were, close Sonar, go into the directory where you found AUD.ini, delete it and find the one I made you name MUD.ini. Right click on it, select rename and change the M back to an A and you'll have your original configuration back up. I hope this helps...but if not, I'd recommend a full uninstall of Sonar while removing all registry keys and folders and then starting fresh if you still have this problem. Good luck!
 
-Danny

A while back I had a few funky plugins that used to cause runtime errors and crash Sonar - this was on 8.5.3. Re-opening Sonar, I would have no soundcard outputs visible - basically it was as if the drivers had been deleted. A re-boot would fix this. So to answer your question yes I have seen this. I'm using an Echo Layla 3G interface. Something else, uncheck the 'share drivers with other applications' box under preferences. This may help.

AH, why didnt I think of that - great tip Lance, cheers! You are right though, I'm yet to see this happen yet in X1.

The only issue like this i have lately is a Sonar crash when auditioning different sounds for SD3.If I'm a little too quick jumping around checking out one sound after another, Sonar hangs then crashes.60% of the time a reboot is needed and a small % of the time it doesn't find the  sound card drivers at which point I can do the recommended AUd.ini file move, or unload and reload the sound card drivers ( a longer way to go b because of the reboots)