Vienna Symphonic Library Forum
Forum Statistics

200,375 users have contributed to 43,197 threads and 259,079 posts.

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

  1. Home
  2. Sample Libraries
  3. Vienna Instruments Libraries (legacy)
  4. ViPro performance settings

  • ViPro performance settings

    Dewdman42D
    Dewdman42D

    I'm looking for some advice and/or tips about how to optimally configure ViPro for performance.

    I ahve searched all over this forum and seen all kinds of conflicting advice botu Preload for example.  where should I set it?  Is there any performance disadvantage to setting it at the largest setting, aside from it uses more memory that way?

    What about some of the other settings?

    I'm not typically using a large template and I ahve a lot ram, so most likely I am not too concerned about running out of RAM, maybe later I will be.  

    I tried to disable all cells and load on midi activity, but VEP and ViPro were coughing and spitting all over the place, and even after playing it all the way through, I would have thought all relevant cells would have loaded but its was still coughing and spitting after that until I enabled all cells.

    And basically I did not see my ram usage go up at all when I hit the enable all cells button, even though half the cells were greyed out prior to that.

    I have SSD drive for my samples and I read about people using very low Preload settings, but I am really not sure how to go about determining the best value to use here, and some of the other parameters related to voices and stuff...(shrug)..no idea how to optimize that stuff.

    help?
  • bbeliusB
    bbeliusB

    High preload size: Samples need more RAM, longer loading time, higher performance, more stable with lower latency settings

    A high preload size makes sense when you have much RAM and don't often switch between different VEP projects because the loading time is higher. Because the CPU has more time to get the part of the sample not loaded in RAM (because it has a bigger chunk loaded in RAM), you can lower your latency settings without pops, clicks and drop-outs (if you have many short notes (perf stac, pizz...) this can quickly get an issue).

    My advice: if you have a multi-pc setup and enough RAM, turn it up as high as you can. If you have a single machine setup, you should have enough headroom for DAW and other programs.
    In my experience some instruments are more immune to pops and clicks on low latencies then others. (higher preload sizes: Syn. Pianos, Starter Editions, Strings)

    Ben@VSL | IT & Product Specialist
  • Dewdman42D
    Dewdman42D

    Makes sense.  I dont have huge templates.. yet.  I have 128gb of ram and I'm barely using it with 100 track VSL orch projects.  So I guess I can go full max on the preload, though its still a hassle to sit and wait a couple minutes to load a project...

    any other settings i should fine tune in there?