• SONAR
  • Insane problems with this update (2016.12) *** Solved (for ME!) (p.12)
2016/12/06 05:31:13
Bristol_Jonesey
Noel Borthwick [Cakewalk]
Bristol_Jonesey
Yes John this update has caused more problems than anything I've seen since the dark days of X1a/b.
 
They all seem to be related to the Plugin Manager so I just hope the Bakers have enough information to work out what went wrong and issue a fix.




There are zero changes to the vst scanner or plugin manager in the 2016.11 update. Which version were you using prior to this update? Your problems are most likely coincidental and caused by something else.


Given the plethora of VST related issues being reported across the forum, it would appear that something has definitely borked the scanner or the PI manager.
2016/12/06 07:50:57
auto_da_fe
Interesting Stevesweat and Jackson white...
 
I have the Roland Octacapture and am seeing the same thing.  Any Sonar crash (CA2A or Melodyne, or anything else) causes ASIO drivers to vanish from my machine.  The only way to get them back is to restart DAW.
 
Now a days I always check a standalone VST like EZkeys to make sure my ASIO drivers are alive on the machine.
 
I have disabled and reinstalled the drivers a few times and it seems to help for a little while.
 
Do you also have super slow project loading times ?  I sometimes have 7 - 10 minute times loading projects.  Not sure if it is Roland ASIO driver related ?
 
I will start a new thread and see how many others are seeing issues with their Roland ASIO cards in the last little while.
 
JR
2016/12/06 08:22:18
JohnEgan
Try as I may, without going to extremes, as I may not be considered an extreme user, I'm still not having any operational issues with this update.
Although Im not a computer guru by any means, following this and other threads it is somewhat reminiscent of behaviours Ive seen caused by virus's? Although Im thinking this has already been considered ruled out as a possible cause, I guess it only takes one common download, email or file shared. 
 
Anyway hope for all you affected (or infected) someone finds the solution soon, and you all can get back to producing music.
 
Cheers 
2016/12/06 08:46:54
stevesweat
Was David Blaine on the build team for CA-2A?? I think there is a time bomb in it.
2016/12/06 09:54:43
jackson white
@auto-da-fe
 
My experience strongly suggests the driver "disappearance" is a Roland issue and not a SONAR issue. Losing the drivers happens every time I get a "SONARPLT.exe has stopped working" and has been the case since X2/X3. More of an inconvenience than a showstopper, because the recovery has been very consistent. Similar issues have been noted in other threads well before the latest SONAR update. 
 
I've been looking into updating the interface for this project studio but don't believe it has anything to do with the latest CW VST problems. That sounds more like a Win10 update or some core SONAR cfg issue. I've noted some changes in the registry during my multiple attempts to troubleshoot the problem. 
 
 
2016/12/06 10:05:44
abacab
I'm reaching way out on a limb here, but is there a pattern in common to a specific brand of audio interface and their ASIO drivers, that is now having issues with the plugins?  I ask this because not everyone has seen the issues in 2016.11.
 
Just wondering, because several folks have said that Sonar crashes for them upon inserting certain VST plugins, or starting up an existing project that contains them.
 
Noel mentioned that nothing has changed specifically relating to VST handling.
 
But, is it possible that the changes in 2016.11 to enhance the WASAPI drivers could be at play here?  I believe that some VST's interact with the Sonar audio engine as soon as they are inserted into a project.
 
See this related thread: http://forum.cakewalk.com/Calling-All-Roland-Sound-Card-Users-Quad-and-Octa-m3524639.aspx
2016/12/06 10:12:32
Sidroe
I have had the Roland drivers for my 2 Studio-Captures disappearing consistently since late X2 updates!!! I can't even get the hacked driver installation trick to work to re-install without going online everytime to re-download and re-install. This seems to be just the ASIO driver problem because anything running on the Windows drivers still works!!! I have been tempted to go back to my MOTU 24io!!!
As for the new update, crashes I have never experienced on any other update. Staying where I am for now but bothers me that rolling back is not going to fix the issues!! How about a QuickFix patch?
2016/12/06 10:32:18
jackson white
@abacab
 
The Roland xCapture drivers have always been a bit shaky in my experience but only a minor inconvenience for some time. Easily recoverable with a PC restart, which in my case trashes any "fixes" I made to get the CW VSTs working. 
 
@klauslix reported what sounds like identical symptoms and issues as mine but with a different interface (Steinberg) so I suspect the driver is likely more of a red herring. 
 
However, I am wondering about the recent WASAPI drivers feature as my CPU core balancing now looks considerably more unbalanced than with the previous update. Certainly a "core enough" change to consider the potential impact on any drivers. I've also noted CW very recently updated two of the FX suites with the problematic VSTs before the latest update. 
 
IME, it has only, but very consistently, been the same select CW VSTs that can be associated with the problem. Noel Borthwick stated in another thread that no changes were made to the VST Scan and I believe him, -but- something must have corrupted/changed with the noted CW VSTs to crash Cakewalk VST Scan. 
 
I will try looking into system cfg, Win10 changes, VST3? this Thursday for additional clues. 
2016/12/06 10:36:47
bitflipper
I don't think this is driver-related or dependent or the brand of interface you use. Audio drivers should not come into play when you simply insert a plugin, and definitely don't come into play when you're scanning VSTs. I get the same behavior regardless of the driver mode (I've tested ASIO, WASAPI Exclusive and MME).
 
 
2016/12/06 10:42:25
jackson white
@bitflipper
 
Agreed on the driver comments, believe it's a bit of a red herring.
 
> Have you noticed any changes on the appearance of your CPU core balance? 
 
Mine were remarkably low and well balanced -until- the latest update. I've only had to time to run a few  larger projects since the latest issues but noting large discrepancies across the cores with #1 spiking considerably higher than all the rest. 
 
 
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account