Vienna Symphonic Library Forum
Forum Statistics

193,851 users have contributed to 42,898 threads and 257,858 posts.

In the past 24 hours, we have 4 new thread(s), 15 new post(s) and 92 new user(s).

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. VEP7.1.x Unloading and Quitting takes too long

  • VEP7.1.x Unloading and Quitting takes too long

    B
    B

    Its a big template and takes about 3 to 4 minutes to load. But takes over 7-8 minutes to quit VEP!

    That's longer than the already too long save time of 4-5min.

    At the end of the day/night waiting 6 to 10 minutes before I can turn off my PC is very annoying and I've taken to force quit by shutting down (after saving of course).I have 3 dedicated farms and they all take nearly double the time just to unload/quit the app than they do to load or save. The more samples loaded the longer.

    Will force quitting do any harm to my projects or the app databases etc?

    Why cant VEP just bail quickly? Once Ive saved why does it have to spend all this time unloading samples? Just dump them already.

     

    Windows 11, 12900k/128gb, nvme, VEPro7.1.1384 (happened since v6), Nuendo (already quit N12 before though)
  • PaulP
    VSL Team
    PaulP

    Hi, 

    Deacllocating samples is quite an intense process that is handled differently by different sample players. 

    Force-Quitting VE Pro is an option that will do no harm, unless you have not saved your project. Unfortunately this "brutal" way is not possible to implement into the software, it has to be executed manually. 

    Best, 
    Paul

    Paul Kopf Product Manager VSL
  • M
    M

    Sorry to resurrect an old thread, but getting back into VE Pro after many years, I'm experiencing similar behavior.

    Paul, by force-quitting, do you mean from the Windows task manager?

    Thanks,
    Mahlon
  • D
    D

    @Paul said:

    Hi,


    Deacllocating samples is quite an intense process that is handled differently by different sample players.


    Force-Quitting VE Pro is an option that will do no harm, unless you have not saved your project. Unfortunately this "brutal" way is not possible to implement into the software, it has to be executed manually.


    Best,
    Paul

    Unfortunatelly the same problem is there at deactivating an instance in VEP7. It is not responding, a workflow is imposible. It takes ages until an instance is unloaded and VEP is reacting again.

    VEP7 should just initiate the dealocating but itself should go on with the work, not blocking itself or the DAW.
    Maybe a solution would be to have independent cpu threads for each plugin used or multiple processes which keep VEP away from this weird dependency.