Windows update wouldn't take account of the fact that people have been reporting that blocking the internet speeds it up. Not sure if ipswitch has changed the behaviour. Assuming caching is being used first time you update Sonar and run it's bound to be slow, whether cache is cleared on every update no idea(or whether cache is involved at all or not right now). Nobody has specifically pointed to it as a Win10 issue.

Worked fine last night - saw the update this morning and now - nothing but dropouts. Pulled the internet cable and Sonar loaded MUCH faster but didn't change the dropouts. Increased buffering - no change. Loaded and reloaded Win10 and Sonar several times - no change. The only difference between working fine and not is Ipswich.
 
using Win 10 (64 bit) intel i5-4460 @ 3.2 gHz, 12Gb ddr3, WD Black 1 TB. 44.1 kHz, 24 bit
2 x RME Multiface with ASIO @ 1024, SONAR Platinum 64 bit. Music file I am working on is 594 Mb total.

EDIT: I found the main reason why everything is slower in Ipswich for me (which never happened in previous versions including Hopkinton). I have about 340 tracks in my template. They don't have any audio or MIDI data in them. It's just Vienna Ensemble Pro orchestral template that I use for projects. Half of them (170) tracks are MIDI tracks ready for recording something. and the other half (170) are the Instrument (Audio) tracks that are associated with the specific output of each MIDI track. (which all of this is a very common template for Orchestral etc. usage).
 
Every version since Ipswich had absolutely no slow down at all with this template. But now with Ipswich I tried deleting the tracks in chunks and more I deleted these empty template tracks, it started doing the lag less and less and when there is only 3 to 5 tracks left, the audio tracks itselves (3 audio tracks only with data) play perfectly.
Again, this never happened in previous versions. Looks like there is some handling problem with Ipswich.. So rolling back to Hopkinton again until there is a fix.

Hi
I cannot understand why  people are Obsessed Windows 10.--flamin' Candy crush on that, Pah!!.
It must take ages taking all the rubbish out of that!!
Have a coffee whilst waiting for your computer to settle
Ipswich Is ok here, now waiting for Bognor Regis.
Windows 7  Is supported until 2020 and that leaves plenty of time for the Beta testers.
By then I will have a Hydron Collider Quantum Super Computer with a Wave X Motherboard and of 5D ram.
Hi Dok,  Still playing with my Ticks!!! it's drivin' me portamental!!.
 
It's bedtime here in uk
 
see yer later alligator
 
John
 
 

Just updated to ipswitch and the program is freezing and shutting down when I select midi & audio tracks and "copy" them.. FYI.  I rolled back to the previous update.
 
CM

Maestro6... update your sig to reflect your system specs.
 
170 instrument orchestral tracks with your cpu and memory is kinda extreme; it will take a long time to load, no matter the DAW.  CPU hit is also huge...and I can't imagine not getting memory warnings, resulting in dropouts and system instability.  I do when I get too crazy with templates and I got 6 lovely cores...unfortunately, core balancing is challenging and not related to Sonar.  It's why lots of ViC folks use multiple synced machines...
 
It doesn't matter that there's nothing on the tracks...they are loaded and active... especially when you press play or record.  I can slam my much more robust cpu with just two instances of Omnisphere2 using Airwaves multies...
 
Doesn't matter the DAW... then again, you say it was ok befor... really?  
 
FWIW, I notice no discernible difference in load times, even with several ips tracks and the new "DanaMania" png track icons on my vocal tracks.  I did load up a bunch of kontakt templates with Project Sam, Spitfire, and other configurations and as befor, got the mem warnings and my system became unstable... 100+ heavy duty memory hogs do it every time...
 
Often I delete lots of a template as I go along...as I'm not using everything.
 
I wish we had a "delete all tracks not being used" button! Would make it easier loading templates, muckin' round, cleaning them up and loading another.

Arghhh
 
Updated and now I'm freezing on audio edits and the lag on my virtual synths is nasty :/

Vastman
 
170 instrument orchestral tracks with your cpu and memory is kinda extreme; it will take a long time to load,

Maybe that's the reason he wrote that he's working with Vienna Ensemble Pro. It's assumed that maybe many instruments are hosted on other machines and connected through VE-Pro. So this scenario don't need huge cpu and memory on the daw host.
 
-Markus

Maestro6
EDIT: I found the main reason why everything is slower in Ipswich for me (which never happened in previous versions including Hopkinton). I have about 340 tracks in my template. They don't have any audio or MIDI data in them. It's just Vienna Ensemble Pro orchestral template that I use for projects. Half of them (170) tracks are MIDI tracks ready for recording something. and the other half (170) are the Instrument (Audio) tracks that are associated with the specific output of each MIDI track. (which all of this is a very common template for Orchestral etc. usage).
 
Every version since Ipswich had absolutely no slow down at all with this template. But now with Ipswich I tried deleting the tracks in chunks and more I deleted these empty template tracks, it started doing the lag less and less and when there is only 3 to 5 tracks left, the audio tracks itselves (3 audio tracks only with data) play perfectly.
Again, this never happened in previous versions. Looks like there is some handling problem with Ipswich.. So rolling back to Hopkinton again until there is a fix.

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.

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.
 
A couple days later, the Ipswitch update was released.  I installed it right away.  Since the update, I haven't been able to open the project that I was working on before the update.  Basically, after I click to open the file, the spinning windows icon never goes away.  Eventually, i have to do an end task on Sonar.  I Tried to open the file several times last night, eventually gave up.  Going to try again tonight.  Any suggestions?