Takes the wind out of your sails

Is it your computer that crashes or Sonar?

BIG difference

Bristol_Jonesey


Is it your computer that crashes or Sonar?

BIG difference

Not to a musician... It's only a big difference to to the computer.

:-)

Good Luck!


best regards,
mike

What was the cheap MIDI interface? I have a cheap MIDI interface, actually two: a Korg nano Kontrol and a AKAI LPK 25.

Well mike_mccue is greatly helpful here. Sigh..

Anyway...

I can see you are using the Korg Nano Control. I had some problems in the past with that stuff. The drivers for the Korg nano cotrol are a bit flakey (to put it mildly). Sometimes it wont release ports (or focus or something), letting the application hang forever. I had this happening with Cubase as well as Sonar (8.5 and X1). It would not surprise me if those drivers do some weird things. I have dished the Korg Nanocontrol and a wile ago and replaced it with the (also not very expensive)  Behringer BCF2000. After that both applications behaved without problems...

I do not say this is the culprit, but maybe it is a good idea to de-install the Korg drivers completely (you always can re-install them after the try-out), and disconnect the Nano Control. Be sure to reboot after de-installing!

There are also a lot of other possibilities (like free, but bad designed plugins), Bad sound card drivers etc. etc.

milbrave1953


X1...It locks up ans even after I shut it down it is still running in the background and I can't even shut it off from the task manager...so...I have to reboot the computer.
 

if yr audio interface is external, rebooting that is faster than rebooting the whole pc, good luck

I don't think that talking to a scanner or a camcorder is a reasonable comparison.  Real time processing puts stress on drivers and software that is orders of magnitude beyond normal device access.

If you get crashes in Sonar, but not in other applications (using the same drivers at the same latency), you may be on to something.

Unfortunately, I have to agree with the OP.  I also see more crashes with X1 and the SONARPRD.EXE process also does not exit cleanly. I have as close to Cakewalk-recommended gear as anyone is likely to have and I still crash enough to where it definitely interrupts the creative process. Most crashes seem to be related to bitbridging (built-in 64-bit bridging), which is required for several major plug-in suites that haven't went fully 64-bit yet. 
I don't really fault Cakewalk for the less than rock solid bridging support as I know a lot of it is out of their hands. However, I do think X1 could handle errors better and not be allowed to bring down the whole DAW.

-e.B

There are some issues with the Sonitus VSTs and Waves and UAD VSTs residing in the same project. I stopped using the Sonitus plug ins and rarely get BitBridge hanging issues.

ProjectM


Hey eBlue.


Have you tried jBridge? I wrapped my 32-bit usual suspects with that and most of the trouble with those plugs went away. Like magic. Or at least that's what it felt like.

I did the same here-much better.

One thing you can do (and I know this isn't a real solution) is to get all SSD drives for your system. It's expensive right now, but well worth it in my opinion. Win7 boots up in less than a minute, and I can open a very large project with 3 synths and samplers and lots of audio in about 6 seconds or less. It makes X1 crashes alot more easy to deal with when you are back up and running in under a minute. If you can afford it I highly recommend them.

milbrave1953: i assure you thats not happening here ever, ask others to go over your setup with you !!!