Craig. I have the utmost respect for you and your fantastic work... articles , tips etc. Cakewalk are lucky to have you.
 
However you are paid by Gibson and therefore your view is not independent. Please support me and the other users (Cakewalks paying customers) here to get an update on what is a very serious issue for a software app company to have with its OS platform provider.
 
I have customers that push me always to use pro tools and mac. I continue to use Sonar on Win and happy to make it's case, but this really does not help. I'm convinced Cakewalk have a strategy of silence while working this. In my view that is just not acceptable and I'm afraid is jumping back to the bad old days customer communication days under Roland and before.
 
I ask you to use some customer empathy and rather forget you internal insight and relationship with Cakewalk and think about how you would feel I'm my position, where the tool I use for putting food on the table is now unfit for purpose and my new projects are now in Reaper. I'm not sure how you can defend zero updates on the situation from Cakewalk. Do you. 

What is really wondering me: This behaviour ist related to Windows 10 - at it is said. I am on a W7 64 Bit System. But since the November update I experience also more stuttering,dropouts and crashes while playing or when handling with plugins then before. No matter, if I use Asio or WSAPI. I did not realized this at once. But this crackling / dropout behaviour is new for me.
 
Kind regards  

eltonechris
Craig. I have the utmost respect for you and your fantastic work... articles , tips etc. Cakewalk are lucky to have you.
 
However you are paid by Gibson and therefore your view is not independent. Please support me and the other users (Cakewalks paying customers) here to get an update on what is a very serious issue for a software app company to have with its OS platform provider.
 
I have customers that push me always to use pro tools and mac. I continue to use Sonar on Win and happy to make it's case, but this really does not help. I'm convinced Cakewalk have a strategy of silence while working this. In my view that is just not acceptable and I'm afraid is jumping back to the bad old days customer communication days under Roland and before.
 
I ask you to use some customer empathy and rather forget you internal insight and relationship with Cakewalk and think about how you would feel I'm my position, where the tool I use for putting food on the table is now unfit for purpose and my new projects are now in Reaper. I'm not sure how you can defend zero updates on the situation from Cakewalk. Do you. 

I believe even our local "Electronic Musician" won't be able to help us.. Cakewalk seems to have gone underground on this one..

eltonechris
Craig. I have the utmost respect for you and your fantastic work... articles , tips etc. Cakewalk are lucky to have you.
 
However you are paid by Gibson and therefore your view is not independent. Please support me and the other users (Cakewalks paying customers) here to get an update on what is a very serious issue for a software app company to have with its OS platform provider.
 
I have customers that push me always to use pro tools and mac. I continue to use Sonar on Win and happy to make it's case, but this really does not help. I'm convinced Cakewalk have a strategy of silence while working this. In my view that is just not acceptable and I'm afraid is jumping back to the bad old days customer communication days under Roland and before.
 
I ask you to use some customer empathy and rather forget you internal insight and relationship with Cakewalk and think about how you would feel I'm my position, where the tool I use for putting food on the table is now unfit for purpose and my new projects are now in Reaper. I'm not sure how you can defend zero updates on the situation from Cakewalk. Do you. 

With all due respect, I cannot understand how anyone who counts on their computer to put food on their table would put 100% faith in any Windows or DAW application developers to always provide code updates 100% without errors.  Not ever going to happen...
 
So instead of blaming the developers for an inevitable problem, the simple answer is to roll back to a system image that was made prior to the issue.  Then wait for a fix, while you can still get your work done on a stable system.

bitflipper
The easiest workaround is to start SONAR and close it. For me, at least, the problems do not reoccur after SONAR has been opened once. They reappear after a reboot, however.
 
It would be nice if Noel would give us a little information, though. I'm sure he already knows what the problem is, but the fix is likely going to be very difficult. I'm also sure he's deep into it and hasn't seen a 40-hour workweek since this all began.

I just observed something odd using ProcessExplorer by Sysinternals, which is related to ProcMon, but is actually a souped up Task Manager.
 
I was looking at the threads view for the main SONARPLT.EXE after a freash boot-up and first run for Platinum, and I saw threads for each of the project plugins .dll files.
 
So I closed that project and created a new one.  Inserted a few instruments and FX.  ProcessExplorer no longer shows any plugin .dll threads in the main Sonar process.
 
So I re-opened the first project that had shown plugin .dll threads for Sonar.  Diito.  None shown.  Weird ...
 
Here is a free eBook with Chapter 5 "Processes, Threads, and Jobs" from "Windows Internals", by Mark Russinovich, founder of Sysinternals.  https://live.sysinternals.com/windowsinternals/windowsinternals-ch05.pdf
 
Grab a copy of ProcessExplorer here and follow along, LOL!  https://technet.microsoft.com/en-us/sysinternals/processexplorer.aspx

dlesaux
I've heard about the fact that Microsoft changed something to so with timing in their last update. Is this a manifestation of that issue?

The explanation given by Microsoft that "The problem is related to a change in the timing for thread initialization on Windows" may be somewhat terse, and be less than clear to a non-technical person.
 
My interpretation is that this refers specifically to code in Windows internals, not to audio timing.  It's much deeper down than the audio layer.
 
While you may be experiencing some audio issues, this thread timing thing leads to crashes and other errors.
 
Windows is a hot mess.  It's a wonder it works at all, LOL!

jimo

John
 
No other plugin from CW have this problem. Also no other plugin from third parties seem to have any problem.

I am also having problems with some Waves plugins, I initially noticed it on the latest version of the API 2500 (mono)
 

I am having problems with Waves plugins as well. I removed all Waves plugins from the project and the project no longer crashed.

sorry if this has already been posted, but another possible workaround, from seth over on the steam forums, is to set compatibility mode to windows 8 on the sonar exe http://steamcommunity.com.../2/154643795213913095/
hth

pwalpwal
sorry if this has already been posted, but another possible workaround, from seth over on the steam forums, is to set compatibility mode to windows 8 on the sonar exe http://steamcommunity.com.../2/154643795213913095/hth

I would not have expected this if the issue is thread initialization.

microapp

pwalpwal
sorry if this has already been posted, but another possible workaround, from seth over on the steam forums, is to set compatibility mode to windows 8 on the sonar exe http://steamcommunity.com.../2/154643795213913095/hth

I would not have expected this if the issue is thread initialization.

indeed, and i haven't confirmed it myself as i don't have the issues others are seeing, but maybe it helps someone