ok, my machine can repro this issue on a newly created file where I delete the audio. Something in my machine environment is causing this issue I am pretty sure.
 
here is how I recreated it. (recreates in safe mode too)
1. Create new project
2. Import any audio loop
3. bounce to clip
4. Save project as CWAF.cwp - or whatever you want to call it
5. Go into audio folder and delete the project audio file
6. Open SONAR
7. Open CWAF project - should get find missing audio prompt
8. select search
 
At this point my machine craters while searching the C:\Users\All users\...Programs directory. Which directory? I don't know.
 
Here is what I am wondering - is there a utility in or for windows that will show you the last referenced/scanned directory at any point or time? Something in that directory may be causing the grief and I would like to know what it is, or may be. Thoughts? 

Andrew Rossa [Cakewalk]
Looking into this...

Dan and Andrew,
 
Pls also look at this here and this one. Some more crashes with X3b when opening new and old projects, but at least in my case there are no missing audio files ...
 
Help is appreciated!
 
Thanks guys.
 

Sonar has a list of project-file types it will search for audio references. In CWAF you can configure that list. Try disabling all the file types except cwp & cwb. If that doesn't crash, maybe that's all you need. However, you can keep enabling types you might have used (bun, wrk, ???) until it crashes. In that case, you have found a file type that some other program has created, but CWAF has been told to treat it as a Sonar project.

I thought CWAF is only for cleaning harddrives by removing no longer used audio files. I wonder how CWAF settings would impact how Sonar itself looks for audio files (I just RTFM but it did not tell me anything in that respect).

It's interesting, though, that CWAF got an option labelled "Don't show Corrupt Files in Main Display" ... what's that about???

I worked with TS yesterday with CWAF and nothing helped. Awaiting a word from TS on where we go from here.

Hi Conley


My view is either your virus scanner is getting in the way or this is indeed a Sonar bug as you've nailed down the specific steps to repro.

Either way I suggest you do a full "check your drive for errors" (chkdsk) on all your local hard drives, and check out your virus scanner if you are running one (if you aren't you should be), and running Windows update might be a good idea as well.
 
Oh and does it crash when you run Sonar as an admin user?
 
Thanks...

Alex, this fails in Safe mode too. The virus scanner is not in play there.  In normal mode, I did run as administrator as well as having the virus scanner disabled. :) that was one of the first things I did.
 
Thanks though!

Thanks Conley - Just try this then I suggest before Cake gets back to you (always a worthwhile exercise anyway)...
 
check your drive for errors" (chkdsk) on all your local hard drives ... and running Windows update might be a good idea as well.
 
 

thx again :)
It is a solid state drive and no errors found. It dies in the C:\USER...\...Programs directory, but can't figure which one.