Open in Safe mode and don't load any plug-ins as a baseline point of comparison.

Thanks, I'll give it a try tonight..

davec69
I recently subscribed to Sonar Platinum, on the Hopkinton release.   After installing everything, Sonar worked fine.   I was noticing high activity on core 1 of my cpu, but everything seemed to work.
 

Interesting - I opened a project I finished mixing about half a year ago (Braintree?) in Ipswich and I got this unusual high activity on core 1 and lots of drop-outs but haven't had time to follow up yet ...
 
To be honest I have no clue as what could be causing this high CPU use on core 1 (plus the total imbalance with other core which are far less used)  ... of course I have also updated win7 and NI plugs since finishing that mix...
 
Anyone else that???

I have had a performance issue, but it may have been caused by enabling Hyper-V. That's the only other thing that changed. 
 
After about 1 minute into recording a take, it slowed down momentarily but did not drop out. 
 
I've now disabled Hyper-V and will see if Sonar is better.

So, to report back on my findings last night, I started up Sonar in safe mode.  First attempt, I bypassed all plugins, and the project loaded no problem.   Next, I loaded each plugin one at a time until I found the plugin causing the problem.   I found that If I didn't load the Nebula 3 plugin on my drum track, the project would load with all the other plugins.   I was using the same plugins prior to Ipswich, and they were all loading fine.  Not sure what changed.
 
Update!!!!!
I found the cause of my problem above.    A couple days ago I was trying out WASAPI mode, to compare with ASIO.  After I finished, I forgot and left my driver set to WASAPI mode.  This is what caused the sudden problem with Nebula3.   After switching my driver back to ASIO mode, I was able to load my previous project files with out disabling Nebula 3 first.
 
FYI.  I still get the high CPU activity on CPU 1.  Not sure what's going on there. 

Is there a patch for Nebula 3?
Run windows update.
Try running Sonar as administrator.

Ta.

FreeFlyBertl

Maestro6
Now, this is interesting. Large / extreme projects are good for spotting performance issues when small changes accumulate ... there have been major changes to how MIDI vs. audio tracks are handled now that you can record synths. I wouldn't be surprised if optimization in the code is possible in a few places ...
 
You should share that template with Cakewalk support.


FreeFlyBertl, what you wrote makes sense, I wonder too if the new recording synths feature might have caused this. I just shared my template with Cakewalk support. Let's see what happens. Thanks!
 

Doktor Avalanche
Is there a patch for Nebula 3? - I'm on the latest version
Run windows update. - I'll check this, but it's Windows 10, so it's probably up to date.
Try running Sonar as administrator - I can give this a shot tonight.

Ta.

SOLVED! (Workaround): I wanted to update all of you that after I shared my templates with Cakewalk and they had the same issues at their end as well with my templates. (works fine on Hopkinton but not on Ipswich). They suggested me two things and solved both the problems. Here they are:
 
1. Opening a project/template takes long time. - Solution: (This was simple and something I didn't try before) Just save it as a new version again on Ipswich and next time it opens up in normal speed.
 
2. Performance problem. - Solution: In preferences-->Project-->Record-->"Allow Arm Changes During Playback/Record" has to be disabled. That fixed the problem. Looks like this has some sort of CPU hit on the computer with the new real-time direct instrument track recording feature that was introduced with Ipswich I believe. I do like the "Arming tracks" during playback/record function normally, so would love to be able to enable this without having performance issues.
 

Nice find! For what it's worth, I'm finding Ipswich on Win 10 preview build 10547 to be the best sonar experience yet. The future's so bright I gotta wear shades.