my first serious problem -X1 didn't start any more

Yesterday evening, I saved my project, no problems.
X1 32 bit, Win 7 64 bit, 42 tracks, some soft synths, and effects, nothing extra ordinary.
Today, I wanted to open my project again: project could not be loaded, a message related to cyclone appeared, X1 crashed.
Blue screen, after trying to start X1 again.
After booting the system, start X1, create a new empty project: X1 crashes.
Next reboot, starting X1: crash. Without doing anything, just starting X1!
Don't know how may blue screens and reboots I had.

I found C:\Users\<your user-name>\AppData\Roaming\Cakewalk\SONAR X1 Producer\AUD.INI had the latest time stamp, so I renamed it.
X1 started again, creating a new empty project worked fine.
I found out that my main settings seems to be still available.

Open yesterday's project by holding <shift> when pressing OK, dismiss cyclone, project opened, puuuhhh.

This heavy process made me feel a bit uneasy.
What happened here?

I can live with some bugs, as long as I can handle those.
But that was nearly a real "no go", a "show stopper".
What if I hadn't found the corrupted file AUD.INI?
What if I couldn't dismiss cyclone as it had been a major part of my project?
Is there any magic key combination that start X1 in a "save Mode"? I tried  shift, alt, but no magic behind these keys.

Till now I was quite happy with X1, but this issue made me feel doubtful.

Did you by any chance have the Sonitus delay in use in the project?  There is a memory leak in the version shipped with X1.  If so there are a number of threads dealing with how to solve this. 
If it was in use (Sonitus delay) the memory loss may have prevented the proper saving of the file during the the Cyclone preset/settings saving resulting in the corrupted file.

lorneyb2


Did you by any chance have the Sonitus delay in use in the project?  

Thanks for your support
And it's a good idea, but no, I didn't use  sonitus delay in my project.

Something with cyclone went wrong. The message told something about a stack problem.


But anyway, I used different other daws before and never went into such a situation.
I'm sure that I'm still doing some "do nots", as I also try out different new things.


But never should a user run into the  situation that one just  can't  start the application.
That's a kind of software quality, "robustness".
And don't get me wrong, X1 impresses me, but now I've the concern to come into a situation, where I might find no workaround.

lorneyb2


Hopefully the X1b will solve some of these issues.

Do you have the Scan VST on start up enabled?  The aud.ini getting corrupted without that in place wouldn't be expected.  I would assume it would be read only unless you had made some changes in preferences  the last time you had had the project open.

Other than that it could point to a problem on hard drive that is developing.  May not be a bad idea to do a check disk to see if there are some disk problems. 

VST scanning is not enabled at startup.


Right now I could work as usual.
I believe it was caused by a bug but I'm not able to repeat the necessary steps.
The only loss I see is my screen sets, they are all empty. No big deal to create new ones.

But I wish there were a <Shift> start, to start X1 in save mode, that means
X1 asks for: - reset all X1 ini files to the last working  configuration.