Problems with X3

Do you happen to have one or more 32-bit plugins loaded into your X3 project?
 
There are some 32-bit plugs that do not play well with 64-bit Sonar, and it gets a bit tricky, since they likely worked in some prior Sonar version, and each plugin has its own interpretation of the VST 2 or VST 3 specifications.  So, sometimes errors are only exposed because of code changes within Sonar - not to say that the Sonar code is bad, it's just that it may slightly be different in how it does things, or passes things to and from the plugin.
 
I went through a process of first of all deliberately choosing to move to a completely 64-bit environment, then I made sure each 32-bit plugin I wanted to use in 64-bit Sonar worked, and I moved those to a sub-folder in the 32-bit plugins folder.
 
I now have all 64-bit plugin 3rd-party plugins, and only whatever 32-bit ones came with Sonar.
 
SO, these 32-bit plugins MAY be experiencing a slightly different set of code in its interactions with Sonar and/or Windows (new maintenance), and this HAS caused weird processing and crashes - per other posted threads.
 
What happens if you open it in Safe Mode with no effects, to see what happens?  This would be a super easy quick test to see if something with the plugins is causing your problems.
 
Please review and hopefully perform, and post back so I can try to help you through whatever is happening.  :)
 
Bob Bone
 

I would agree with Bob's tack but I would also verify if the performance issue is occurring in other projects as well. If it isn't then that would reinforce the idea of a plug being the problem. If the issue is occurring in all projects I don't have any good ideas other than to ask the question: What Changed?
 
Best of luck.
 
Regards,

ALSO:
Based on your system specs, I would suggest you have a buffer size setting issue...
pops, clicks, stuck notes all have a sort of balancing act they do between how FAST you are sending your buffers and
how LARGE they are, in both audio and midi.
I assert that your rig should be able to handle (to a point) a large session w/plugins without  such a large buffer.
too small; pop pop  too large; cripple your cpu, pop pop stutter; too slow, pops and maybe crash as well.
Assertion 2; a 40% cpu hit is not uncommon on large projects w/ lots of (esp. realtime ) plugins, on an
I7 2600, and that shouldn't give you the issue you described in your OP.
 
I always use the old backwards walk when I get issues on a system
that was running well before I  ever even CONTEMPLATE a re-install/wipe/whatever:
1.user error(connections, etc.)
2.hardware (random, non repeatable)
3.software (always repeatable with same steps)
4.(sonar specific): burn the aud.ini file and sonar will make you a nice clean one. you will have redo any configuration tweaks you had but usually works.
 
hope some of this helps, I'm a 2 finger typist (lol).
 
 
Mel

According to some threads on the web, this plugin's pitch correction functionality uses 'look-ahead' processing, which will drive your latency through the roof.  I am wondering if there is some other functional use of look-ahead processing within that plugin.
 
That plugin sounds like those parts of it are meant to be done POST tracking, for mixing.mastering.
 
Bob Bone
 

Thanks for going to the trouble of looking that up Bob! I actually did manage to freeze the track I was using Nectar on.  It did improve things slightly, but it didn't change much overall.