I just bought a new Novation Impulse 61 keyboard controller to replace my wonky M-Audio Axion 61 (1st edition), and followed the directions to the T on setting it up for Sonar Platinum. I had to install Novation's proprietary Automap program, which as I understand wraps VSTs in a certain way so they could be easily controlled by the controller.
 
When I opened up Sonar after setting it up, I opened a short test project I started after getting Sonar Platinum, it was probably less than 20 measures long and only had about 3 VST instruments in it, and no effects, aside from some ProChannel elements.
 
It worked fine, I LOVED having everything controlled at my fingertips. It was the controller I was looking for.
 
But then I tried opening an older, more complete project with several VST instruments and effects in it, and Sonar Platinum just hung there and gave the "(Not Responding)" message at the top of the task bar.
 
Uh oh.
 
So then I restarted the computer, but to no avail, I got the same results. Short projects opened fine. Larger, more complete projects will not open.
 
I've read this forum before I bought my Novation controller, some people said it works perfectly, and now I'm seeing people with problems with Automap, but none having to do with opening projects. I'm panicking here now (it always sucks to be the only one with that problem).
 
What do I do? Is there a way to use the controller without Automap? Did I just waste $400?
Were those larger projects ruined forever?
 
 

I figured this out by process of elimination - I Uninstalled Automap, but still had this problem. Then I discovered Sonar Platinum only hangs in projects where the "!WaveShell-VST3 9.6_x64 (Automap).vst3" was loading. After deleting this wrapped Waves plugin, Sonar Platinum loads all projects now.
 
Okay, so here's the burning question? Who's responsible for fixing this? Novation, Waves or Cakewalk?

Hi Elson . . . glad you found the root of your issue.
I also use the Novation Automap software, and I ran into a very similar problem with my Melodyne software.
It seems some plugins just don't like the way Automap renames the VST filename with ! . . .(Automap) in the name.
 
I recall contacting Novation support, and they had no clue, their support for Sonar (at least few years back) was sorely lacking.  I had to find out the solution on my own using trial and error diagnostics. I let Novation know how I solved my issue (by renaming the VST filename) so they would perhaps have it in their database ? Not sure if you tried Novation tech support ?
 
So, my answer to your burning question of who fixes this issue . . . I think we do.