Vienna Symphonic Library Forum
Forum Statistics

200,867 users have contributed to 43,214 threads and 259,141 posts.

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

  • Kontakt Multiprocessing now on?

    I was reading the manual and on Pg. 10 "A note about Multi Processing" it says that you recommend the multi processing to be ON in Kontakt. Before (VE Pro 4) i thought it was recommended to be OFF - so that VEP can handle the spreading of the work load..

    Should it be on or off? ..or was I wrong about that in VE Pro 4?

    Thanks, J


  • last edited
    last edited

    In most circumstances it's better to turn it off, but the manual mentions this specific case:

    @Another User said:

    Certain plugins, such as Native Instruments Kontakt, also offer the possibility of multithreading, which

    may complicate things further. If using Vienna Ensemble PRO to host such a multi-timbral plug-in

    exclusively in one instance, it might give better performance to turn on multi-processing in Kontakt while

    keeping a low thread count (1-2) for Vienna Ensemble PRO. 


  • Thank you for the response! I'll leave it off. ~J

  • last edited
    last edited

    @Karel said:

    Certain plugins, such as Native Instruments Kontakt, also offer the possibility of multithreading, which

    may complicate things further. If using Vienna Ensemble PRO to host such a multi-timbral plug-in

    exclusively in one instance, it might give better performance to turn on multi-processing in Kontakt while

    keeping a low thread count (1-2) for Vienna Ensemble PRO. 

     

    Karel, just to make sure I understand you correctly, does that mean if you have one VE PRo instance hosting exclusively only Kontakt instances (say 12), and another instance hosting Omnisphere, etc that it would be better to turn it ON? 

    If that is the case,  that would simply be a matter of organizing the multi-timbral plugins in their dedicated instances.


  • To keep it simple, I'd just turn it off unless there are actual performance issues.