So, I'm getting repeatable crashes on one project. They happen if I open the project, and click a bus channel on the console view. My inspector tries to switch to the ProChannel view on the selected bus, briefly displays "console emulator failed to load" or something close to that, and SonarPDR has to close. The error reporter doesn't even start. Just boom, exit.

How do I make this into a testable project file (the project has like 13 GB of audio data even though it's relatively simple) and where do I send it?

Try opening the project without console emulator and then saving it under a different filename:
http://forum.cakewalk.com/Open-Sonar-in-safe-mode-Solved-m2524512.aspx

http://www.digifreq.com/digifreq/tip.asp?ID=10

It works fine if I click the bus from the track view first. Saving it under a different name doesn't solve the issue.

> Saving it under a different name doesn't solve the issue.
The idea was to remove the console emulator first before saving it again so it wouldn't crash when starting up. So if you can remove the console emulator, please do so (if not use my original suggestion), then save the project under a different file name. Close Sonar. Open the newly saved project, then pop the console emulator back in, save it ... see if that helps.... Cheers...

I get what you're saying but again, the project works fine if I click the bus from the track view first. Removing the console emulator will surely "fix" it but it already works, just not if I happen to click the bus from the console view first. Since this is an entirely repeatable crash, but the error handler doesn't pop up, I'm wondering how to submit the project for testing.

Send the .cwp file to Cakewalk.

Did you disable the 64 bit engine? Lots of folks have been talking about that work around.

jb101
Send the .cwp file to Cakewalk.

^^^^^^^
If it's reproducible by CW, then there's a bug to fix!   Assuming it's not plugin specific, of course.
 

> just not if I happen to click the bus from the console view first.
 
Fair enough but I'm wondering if this will fix it, i.e. this might be a corrupted project file. You don't know till you try and this will be useful information for Cake to know (Good point about switching off the 64 bit engine as well).
 
Agreed - an error handler should pop up, that is a bug in itself.

Ta