rfreeze
The reporter did ask and I told it yes.
 
Delta66 ASIO
 
Don't waste a lot of time.  My hardware is rock solid with Reaper.  I'll pick back up with that until I see some maint releases for Sonar.  I'll just make sure not to trust it to quickly next time.

Might be rock solid with Reaper but could be causing Sonar to crash. It's different software maybe making different procedural calls and code to access the driver, or even windows library routines getting the way. I would definitely check you are on the latest driver version and firmware, and make sure you are on X3E, and run Windows update everywhere.
 
Otherwise you are probably looking at plugins.
 
Cheers...

Anderton

rfreeze
The only plugin in the project was a bypassed copy of the tempo delay that came with X3.
 
I was working with the comp tool when it poofed.  I'll bet the $80 I wasted upgrading to X3 that the crash has to do with the comp tool.

Was it the Cakewalk Tempo Delay or the Blue Tubes one? The Cakewalk one is an old DirectX plug-in. In fact it will throw a DirectShow error under some circumstance I don't recall right now, something like bouncing to clip in a mono track because it's a stereo effect. 
 
I'm not trying to minimize your frustration at having something go wrong. I understand what it's like to lose work. However, as mentioned I think the work probably isn't lost, and if you used the Cakewalk Tempo Delay, it's a DirectX plug-ins - which has been a "zombie format" ever since Microsoft lost interest several years ago, and only remains supported in a few hosts primarily for backwards compatibility. You'd be better off with the Blue Tubes if that's not the one you used.
 
You are not the first person to have this kind of problem nor will you be the last, but many times relatively simple solutions are found through the experience of people on this forum. 

CakeAlexS

rfreeze
The reporter did ask and I told it yes.
 
Delta66 ASIO
 
Don't waste a lot of time.  My hardware is rock solid with Reaper.  I'll pick back up with that until I see some maint releases for Sonar.  I'll just make sure not to trust it to quickly next time.

Might be rock solid with Reaper but could be causing Sonar to crash. It's different software maybe making different procedural calls and code to access the driver, or even windows library routines getting the way. I would definitely check you are on the latest driver version and firmware, and make sure you are on X3E, and run Windows update everywhere.
 
Otherwise you are probably looking at plugins.
 
Cheers...

The BT Tempo Delay was bypassed in an empty track that was not involved in the comping that was going on at the time.  It is the only plugin in the project.
 
X3e, Win 8.1 fully updated.
 
I appreciate that a card can cause problems with one piece of software but work fine with another.  My hardware is my hardware ... Delta66s have been around forever and have worked fine forever - with performance that is difficult to match with modern interfaces - at 'reasonable' cost.
 
BTW, my last takes are nowhere to be found.  That's not a big problem though - I enjoy playing my guitars.  :)  The real problem is time lost working thru the takes with the comp tool.  Now, if I was paying for talent, it would be a different story.
 

Useful information, the plug-in wouldn't cause the problem if it was not inserted in the track and not the DirectX Tempo Delay.

Argh, I still occasionally get crashes like that. I just had SONAR hang on me on saving, luckily I had a fairly recent copy I was able to reconstruct from. It's very frustrating. 
 
One thing I like to do is try and move forward in small, like steps. So, when I'm using Melodyne a lot, I'll make sure to bounce all the clips down and then save. If I'm doing Audiosnap work, I'll bounce them all too and then save. Of course one doesn't always remember that in the heat of the moment when you've got momentum going.
 

wicked ... that's pretty much where I am.  I have a lot of years with Cakewalk stuff, so I generally save often  :)  To be fair, I have to say that's actually good practice no matter what software you use.  Like you say though, you get something going, you get excited and start thinking about music instead of gear ... that's when it happens.
 
I'm even beginning to think that unsaved data may somehow be at the core of these crashes  ;)
 
Is there a way to trigger actions?  For example, have recording arm a trigger to initiate a save automatically when the transport is stopped.  Timer- and event count-based save triggers are just glitches waiting to happen.  But having a sequence of events trigger a save would be pretty cool.

rfreeze
I'm even beginning to think that unsaved data may somehow be at the core of these crashes  ;)

 
Actually I think you might have a point. In the words of Herman Cain "I don't have facts to back this up," but it seems that when I save, some kind of order is restored in the force and I can go on for a long time without problems. Then I think "Hmmm, I've gone on for a long time without problems, better save" and then I go for several more hours. But I do push SONAR pretty hard, so maybe I'm just lucky.
 

Is there a way to trigger actions?  For example, have recording arm a trigger to initiate a save automatically when the transport is stopped.  Timer- and event count-based save triggers are just glitches waiting to happen.  But having a sequence of events trigger a save would be pretty cool.

 
Not quite, but auto-save saves automatically based on either elapsed time or number of edits. A few people refuse to auto-save because they don't want to "overwrite" something without their knowing it but that's incorrect, Auto-save creates a separate file and doesn't overwrite anything. So typically, I'll "save as" with a suffix after major changes (e.g., mysong01, mysong02, etc.) with auto-saved files handling things in-between. Although I do this as "crash insurance," it seems like 95% of the time the way it ends up being used is when I decide that an earlier take I did was better.
 

Pretty unrelated, but I love that Bluetubes delay. Using it on mixes currently for vox. Instant Elvis! :-)

rfreeze
 have recording arm a trigger to initiate a save automatically when the transport is stopped.

It is possible to script a stop+save hotkey using AutoHotkey, here is an example bound to Windows+s
#s:: Send,{Space}^s

That's a really good idea scook.  Not as cool as integrated event-based scripting, but I already have AHK bookmarked from reading your post(s) in other threads.