Vienna Symphonic Library Forum
Forum Statistics

194,159 users have contributed to 42,912 threads and 257,926 posts.

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

  1. Home
  2. Sample Libraries
  3. Vienna Instruments Libraries
  4. Adjustable sample preload? VI suggestions.

  • Adjustable sample preload? VI suggestions.

    P
    P
    Hi there,
    Will you be adding adjustable preload capabilities to VI? I've just got the library. Loving it, but notice that it places huge memory burden on PC (as expected). RAM save isn't the favoured solution for me as I feel it is a bit of cludge, as it was with Halion. I don't want to have to tell the tool what to unload. Is a bit messy for my liking.
    The huge sample base of the symphonic orchestra means that currently it is pretty impossible to load all instruments into a single memory space.
    However, if you offerred the capability to lower the pre-load, that would help out by allowing more to be loaded at the expense of latency?
    I would also suggest - as I believe I have done before - that you add a zero pre-load capability so that no samples are loaded into memory at all, but instead VI acts as an intelligent file routing piece of software. Raise the latency to compensate perhaps. Those of us who don't play music live and merely notate the music could then easily have the entire orchestra loaded into a single PC or perhaps even laptop. And project load times would be very quick.
    As a professional software designer as well as a professional composer, I know that the above is more that feasible to achieve.
  • J
    J
    Good idea, with the EXS 24 VSL library it was possible to choose sample headers as small, medium or large. Ths enabled trade-offs between amount of RAM used and hard disc speed.

    julian
  • cmC
    VSL Team
    cmC
    last edited
    last edited
    i've already posted some considerations in a thread where also paynterr contributed

    @Another User said:

    just a few words .... optimization (be it usage of RAM - headword: memory fragmentation, be it streaming - headwords: buffer sizes and access latency, be it processor load or automated sample selection) is a frail flower.
    you have to be very careful if you touch one component to not screw up the others and only the average and overall optimization is what gives you *performance*

    and in another which i just can't find ... you can't optimize for a certain workflow (besides harddisks are still too slow to deliver usefull amount of data within a reasonable timeframe to realize *zero pre-load* with a bearable latency) - some users are actually unhappy if they have to increase from 256 to 512.
    the structure of the monolithic data files has even driven the archievable performance to the limits, currently we have to accept seektime, latency and maximum throughput of harddrives for storage of data as the bottleneck unless we accept the costs of solid state disks or similar.
    the number of preloaded samples is the least you will find anywhere - configurable or not.
    christian
    and remember: only a CRAY can run an endless loop in just three seconds.
  • T
    T
    what about an "offline" qualitiy, compressed audio version of the samples.
    perhaps like a "construction" kit, for fast workflow and composing, for an "on the road" library with the possibility to load many instruments on a laptop ...

    than a switch to change all to the native version for the final mixdown ...

    it´s just an idea ...

    thomas
  • M
    M
    What about flash drive caching? Use an USB stick for the sample preloads. Would that be possible?
    (Wouldn't have a RAM limitation either.)