Vienna Symphonic Library Forum
Forum Statistics

196,620 users have contributed to 43,021 threads and 258,416 posts.

In the past 24 hours, we have 0 new thread(s), 0 new post(s) and 88 new user(s).

  1. Home
  2. Sample Libraries
  3. Vienna Instruments Libraries
  4. Vienna Ensemble CPU usage

  • Vienna Ensemble CPU usage

    M
    M

    Is VE supposed to be constantly using about CPU (about 30% in my case) - even when nothing is playing...?!

    I have two instances of the VE VST, with a total of 25 instruments loaded, using FX Teleport to host remotely from another machine (running Sibelius 5.1).
  • PaulP
    VSL Team
    PaulP

    Hi Mike,

    please give us some specs of your system, that will be a big help in answering your question [:)]. 

    I am not using FXTeleport, but maybe some fellow FXT user can chime in here.....

    Thanks,

    Paul 

    Paul Kopf Head of Product Marketing, Social Media and Support
  • D
    D

    FXT is a trade-off between PCs. Every time you load an FXT wrapper the CPU usage on the host will go up. However, the thing is to see whether or not it goes up more or less than when your VSTi are loaded locally.

    However, when using sample libraries, FXT is nearly always useful, not so much because of the CPU offload, but because of the "memory used for samples" offload.

    As Paul say, please include your system specs, because some of us have at least two set-ups that we may be able to compare for you.

    DG
  • M
    M

    The machine is an Intel P4 3.2Ghz with 4Gb memory, /3Gb switch, two hard disks.  While "idle" (i.e not playing anything) the FXT server (server.exe) sits at around 8% CPU, and ViennaEnsemble.exe fluctuates between 20% and 25% (according to Task Manager).

    I have another machine, pretty much the same spec, also using FXT, but with GVI.  On that machine server.exe runs at about 8% when idle, but that's it.  GVI seems to only use CPU when it's actually doing something!

    As I said, I was just curious.  I was just surprised to see 30% CPU even when it was doing nothing at all - it's been totally silent for hours and 30% CPU throughout!  But it all works well.