I have sorted out most of teething problems with sonar, except the one with Omnisphere.
Cubase and Traction are fine with it, but Sonar hates it, on my PC.
I have noticed the following;
- if I launch Omnisphere, but with the options set in Sonar not to display the interface. It starts, pretty damn quick, and I can play the the default patch.
When I try to open the Omnisphere interface, one of my CPU cores maxes out for about 5 seconds then it appears. If I close the interface and then try to re-open it, the same CPU maxes out , but indefinitely... and if I am not careful to quickly force a process close-down of Sonar, then my whole computer will just freeze ... require a hardware reboot (not something I am willing to do many more times).
Why does the Onipshere interface put such a load on the PC.
(I have switched off the X-Ray mode in Sonar ... doesn't make a difference.)
If it works fine in other hosts, but not in Sonar, one thing I would suspect is write automation. I know turning that on can cause problems in Sonar when working with instruments with lots of parameters. But, as long as that is turned off, Omnisphere works fine here in Sonar.
Automation works in Sonar and you can draw in events, but when you turn write mode on, Sonar displays a warning that performance will be slow. I don't understand why since it works fine in other hosts, so you'd have to ask Cakewalk about that.