Vienna Symphonic Library Forum
Forum Statistics

193,964 users have contributed to 42,904 threads and 257,885 posts.

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

  1. Home
  2. Software
  3. Vienna Ensemble Pro 7
  4. Kontakt instances in VEP7 take ages to unload

  • Kontakt instances in VEP7 take ages to unload

    E
    E

    Hello!

    I have a VEP7 orchestral template with around 50 instances of Kontakt 5.8.x in a single VEP7 instance. Loading this 50Gb template takes some time but nothing unusual. I use it mainly with Dorico and it works perfectly fine on my Windows 10 PC with 64Gb of RAM and Intel i9 8-core CPU.

    But alas! When comes the time to close VEP7 after a hard day of working, it takes ages for VEP to quit and for the RAM to be free again. Loading the template only takes a few minutes, but unloading it takes up to one hour, sometimes more. When I check the task manager I see the RAM curve lowering painfully slowly.

    A few notes:

    • It was already the case with VEP6 and my older CPU/motherboard configuration, but it's become unbearable with a full Kontakt template
    • The behaviour is the same with various versions of Sibelius and Dorico
    • My full VI orchestral template (~70-80 VI with the Dimension Strings) loads and unloads like a charm

    Has any of you experienced the same behaviour? Do you have any workaround? I hate to "force quit" software, especially audio software with iLock as I've encountered a few issues (e.g. iLock not recognized after force quit). I understand this is probably a Kontakt issue but I was unable to find any clue when searching on that side.

    Thanks a lot for your help!
  • Andreas8420A
    VSL Team
    Andreas8420A

    Hi Esther,

    Deallocating samples is quite an intense process handled differently by different sample players inside VE Pro. But regardless - it's the plugin (= Kontakt) that unloads the RAM, not VE Pro. Force-Quitting VE Pro is one option that usually should not harm your system (unless you have not saved your project). I am afraid this "brutal" way will not be implemented into the VE Pro software - it has to be executed manually if you want to do that. 

    That being said, it *can* be dangerous if the operating system fails to unlock certain system resources like shared memory, for instance.

    Best regards,
    Andreas

    VSL Team | Product Specialist & Media Editing
  • ErisnoE Erisno moved this topic from Vienna Instruments Pro on
  • D
    D

    @Andreas8420 said:

    Hi Esther,

    Deallocating samples is quite an intense process handled differently by different sample players inside VE Pro. But regardless - it's the plugin (= Kontakt) that unloads the RAM, not VE Pro. Force-Quitting VE Pro is one option that usually should not harm your system (unless you have not saved your project). I am afraid this "brutal" way will not be implemented into the VE Pro software - it has to be executed manually if you want to do that.

    That being said, it *can* be dangerous if the operating system fails to unlock certain system resources like shared memory, for instance.

    Best regards,
    Andreas

    Hello Andreas84,

    the problem is, that if you want to disable an instance its the same pain. VEP7 is not responding long time, normal workflow is impossible.

    If VEP7 couldn't take the responsibility and just somehow tell the OS to kick out the plugin from the RAM at once, it should be able to go on with the work and does not block itself and the DAW.
    As an implementing idea could be a separate thread for holding each plugin.

    Best regards.