• SONAR
  • Insane problems with this update (2016.12) *** Solved (for ME!) (p.2)
2016/12/03 06:18:16
Bristol_Jonesey
soens
Dumb question: Are the updates cumulative? If so, do you inherit the bugs from the last update with the next one?


Updates are indeed cumulative but that's not to say any given bug wasn't eliminated prior to releasing a new update, otherwise no bugs would ever be squashed!
2016/12/03 06:44:13
Bristol_Jonesey
This is utterly bizarre.
 
As stated above, last night I rolled back to what I thought was 2016.10
 
Well I was just helping someone out with a synth problem and noticed that the Synth Tab was no longer in the browser. Imagine my surprise to find it under Views > Synth Rack View
 
Now my curiosity was totally piqued so I dug a little deeper and according Help > About, I'm running version 22.11.0 Build 111.
 
All of my plugins are present and correct, including the ones which were causing me grief yesterday.
 
Could someone with a known, working version confirm what the latest build number is please.
 
I did adopt the early release the day before if this is a factor.
 
Interestingly, the CCC shows 2016.10 as a rollback option.
 
 
Confused  of Bristol
2016/12/03 07:05:19
adrian.crossan
Yes, current version is  22.11.0 Build 111 [2016.11].
2016/12/03 07:28:16
chuckebaby
current build is 111 Jonesey.
Sorry to hear of your problems man. but hope it is cleared up now.
Im actually doing a marathon of sorts here. running great.
I personally AM a fan of rolling updates, but with that comes Ye ole double edged sword.
At least with the old way, the updates came once a year you knew you were stable for that year.
However if you weren't stable, you had to wait another year hoping you would see improvements.
 
Whenever I have issues with the plug in manager I re personalize by holding down CNTRL and starting sonar.
This rebuilds the library and does a rescan/reset.
2016/12/03 07:36:22
Bristol_Jonesey
Yes I'm a big fan of rolling updates - this is the first one that has ever caused me problems and things seem settled now, but without me doing anything!!
2016/12/03 07:40:30
chuckebaby
Bristol_Jonesey
Yes I'm a big fan of rolling updates - this is the first one that has ever caused me problems and things seem settled now, but without me doing anything!!


you must have done something. Possibly did the "Jonesey dance backwards or something ?
Typically Voodoo like this works for me all the time. Once I ate a banana side ways and Sonar started working again.
2016/12/03 07:54:28
John
This is really good news. I can confirmed you are running the latest Sonar version.  I think Chuck is on to something.   
2016/12/03 08:23:16
Zargg
chuckebaby
Bristol_Jonesey
Yes I'm a big fan of rolling updates - this is the first one that has ever caused me problems and things seem settled now, but without me doing anything!!


you must have done something. Possibly did the "Jonesey dance backwards or something ?
Typically Voodoo like this works for me all the time. Once I ate a banana side ways and Sonar started working again.



2016/12/03 08:35:28
celopadua
This update has caused random crashes for me as well. 
 
Nothing wrong with the plug-ins scanning, but seems to crash specially while using East/West Play vsti.
 
I've submitted all reports to Cakewalk via their Crash Report Submission dialog.
2016/12/03 08:49:56
abacab
John
This is awful to hear. I am so sorry that two of the finest members are having problems with Sonar. I wish I could clear it up for you both. I am not seeing any problems here. 




I'm not seeing any issues with the latest update either.  I am wondering what the difference is between those with issues and those without?
 
Something that made me go hmmmm?,  is this comment:
 
Bristol_Jonesey
 
  • Plugin Manager stalling during a Rescan (Yes I did a reset). Always seem to stall on either Rapture Pro, Rapture Session or Z3TA+2
  • Failure to find existing plugins, even when on the rare occasions that the rescan "finished"
  • Crashing when loading any 32 bit plugin (I get the "Sonarplt.exe has stopped" working message)



Since I installed Platinum x64, I have made an effort to avoid installing 32-bit plugins.  I keep X3e 32-bit installed for that purpose.  Perhaps something not quite right with the VST scanner in the new?
 
One other thought, is the problem only occurring on Windows 10, or are Win 7 & 8 users also seeing these issues?  I have avoided Windows 10 Version 1607 (Anniversary Update) so far, and have all Windows updates locked down until I am ready for them.
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account