Vienna Symphonic Library Forum
Forum Statistics

194,964 users have contributed to 42,945 threads and 258,049 posts.

In the past 24 hours, we have 8 new thread(s), 22 new post(s) and 99 new user(s).

  • VEP 6.015318 seriously crashing while scanning plugins

    Hi;

          Bought the VEP 6 upgrade a month ago, was hoping coast might be clear to try it. Seems like it promptly crashes after scanning a plugin or 2. I tried both 32 & 64 bit versions for about 20 minutes. Finally gave up & reinstalled 5, at least I know that version works. Looked like it was trying to scan VST, anyway to force it just to use AU? I'm open to suggestions.

    Thx,

    Dan


  • Hi, 

    I'm experiencing the same problem with Flux VST plugins. When starting to scan Hear3 or SPAT3, VEP crashes immediately (Hear) or hangs at the splash screen (SPAT).

    Hoping for a fix to be released soon - and the option to select which plugin(format) will be included in the scan.

    Best,

    Hans-Peter 


  • Problem just disappeared after uninstall/reinstalling VEP.

    EDIT: Just started crashing again - I can track it down to the Flux VST plugins. After removing the Flux folder in VST, VEP loads without a hitch. Adding it again and VEP crashes. Already reinstalled the Flux plugins, to no avail. 

    Best,

    Hans-Peter


  • Hi, 

    No troubles here on VEP 6.0.15318, Flux Spat3 works and validates as expected on OS X 10.11.6, both VST and AU. 

    Is it an option for you work with the AU version of Flux only?

    Can you send the crash report to support@vsl.co.at?

    Of course I assume that you are using the latest versions of the Flux software...

    Best, 
    Paul


    Paul Kopf Product Manager VSL
  • That's interesting because on Windows(7), using the Flux Center default installation paths, no Flux plugins are found.  Moving the .dll files up in the folder hierachy make them visible to VEP6, but they do not work (the GUI is absent, or VEP crahes). All was normal with VEP5.


  • Flux also killed everything here too. I just kept launching VEP and it must have finally built its cache.