I am using sonar x3c (been through the producer editions from 8.5, x1, x2). I don't tend to do anything too complex and generally I have had a trouble free ride with all versions. However I did have an annoying problem with 8.5 whereby it would crash, but leave a process running which you could not end and the only thing to do was to restart my computer. This never happened to me in X1 or X2.
 
I have been experimenting with addictive drums and selected one of the preset patterns for my song - not something I would normally do but it sounded ok so I thought that I would give it a try. As you would expect the pattern whilst sounding good was pretty lifeless so I thought I would add a bit of bounce to it with some judicious quantizing and this is where my problem starts. First any quantizing causes Sonar to crash, and it leaves a process behind which you cannot end. If I wait for a while the process eventually stops and so I can run Sonar again but when I do it has lost the audio interface and the only way to get Sonar to accept that my Quad-Capture really is still there is to restart my computer (all other apps access the audio interface without a problem).
 
Is anyone else experiencing this behaviour?

Hello
 
Are you running X3 and 8.5 on a totally different system or side by side?
You have latest quad capture drivers and firmware I assume?
Latest version of 8.5? (i.e. 8.5.3 ?)
When was the last time you ran windows update?
Have you tried renaming your AUD.INI file and then reconfiguring?
Have you reset and rescanned your plugins?
Any errors in your event viewer?
 
Please post specs of your system in your footer (see my footer) so we know exactly what you have.
 
Thankyou.

The process that is left hanging may be BitBridge - do you have 32-bit plugins running in 64-bit Sonar (in one of your failing projects)?
 
If so, BitBridge gets loaded as a wrapper for those plugins, and sometimes does not flush from memory in a timely manner upon Sonar termination.
 
 

You have to turn your QC off then back on. I have this from time to time. Sometimes though, I have to restart.

First allow me to apologise and thank you for the response to this question originally posted some time ago. Almost immediately after posting I got overtaken by my day job which meant I ended up doing a huge amount of travelling and have only returned to recording in the past month.
 
So with renewed enthusiasm I updated my computer, purchased Sonar Platinum and started recording with renewed vigour. Sad to say problem still persists. Quantise freezes, sonar eventually crashes leaving sonar.exe process running, only answer is to reboot.
All drivers are up to date.
 
I've seen many videos on youtube etc where quantize is used successfully with no crashes so maybe I'm doing something wrong. My process is:
1 select track
2 select quantize from process
3 change values in quantize window
 
I have found a work around - do not audition within the quantise window - no crash!

Hi chudson,
M-audio MIDI drivers have frequently been the culprit for causing Sonar to not terminate properly. I had that exact problem with an M-audio USB MIDI interface back in the day and I know others have had similar experiences. Next time it happens and you find that Sonar stays running in the background try disconnecting the USB cable that plugs into your Oxygen49 and see if that allows Sonar to exit properly.
 
Good luck
Dean

Check my post on THIS thread
http://forum.cakewalk.com/Frustrated-Platinum-keeps-crashing-m3178843.aspx#3179113
perhaps it will help.
 
Mel

thanks for the responses my work around is ok for now but I will bear your suggestions in mind in the future

Sometimes after a SONAR freeze I'll need to restart SONAR, shut it down and then restart again.  The midi icon stays up even after closing SONAR.  A restart clears it.
 
@