Vienna Symphonic Library Forum
Forum Statistics

199,035 users have contributed to 43,150 threads and 258,878 posts.

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

  1. Home
  2. Sample Libraries
  3. Vienna Instruments Libraries
  4. VE : First Look

  • VE : First Look

    S
    S

    I'm just starting to test Vienna Ensemble.

    First look :

    Vienna Ensemble is "just" a custom host for the Vienna Instrument we already know. So I found the same drawbacks :

     - Each empty VI use some memory

    A fresh empty standalone VE (1 VI already loaded) : 35Mb

    VE + 16 empty VI : 280Mb

    VE + 32 empty VI : 560Mb

     - No "master" optimize/reset button

    I was hoping the developper would add a way to enable optimize for all the loaded VI, but it's not the case.

    Other tests about the memory :

    As explained by DG a few months ago, there is a tips to reduce the loading time with the VI "shared memory".

    (With the VI, you can load a preset, then load this same preset in another VI and the samples are not loaded two times.)

    VE in Nuendo + VE in Bidule : shared memory

    VE in Nuendo + VE standalone : memory not shared.

    Best, 
  • PaulP
    VSL Team
    PaulP

     Hello Stéphane,

    VE as a plugin is one application, the VE standalone is an application of its own, this is by design. As they are two seperate application, memory cannot be shared. 

    Please expect further features with future updates [:)]

    Best,

    Paul 

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

    Thanks Stéphane. So it seems as if the load a standalone template as well as a template in Nuendo is the way to go. Of course it means that one needs more RAM, but as I don't really see my template getting much larger than 10GB (ATM) I guess that if I get a 16-32GB machine, then this is not a problem! However, with only (how can I say only!) 8GB RAM it is an issue.

    DG
  • S
    S

    Hi Paul,

    I understand, and I agree that this behaviour could be useful for some users, but not when you want to preload your librairie before you open your sequencer.

    In fact, it's still possible if you run another host (like bidule) side by side with you main sequencer.

    First look, next part :

    If you use your keyboard to navigate between all the loaded VI (in the left row), the scroll-bar doesn't follow.

    In general, the keyboard behavior is strange (tab, cursor, shift+tab, ctrl+tab), like with the VI 
  • S
    S

    Setup : Vista 64, Plogue Bidule 64, Vienna Ensemble 64

    With the Vienna Instrument, the first load is slow, but the second one is faster (cache behaviour ?) 

    With VE, I load a preset which use about 4.8Go 

    First load : 7mn30

    Second load : [b]9mn 40[/b]

    It's strange that the second load is slower.

    I've Nuendo 4 32 and 64 bits on this computer.

    At first, I try VE with the Nuendo 64 bits release. Then I've try Nuendo 32 bits. It detects "Vienna Ensemble x64.dll". I can't use it (normal behavior), but the problem is that it didn't detect the 32 bits Dll. I had to temporary move the 64 bits dll.

    It seems the two VE release have the same ID.
  • S
    S

    I don't understand why the VE service stay in the taskbar, it doesn't help the user to find the correct window, and I don't understand why we need this window in the taskbar.

    I assume,VSL will add some features in it like a "disconnect mode", or the possibility to preload samples without loosing memory with the unused VI Gui.

    Another thing about the VE Windows :

    Is it possible to have the preset name before the software name ?

    Actually, if I load a preset named "Strings", in the taskbar, I see only "Vienna Ensemble" because there isn't enough space to read the preset.

    It could be easier if the Window's name were "Strings - Vienna Ensemble". 

    Best