Answered{SOLVED} After updating SONAR the plugin mgr crashed a lot w out completing a full scan .

Author
Post
Essentials Only Full Version
kennywtelejazz
Max Output Level: -3.5 dBFS
  • Total Posts : 7151
  • Joined: 2005/10/22 06:27:02
  • Location: The Planet Tele..X..
  • Status: offline
2017/06/02 06:41:51 (permalink)

{SOLVED} After updating SONAR the plugin mgr crashed a lot w out completing a full scan .

I updated SONAR tonight and now I'm really sorry I did ..
I don't know why all of a sudden my plugin manager can't make it through a scan without crashing ...
After it crashes I have no VST 3 Plugs or Synths listed in SONAR ...
My last scan was a few weeks ago ...no problems
I don't know what to do here
Suggestions ?
 
Kenny
post edited by kennywtelejazz - 2017/06/02 13:12:40

                   
Oh Yeah , Life is Good .
The internet is nothing more than a glorified real time cartoon we all star in.
I play a "Gibson " R 8 Les Paul Cherry Sunburst .
The Love of my Life is an American Bulldog Named Duke . I'm currently running Cakewalk By BandLab as my DAW .
 
https://soundcloud.com/guitarist-kenny-wilson
 
https://www.youtube.com/user/Kennywtelejazz/videos?view=0&sort=dd&shelf_id=1
 
http://www.soundclick.com/bands/pagemusic.cfm?bandID=427899



#1
See best answerList Solutions Only

14 Replies Related Threads
    telecharge
    Max Output Level: -67 dBFS
    • Total Posts : 1180
    • Joined: 2014/03/31 18:01:17
    • Location: Enfuego, Monterey
    • Status: offline
    Re: My plugin manager can no longer make it through a scan with out crashing after updatin 2017/06/02 10:21:52 (permalink)
    Since you didn't mention it...
     
    Have you tried a VST reset before a rescan? Also, some of the FX suites were updated with this release, so I would verify they're up to date, as well.
    #2
    THambrecht
    Max Output Level: -73 dBFS
    • Total Posts : 867
    • Joined: 2010/12/10 06:42:03
    • Location: Germany
    • Status: offline
    Re: My plugin manager can no longer make it through a scan with out crashing after updatin 2017/06/02 11:21:06 (permalink)
    You can always roll back to a previous version of SONAR. And then test what happens.
    You can also make a windows system recovery - if you have not turned them off.
    - Maybe a vst-folder or a file has no read-permission and the vst-scanner crashes. What should not happen.
    - Maybe its up to an windows update that has changed read-permission of a folder.
    - Maybe a file is corrupt.
     
     
     
     

    We digitize tapes, vinyl, dat, md ... in broadcast and studio quality for publishers, public institutions and individuals.
    4 x Intel Quad-CPU, 4GHz Sonar Platinum (Windows 10 - 64Bit) and 14 computers for recording tapes, vinyl ...

    4 x RME Fireface 800, 2 x Roland Octa Capture and 4 x Roland Quad Capture, Focusrite .... Studer A80, RP99, EMT948 ...

    (Germany)  http://www.hambrecht.de
    #3
    chuckebaby
    Max Output Level: 0 dBFS
    • Total Posts : 13146
    • Joined: 2011/01/04 14:55:28
    • Status: offline
    Re: My plugin manager can no longer make it through a scan with out crashing after updatin 2017/06/02 12:09:50 (permalink)
    As Telecharge mentioned... I would try a VST reset before a rescan.

    Windows 8.1 X64 Sonar Platinum x64
    Custom built: Asrock z97 1150 - Intel I7 4790k - 16GB corsair DDR3 1600 - PNY SSD 220GB
    Focusrite Saffire 18I8 - Mackie Control
       
    #4
    kennywtelejazz
    Max Output Level: -3.5 dBFS
    • Total Posts : 7151
    • Joined: 2005/10/22 06:27:02
    • Location: The Planet Tele..X..
    • Status: offline
    Re: My plugin manager can no longer make it through a scan with out crashing after updatin 2017/06/02 12:38:01 (permalink)
    telecharge
    Since you didn't mention it...
     
    Have you tried a VST reset before a rescan? Also, some of the FX suites were updated with this release, so I would verify they're up to date, as well.


     
    THambrecht
    You can always roll back to a previous version of SONAR. And then test what happens.
    You can also make a windows system recovery - if you have not turned them off.
    - Maybe a vst-folder or a file has no read-permission and the vst-scanner crashes. What should not happen.
    - Maybe its up to an windows update that has changed read-permission of a folder.
    - Maybe a file is corrupt.
     
     
     
     




     
    Hi telecharge and THambrecth , thanks for offering your help and suggestions
     
    Here's what I did  VIA the CCC . A full update of SONAR and all the plugs that were available in this new release .
    I thought I may have screwed up by launching SONAR after all the updates because I do not know if launching SONAR that way VIA the CCC is considered  launching as run as administrator according to Windows ..
    I mention that because the first thing I did after launching SONAR was to run my plugin mgr ...
    I had my options set to a full  VST reset that also  included a rescan failed plugins and rescan exisiting plugins box's as checked ...
    OH boy lets just say I have been working at this problem nonstop since 9 PM to 4:45 AM
     
    Aside from my persistence I am super proud of the fact that I didn't open my mouth here on the forum and tell you guys what I really think ...
    Even a mythological fire breathing dragon right out of a fairy tale  may  have been impressed with the heat of the flames I could have summoned to have burnt the bridge down to the ground  ...
    Whew , lets face it , restraint of tongue and pen don't always come easy for me 
     
    Alright , here's what happened ..on my computer a typical VST scan takes between 15 to 20 + mins ..
    The first half a dozen times I ran my scan I kept watching to see where it was crashing ...and on what plug ?...
    The Tokyo Dawns TDR Kotelnikov was the first plug that crashed my plugin mgr repeatedly ...
    I went in there and removed it manually from both the 64bit and 32 bit versions and their respective folders ...
    Then it was time to rerun the scan a few more times
    The next plug that crashed my plugin mgr was the TX16x at that point I was like WTF is going on here?
    both of these plugs that are crashing my SONAR plugin mgr run perfectly fine in Samplitude Pro X 2 , Reaper 64, Ableton Live 9 , Mixbus 4 , Mixcraft 7 , Sony Acid Pro 7 and a few other DAWs Like Project 5 and all my 64 and 32 bit standalone Midi Guitar apps... ???????????..........what's up with that ?????
    So I rollback SONAR ..great now maybe it will work ....nope not happening ...a real crash-fest all over ...
     
    Remember these plugs weren't crashing the plugin mgr before in SONAR up until tonight  ...
    I know I didn't want to do a system restore , it's too hot to run my fireplace , and I didn't want to make like my computer was a horse with a broken leg and shoot it so I did the only thing that made sense to me...
    I decided to uninstall anything that crashed my plugin mgr ....
    The TX16x was the last plug that crashed so I uninstalled that ...
    At that point I said you know what lets just re-update SONAR again ...which I did VIA the CCC...
    Crossed my fingers , re set everything again and ran a scan ....
    This time the plugin mgr crashed when it got to the Youlean Loudness Meter ...
    I said OK let me remove that .....which I did ....
    Well I went this far lets run the plugin mgr again and see what happens next...
     
    I'm very happy I did ...this time the plugin mgr didn't crash ....
     
    I was like what you have had a change of heart ? OK You Wub me ...I Wub you too
     
    Thankfully everything seems to be working now 
     
    Sorry folks about the long winded verbiage ...that's my story and I'm sticking to it ..
     
    Kenny
     
     
     

                       
    Oh Yeah , Life is Good .
    The internet is nothing more than a glorified real time cartoon we all star in.
    I play a "Gibson " R 8 Les Paul Cherry Sunburst .
    The Love of my Life is an American Bulldog Named Duke . I'm currently running Cakewalk By BandLab as my DAW .
     
    https://soundcloud.com/guitarist-kenny-wilson
     
    https://www.youtube.com/user/Kennywtelejazz/videos?view=0&sort=dd&shelf_id=1
     
    http://www.soundclick.com/bands/pagemusic.cfm?bandID=427899



    #5
    kennywtelejazz
    Max Output Level: -3.5 dBFS
    • Total Posts : 7151
    • Joined: 2005/10/22 06:27:02
    • Location: The Planet Tele..X..
    • Status: offline
    Re: My plugin manager can no longer make it through a scan with out crashing after updatin 2017/06/02 12:42:03 (permalink)
    chuckebaby
    As Telecharge mentioned... I would try a VST reset before a rescan.




    Hey Chuck ,
     
    Ever since the last time we talked I have always ran it as a VST reset before a rescan ..
     
    You had hipped me to that
     
    thanks
     
    Kenny

                       
    Oh Yeah , Life is Good .
    The internet is nothing more than a glorified real time cartoon we all star in.
    I play a "Gibson " R 8 Les Paul Cherry Sunburst .
    The Love of my Life is an American Bulldog Named Duke . I'm currently running Cakewalk By BandLab as my DAW .
     
    https://soundcloud.com/guitarist-kenny-wilson
     
    https://www.youtube.com/user/Kennywtelejazz/videos?view=0&sort=dd&shelf_id=1
     
    http://www.soundclick.com/bands/pagemusic.cfm?bandID=427899



    #6
    scook
    Forum Host
    • Total Posts : 24146
    • Joined: 2005/07/27 13:43:57
    • Location: TX
    • Status: offline
    Re: My plugin manager can no longer make it through a scan with out crashing after updatin 2017/06/02 13:09:20 (permalink) ☼ Best Answerby kennywtelejazz 2017/06/04 07:09:03
    Do not run VST reset as the routine method for scanning plug-ins in SONAR. A VST reset should be performed as a last resort to clear up problems with the plug-in list. FWIW, there is no need to run an additional scan after a reset. The reset process removes all the information in the registry VST inventory then performs a scan.
     
    Make sure the scan path is not scanning paths that do not contain VST plug-ins. Also do not add redundant paths. The scanner recurses though the paths listed in the scan path. Maybe listing the paths listing in your scan path found in Preferences > File > VST Settings would be a good idea.
     
    I avoid adding 32bit plug-ins to the 64bit scan path when the vendor supplied a 64bit version of their plug-in. This reduces the amount of data being scanned.
     
    Sometimes generating a log can help. To create a scan log hold the SHIFT key while clicking the Scan button in Preferences > File > VST Settings. This is the preferred place to launch the scanner whether running a regular scan or reset.
     
    The problem may not lie with the plug-ins that are failing but a plug-in preceding them. Moving plug-in that fail temporarily out of the way in order to get a scan to complete is the method I use. Do NOT repeatedly run resets. Repeat the regular scan process. Once the process completes normally, add the failed plug-ins back into the scan path and scan again.
     
    Once a complete scan is performed, try using the default automatic background scan.
     
    #7
    kennywtelejazz
    Max Output Level: -3.5 dBFS
    • Total Posts : 7151
    • Joined: 2005/10/22 06:27:02
    • Location: The Planet Tele..X..
    • Status: offline
    Re: My plugin manager can no longer make it through a scan with out crashing after updatin 2017/06/02 15:06:11 (permalink)
    scook
    Do no run VST reset as the routine method for scanning plug-ins in SONAR. A VST reset should be performed as a last resort to clear up problems with the plug-in list. FWIW, there is no need to run an additional scan after a reset. The reset process removes all the information in the registry VST inventory then performs a scan.
     
    Make sure the scan path is not scanning paths that do not contain VST plug-ins. Also do not add redundant paths. The scanner recurses though the paths listed in the scan path. Maybe listing the paths listing in your scan path found in Preferences > File > VST Settings would be a good idea.
     
    I avoid adding 32bit plug-ins to the 64bit scan path when the vendor supplied a 64bit version of their plug-in. This reduces the amount of data being scanned.
     
    Sometimes generating a log can help. To create a scan log hold the SHIFT key while clicking the Scan button in Preferences > File > VST Settings. This is the preferred place to launch the scanner whether running a regular scan or reset.
     
    The problem may not lie with the plug-ins that are failing but a plug-in preceding them. Moving plug-in that fail temporarily out of the way in order to get a scan to complete is the method I use. Do NOT repeatedly run resets. Repeat the regular scan process. Once the process completes normally, add the failed plug-ins back into the scan path and scan again.
     
    Once a complete scan is performed, try using the default automatic background scan.
     




    Well scook ,
     
    You have certainly said a lot here ...
    This is the longest post I have ever seen of yours ...I hope I didn't piss you off ...
     
    FWIW , I had never ran a full on reset VST scan until recently on my other Win computer ...
    T Racks CS had gone MIA on me within SONAR and after doing the full on reset I was able to use it again ...
     
     
    On this computer maybe I shot myself in the foot by starting it off with a reset VST scan after the update ..
    I may have assumed falsely that a full on reset VST scan was the right approach after having done a full update ..
    If people think I'm an a hole fine ...maybe someone else down the line may learn from this
     
    thanks for the info 
     
    Kenny

                       
    Oh Yeah , Life is Good .
    The internet is nothing more than a glorified real time cartoon we all star in.
    I play a "Gibson " R 8 Les Paul Cherry Sunburst .
    The Love of my Life is an American Bulldog Named Duke . I'm currently running Cakewalk By BandLab as my DAW .
     
    https://soundcloud.com/guitarist-kenny-wilson
     
    https://www.youtube.com/user/Kennywtelejazz/videos?view=0&sort=dd&shelf_id=1
     
    http://www.soundclick.com/bands/pagemusic.cfm?bandID=427899



    #8
    scook
    Forum Host
    • Total Posts : 24146
    • Joined: 2005/07/27 13:43:57
    • Location: TX
    • Status: offline
    Re: My plugin manager can no longer make it through a scan with out crashing after updatin 2017/06/02 15:16:23 (permalink) ☄ Helpfulby kennywtelejazz 2017/06/04 05:49:48
    Not upset at all.
     
    Some problems need longer replies fortunately most do not. There were a few things to cover in this thread.
     
    VST reset can be a quick fix. A little understanding of the process can assist with a quicker fix.
     
    #9
    bwbalint
    Max Output Level: -85 dBFS
    • Total Posts : 296
    • Joined: 2015/03/28 17:13:56
    • Location: Eastern USA
    • Status: offline
    Re: My plugin manager can no longer make it through a scan with out crashing after updatin 2017/06/02 17:28:52 (permalink)
    Recently after adding Vocalign Project, the automatic background scan was getting stuck at Zeta +2. I noted that Vocalign Project and Zeta +2 are in the same path,' C\:Program Files\Common Files\VST3. '  I tried several times, but same thing.  Stuck on Zeta +2.  
     
    I deleted the Zeta+2 folder.  Rescaned, and this time it completed without issue.  Reinstalled Zeta+2 via CC, and everything is showing up and running as expected.  
     
    I am not sure if this was the most correct procedure, but it seemed to work.  

    CbB latest incarnation, Focusrite Scarlett (2nd generation), WIN10 1809 build,  , MCU pro , Yamaha Motif classic 6 , focusrite ASA one
    #10
    scook
    Forum Host
    • Total Posts : 24146
    • Joined: 2005/07/27 13:43:57
    • Location: TX
    • Status: offline
    Re: My plugin manager can no longer make it through a scan with out crashing after updatin 2017/06/02 17:35:45 (permalink)
    The automatic scan should never get stuck on a plug-in that has already been scanned. The automatic scan should only scan new plug-ins. Make sure the "Rescan Failed Plug-ins" and "Rescan Existing Plug-ins" are NOT checked in Preferences > File > VST settings. These options are intended for temporary use with the manual scan option.
    #11
    dcumpian
    Max Output Level: -34 dBFS
    • Total Posts : 4124
    • Joined: 2005/11/03 15:50:51
    • Status: offline
    Re: My plugin manager can no longer make it through a scan with out crashing after updatin 2017/06/02 17:54:22 (permalink)
    FYI, I have had plenty of problems with the Youlean Loudness meter plugin. So much so that I've completely removed it. Apparently, the developer is aware of the problems but hasn't gotten around to fixing them.
     
    Dan

    Mixing is all about control.
     
    My music:
    http://dancumpian.bandcamp.com/ or https://soundcloud.com/dcumpian Studiocat Advanced Studio DAW (Intel i5 3550 @ 3.7GHz, Z77 motherboard, 16GB Ram, lots of HDDs), Sonar Plat, Mackie 1604, PreSonus Audiobox 44VSL, ESI 4x4 Midi Interface, Ibanez Bass, Custom Fender Mexi-Strat, NI S88, Roland JV-2080 & MDB-1, Komplete, Omnisphere, Lots o' plugins.    
    #12
    kennywtelejazz
    Max Output Level: -3.5 dBFS
    • Total Posts : 7151
    • Joined: 2005/10/22 06:27:02
    • Location: The Planet Tele..X..
    • Status: offline
    Re: My plugin manager can no longer make it through a scan with out crashing after updatin 2017/06/04 06:07:29 (permalink)
    scook
    The automatic scan should never get stuck on a plug-in that has already been scanned. The automatic scan should only scan new plug-ins. Make sure the "Rescan Failed Plug-ins" and "Rescan Existing Plug-ins" are NOT checked in Preferences > File > VST settings. These options are intended for temporary use with the manual scan option.




    OK scook  I have to give it to you , I did what you said yesterday after I updated SONAR on my main PC .
     
    Old Kenny  "Made sure the "Rescan Failed Plug-ins" and "Rescan Existing Plug-ins" were NOT checked in Preferences > File > VST settings."
     
     
    I don't know what happened next because it all happened so fast I missed it
    Walked into my kitchen to get a fresh cup of coffee and when I got back my scan was over ...
    There were no crashes , and everything was there where it was supposed to be
     
    Now I'm starting to wonder if Cakewalk should create an online detention classroom for all the dumb a$$ed holdovers that don't know some of the basics I'm not gonna mention any names but I know where I'll be after 3 O clock
     
    What can I possibly say at this point ? other than Hey scook I'm glad you came down hard on me 
     
    thank you ,
     
    Kenny
     
     
    post edited by kennywtelejazz - 2017/06/04 06:52:00

                       
    Oh Yeah , Life is Good .
    The internet is nothing more than a glorified real time cartoon we all star in.
    I play a "Gibson " R 8 Les Paul Cherry Sunburst .
    The Love of my Life is an American Bulldog Named Duke . I'm currently running Cakewalk By BandLab as my DAW .
     
    https://soundcloud.com/guitarist-kenny-wilson
     
    https://www.youtube.com/user/Kennywtelejazz/videos?view=0&sort=dd&shelf_id=1
     
    http://www.soundclick.com/bands/pagemusic.cfm?bandID=427899



    #13
    kennywtelejazz
    Max Output Level: -3.5 dBFS
    • Total Posts : 7151
    • Joined: 2005/10/22 06:27:02
    • Location: The Planet Tele..X..
    • Status: offline
    Re: My plugin manager can no longer make it through a scan with out crashing after updatin 2017/06/04 07:08:31 (permalink)
    dcumpian
    FYI, I have had plenty of problems with the Youlean Loudness meter plugin. So much so that I've completely removed it. Apparently, the developer is aware of the problems but hasn't gotten around to fixing them.
     
    Dan




    Hi Dan ,
    Thank you for the info  I'm glad I nixed that plug early in the game ...
    The TDR Kotelnikov I had on that computer was on there for years and it came up as from 2015 ...
    I'm sure if I updated w a more recent version it would be OK ...
    The TX16x was another one I haven't used much ...
    Had I known what I know now I'm sure things may have worked out different....
    FWIW, none of these I consider a loss ...
     
    all the best ,
     
    Kenny
     
     

                       
    Oh Yeah , Life is Good .
    The internet is nothing more than a glorified real time cartoon we all star in.
    I play a "Gibson " R 8 Les Paul Cherry Sunburst .
    The Love of my Life is an American Bulldog Named Duke . I'm currently running Cakewalk By BandLab as my DAW .
     
    https://soundcloud.com/guitarist-kenny-wilson
     
    https://www.youtube.com/user/Kennywtelejazz/videos?view=0&sort=dd&shelf_id=1
     
    http://www.soundclick.com/bands/pagemusic.cfm?bandID=427899



    #14
    scook
    Forum Host
    • Total Posts : 24146
    • Joined: 2005/07/27 13:43:57
    • Location: TX
    • Status: offline
    Re: My plugin manager can no longer make it through a scan with out crashing after updatin 2017/06/04 13:16:13 (permalink)
    None of those plug-ins may be the problem. Now that the scanner has run to completion I would not be surprised if adding the plug-ins back and running scan again (or if automatic background scan is enabled), they will get picked up. Just do not run a reset or have the two scan options set. Sometimes a plug-in that does scans correctly trashes memory in a way that causes plug-ins to fail later on in the process.
    #15
    Jump to:
    © 2024 APG vNext Commercial Version 5.1