• SONAR
  • [Fixed in X3e update] Sonar X3C moving bus fader crash
2013/11/14 04:53:11
djpremacy
Hi everybody,
 
I was really happy with Sonar but last 2 days I have many crashes.
Sent them via Sonar crash report. 
 
Sonar X3C
Windows 8.1 64 bit
I7
NI audio 6 interface
AMD radeon 7770
Dual screen workflow (left main inspector,right the console and piano roll switching tabs)
All with latest drivers.
 
2 days ago I purchased the prochannel pack and since then the problem are happening.
I updated my project start template and I replaced all the 3rd party compressors/gate etc with the prochannel plugins.(4k channel, 4k Gate) and also added concrete limiter and Ca-2a to some channels.
 
In the template I use the 4K channel,4K gate from the addon pack on the busses.
50%+ of the time when moving the volume fader on any of the busses sonar will crash. Also 2 nag screens below the crash screen show me error with prochannel 4K channel, en gate. Most of the time it's when moving volume faders on bus that has the 4K channel or gate on it. They are being fed from a sidechaining signal (kick track)
 
I tried to solve doing the following things :
Rescan all plugins
Disable 64bit double precision engine
Closed the 2nd screen (console) and moved it to 1st screen. Save, reopen en move the console back to 2nd screen.
Removed all addon pack prochannel modules from the busses. Still crashes but seems less frequent.
Installed a windows net framework update that was suggested in another forum thread.
Remove all sends to the bus compressors.
Tested my old template without prochannel pack plugins and works fine.
 
Should I maybe run in safe mode and try to replicate? Will if then load the prochannel plugins (but no 3rd party vst?)
My guess is that it really has to do with the prochannel pack that I installed and specifically the 4K Channel compressor (on a bus, but shouldnt be a problem) and gate. Also it seems that selecting and switching channels is slower than before and the re-draw of the inspector prochannel is slower.
 
Hopefully a solution can be found for this great software!
Thanks from a user that had a really stable Sonar X3 untill I installed the prochannel pack.
 
 
2013/11/14 05:41:32
cowboydan
2013/11/14 06:08:28
djpremacy
Thanks. I did that yesterday and did not solve the problem. I will try again this afternoon. Maybe reinstalling the whole net framework 4.
2013/11/14 06:12:56
cowboydan
If you have the 64 bit engine checked in preferences, change this. Here are the most problems in sonar right now.
2013/11/14 06:47:31
djpremacy
I always keep the 64 precision engine unchecked.
As I read in the forum this was causing many problems to many users.
2013/11/14 07:04:14
Mystic38
I suspect its simply not going to be possible for CW to replicate your problem..
 
You indicate your old template works.
 
Suggest that you open a new standard template (not your custom one) add one feature and fully test it.. then add another feature and fully test it.
 
if you get to the point where doing ONE thing causes issues, then focus on that... that ONE thing can be replicated by users here and also by CW staff.
2013/11/14 07:04:37
gswitz
Sonar doesn't use the .Net framework. They just use C++. You don't need the framework to run Sonar.
 
I too am unchecking the 64 bit engine as everyone is saying to. I find it hard to keep it unchecked. Every time I bounce, I lean towards checking it, but I don't. ;-)
 
DON'T CLICK THE BBBBIIIIGGG RRRREEEEDDD BBBBUUUUTTTTOOONNNN Stimpy!!
2013/11/14 07:19:19
mettelus
Mystic38
Suggest that you open a new standard template (not your custom one) add one feature and fully test it.. then add another feature and fully test it.
 
if you get to the point where doing ONE thing causes issues, then focus on that... that ONE thing can be replicated by users here and also by CW staff.


+1, I would recommend this route as well. There may be an artifact in your old template that is causing this.
2013/11/14 10:18:55
djpremacy
ok, i have an update.
 
I de-installed all prochannel plugins and then when starting the custom template ofcourse it will give the message that plugins are missing. BUT, there is no problem selecting tracks or moving faders.
Re-installing the concrete limiter works ok with the custom template.
 
After installing the 4K channel compressor and/or the gate the problems start occuring again.
Right screen = console,  left = inspector with prochannel.
 
So i did the following.
1. Create NEW project with normal Sonar template selection.
-Add one vst (ANA synth or Massive) + 4K bus compressor,Console emu, concrete limiter,Gate, and channel compressor
-Add one bus and route the synth channel to the created bus. On the bus I also put the concrete limiter, gate, and 4k channel compressor.
When playing project and trying to move the bus fader an instant crash. This is with the inspector and track view left, and on the right monitor the console view.
 
2. Same template as above but with console view undocked and on the 2nd monitor. Instant crash.
 
So after installing the prochannel modules it seems that the dual monitor setup with console on 2nd  screen creates the crashes.
Does this help in identifying the problem?
 
2013/11/14 10:28:58
brundlefly
Did you get the 64-bit Double Precision Engine disabled in Preferences > Audio > Driver Settings as suggested?
 
Can you reproduce with only one of the new PC modules added to the Master bus in the Normal template? What if you bring your Console view back to the main monitor? You still have too many variables in your project/environment to know what the real culprit is.
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account