Vienna Symphonic Library Forum
Forum Statistics

194,489 users have contributed to 42,922 threads and 257,973 posts.

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

  1. Home
  2. Sample Libraries
  3. Synchron Series
  4. Switching time stretch feature on/off with automation (to save CPU)

  • Switching time stretch feature on/off with automation (to save CPU)

    SandrewS
    SandrewS

    Hey all

    I absolutely love the new "stretch" feature of the Synchron Player - it sounds amazing. However, it is obviously very taxing on the CPU. So I was wondering if there is a method to switch the algorithm on/off for individual instruments using automation or something similar. That way one could switch the algorithm on only when it's needed for an instrument and save a lot of CPU capacity when it's not needed. However, the only strech-parameter that is controlable with automation seems to be "Strech Factor".

    Thx in advnace for any help.
  • PaulP
    VSL Team
    PaulP

    Hi Sandrew, 

    Glad you like that cool feature!

    Automization won't be possible, as all affected samples would have to unloaded / reloaded with every change. 
    So it makes sense to be careful with the resources and only apply time-stretching to the slots where you really need it. 

    Best, 
    Paul

    Paul Kopf Product Manager VSL
  • SandrewS
    SandrewS

    Oh, I see. Thanks for the quick answer.

    Hmm, I wonder if the feature could have the option one day to load both sample sets (the original one and the one processed for the time strech algorithm) and so "buy" the option to save CPU while "paying" with a higher RAM consumption. The feature makes the whole orchestra much more versatile, but I don't see how I can employ it for more than a few instruments whith the current CPU demands, but I could imagin loading 1,5x (or so) more data into my RAM.

    That's just me thinking out loud.
  • M
    M

    But this makes no sense if you're using a template (I host my libraries in VE Pro.). It would be extremely useful to be able to activate time stretching via CC at the start of tracks where it was going to be used, and not have it loaded in. Otherwise you have to create a whole new instance or mess with your template simply when you want to use the time stretching feature. 

     

    Can you perhaps address this request properly? 

    Many thanks

    Mike