Vienna Symphonic Library Forum
Forum Statistics

194,710 users have contributed to 42,932 threads and 258,000 posts.

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

  1. Home
  2. Software
  3. Vienna MIR & Vienna Suite
  4. Will VE Pro be multi core aware?

  • Will VE Pro be multi core aware?

    D
    D

    I've read some other threads about VE3 and multi core issues, and it seems like each instance of VE3 gets assigned it's own core by the host/daw.  So folks are able to spread the load across cores by starting up multiple instances of VE3 and balancing their template appropriately.

    For VE Pro, it seems like there will be new challenges with the support for 3rd party VSTis.  It does't seem practical to load an individual instance of VE Pro for each cpu hungry VSTi.  Or will the footprint of VE Pro be so lightweight that this becomes practical?  And if VE Pro is multi core aware, how is this being implemented in order to be compatible with hosts/daws that are multi core aware?

    Really looking forward to release of VE Pro [:D]
  • D
    D

    Could you post a link to a thread where this is discussed, because I've never heard this as a general problem before? I've only ever heard of this as a Logic bug.

    DG
  • cmC
    VSL Team
    cmC

    this is a more general question which needs to look at your setup as a whole - if one app (or plugin) in the chain is not ready for multi-core the whole chain gets bound to one core. with logic this is *by design* for the live-mode.

    this is related to the fact that an audio stream has to *flow* from source to destination and you can't have a bottleneck inserted on its route - eg. there are some plug-ins for which you have to limit cubase to 2 cores because the plug-in cannot use more than 2.

     

    Vienna Software as such is generally multi-core capable - we tested it up to 16 cores so far.

    hth, christian

    and remember: only a CRAY can run an endless loop in just three seconds.
  • D
    D
    last edited
    last edited

    @DG said:

    Could you post a link to a thread where this is discussed, because I've never heard this as a general problem before? I've only ever heard of this as a Logic bug.

    DG

     

     Oh, I'm not really thinking of this a problem, I'm just trying to understand this whole thing a little better.  I just thought that, in general, this is the way hosts handle multi-core processing for VSTis.  Of course my assumption could be wrong.  However, when I watch VSTis load up in Sonar, I notice activity in one core while one is loading, then activity in a different core when another is loading, and so on.

    Also, in Kontakt 3 there is warning about turning on multi-core processing if your host/daw already has multi-core processing enabled.  This led me to believe there might be some contention if your daw has multicore enabled while a single instance of VE Pro was also trying to perform multi-core processing.  I also think the VE Pro's handling of this will be unique since some of the processing occurs "outside" of the host (if I'm not mistaken again [:)]). 

  • D
    D
    last edited
    last edited

    @cm said:

    this is a more general question which needs to look at your setup as a whole - if one app (or plugin) in the chain is not ready for multi-core the whole chain gets bound to one core. with logic this is *by design* for the live-mode.

    this is related to the fact that an audio stream has to *flow* from source to destination and you can't have a bottleneck inserted on its route - eg. there are some plug-ins for which you have to limit cubase to 2 cores because the plug-in cannot use more than 2.

    Vienna Software as such is generally multi-core capable - we tested it up to 16 cores so far.

    hth, christian

     

    Thanks.  This is good to hear!  So let's say I had a project with just a single instance of VE Pro and nothing else (no VST effects in the chain), but within VE Pro I had 8 different VSTis loaded.  Would I see load distribution across cores in this scenario?