Vienna Symphonic Library Forum
Forum Statistics

182,328 users have contributed to 42,218 threads and 254,755 posts.

In the past 24 hours, we have 2 new thread(s), 9 new post(s) and 52 new user(s).

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. OSX- Is there a way to Disable only 64 bit versions of Plugins in VEP 64?

  • OSX- Is there a way to Disable only 64 bit versions of Plugins in VEP 64?

    T
    T
    In Logic there is an AU manager and a way to run the application in 2 versions (32 and 64 bit). Each version has its own AU manager to manager which plugin is open. I have a few plugins that act a bit unstable in 64 bit mode in Logic and crash the initial scan in VEP. In Logic I just I disable the 64 bit versions and use the 32 bit versions. Since both the 32 and 64 bit versions reside as a single AU Component in the Components folder how do I disable a 64 bit version but not a 32 bit version of the plugin? Basically I only want to run a few plugins like Kontakt in VEP 64 on my mac since I am having some processor issues with Logic and I am hoping to resolve the issues with VEP since VEP handles core distribution better. But what if I only want certain plugins to be active in Logic but not in VEP? Is there a way to control this because right now I am stuck. Thanks, DR
  • K
    K

    There is no easy way to achieve this, but note that if an AU crashes VE Pro during the plugin scan, it will be ignored on following scans and marked disabled. Only on a manual full rescan from the VE Pro settings will the plugin be scanned again. Such a scan will rarely be necessary though, as VE Pro detects new plugins on startup and will only scan those.
  • T
    T
    Thanks, but the issue is that it crashes the VEP scan so every time I reload it trys to rescan and crashes. I guess I could move the plugin during the scan to my Components (Disabled) folder and then move it back after the scan, but not sure if VEP will try to rescan again at some point?
  • K
    K

    In the event of a crash during scan, the plugin that caused the crash should be disabled for the next scan. Is it crashing on the same plugin each time?
  • T
    T
    Yes