Crash after crash after crash after crash

Rough day in Sonar land for me. :( Never had a problem with X3 - even when I recorded a 7 piece band recently with lots of plugs enabled. Today I've crashed non-stop.
 
So today I decided to put together all the different ideas I've had and it's not going well. I turned off ALL plugins accept the item sin the list below.
 

• So first up, BFD3. I laid out a drum track in the Groove Editor and wrote this out as a MIDI into a Sonar track. Turned it into a groove clip and drug it out for a few minutes
• Next up was recording a rhythm guitar in Amplitube. I am LOVING this plugin but I'm afraid it might be the stability problem.
• Recorded another track with guitar for lead using Amplitube.
• Recorded a bass track direct and using Amplitube for that
• Another guitar - this time clean through Amplitube.
• Now I'm trying to do keyboards into audio ins in Sonar.

 
I have been crashing, and it's getting worse and worse. The weird thing is, I'm getting it when I have the project stopped and I'm not doing ANYTHING. I might be tuning a guitar or something, and it just locks up. If I am playing the tracks or recording, it hasn't locked up yet. Very frustrating and very confusing. I've got 64bit Windows 7 with 16GB of RAM and a Mackie firewire interface. I've got my buffers rather low for the Amplitube latency and everything sounds good - no crackles. Again, it locks up when sitting IDLE, not when recording.
 
Any ideas? I LOVE this workflow and I think I could get very creative with it, but it just ain't work'n. :(
 
 

Hmmm... lots of hits on Googling:
 
amplitube crash site:forum.cakewalk.com
 
You might want to check out some of the more recent posts for suggestions.

thanks guys. This got me thinking about drivers and I went and uninstalled ASIO4All and the driver for my Sonuus (neither of which were being used) and changed the setting to not share audio devices.
 
So far so good...

What version of Amplitude are you running? Have you checked to make sure you have all of the updates? Craig made a comment in a thread linked above about Amplitude 2 being okay.
 
An amp sim, if enabled, is running even with X3 "idle." I have never used Amplitude, but if that is indeed the culprit, what you may want to try is bouncing those tracks to new ones to embed Amplitude into the wav file. I do not freeze things often (another option available), so with a situation like yours I would be prone to bounce to new tracks and archive the original tracks (so they are there "in case" of modification later, but removed from being processed). It may be worth trying that just to verify if Amplitude is the true issue.

smallstonefan
crud. no problems when playing or recording, but leave the project opened and Sonar just locks up randomly. Not even stressing the CPU or coming close to maxing memory.
 
What would cause a project to lock up Sonar when sitting completely idle?

Autosave every X minutes?

OP says this in first post: "Never had a problem with X3 - even when I recorded a 7 piece band recently with lots of plugs enabled. Today I've crashed non-stop"...
 
So the problem has started recently.  What changed?  I would troubleshoot keeping that in mind (If it's down to plugs, use process of elimination).

have you tried starting a new project and replicating this ?
or is it one project specific ?

Thanks for all the help everyone!
 
I decided to dig in. Forced a few windows updates that hadn't taken place, updated my video driver, uninstalled some free VSTs I don't use, and did some trouble-shooting on Waves. I was having an issue adding C4 to a project. A Waves tech has been feeding me some things to try. Throughout all this I realized I had my 32bit VST folder in my scan as well as my 64bit VST folder (hence two Waveshell files). I don't think I actually use any 32bit VST files, so I removed that folder and rescanned.
 
Project is running great (and Sonar is loading a lot faster), but I need to let it idle again tonight and see what happens.
 
Again, thanks for all the pointers!

I have not checked that but I will, thanks!

Make sure you have the latest, 64-bit version of Amplitube. Amplitube takes a lot of CPU. There have been a lot of optimizations starting with Version 3.7; I think the latest is 3.10.

Ditch ASIO4ALL if you haven't already.