Failed plugin

Author
kmeals9898
Max Output Level: -90 dBFS
  • Total Posts : 1
  • Joined: 2013/07/05 21:39:00
  • Status: offline
2013/10/22 21:43:56 (permalink)

Failed plugin

Is there an easy way to find out which plugin failed during the VST scan. I have one which causes "Cakewalk VST Scan has stopped working" to pop up. It still finishes to scan the rest of the plugins, so long as you don't hit close program or close out the box till it finishes. Debug doesn't do anything except closes out the rest of the VST scan.
Cakewalk Sonar X-2 Studio
#1

2 Replies Related Threads

    scook
    Forum Host
    • Total Posts : 24146
    • Joined: 2005/07/27 13:43:57
    • Location: TX
    • Status: offline
    Re: Failed plugin 2013/10/22 21:54:33 (permalink)
    It is a bit of an iterative process (i.e. move all the plug-ins out of the scan path and add them back in until the offender is found) but it should continue to happen. You may want to check Preferences > File > VST Settings and make sure "Re-scan Failed Plug-ins" is unchecked. Also "Re-scan Existing Plug-ins" is normally unchecked too.
    #2
    2:43AM
    Max Output Level: -68 dBFS
    • Total Posts : 1147
    • Joined: 2013/06/24 07:59:49
    • Location: PHX
    • Status: offline
    Re: Failed plugin 2013/10/23 06:42:54 (permalink)
    Also, if you have many plugins, try limiting the scan down to only 32-bit plugins or 64-bit plugins. This bolsters the fact that separating 32 vs. 64-bit plugins is a good idea. It aids in troubleshooting and sorting on the back-end.  In Sonar, however, it's seamless; and you build your plugin list using the Plugin Layout tool to your liking.
     
    Some of the plugins that can be annoying in Sonar are sometimes the SynthEdit variety.  Some are coded very poorly! I had to ditch my entire collection of 'm' free plugins, e.g. mComp, mPhaser, mFilter, etc., because they all did not work using BitBridge.
    #3
    Jump to:
    © 2025 APG vNext Commercial Version 5.1