Vienna Symphonic Library Forum
Forum Statistics

195,061 users have contributed to 42,962 threads and 258,121 posts.

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

  1. Home
  2. Sample Libraries
  3. Vienna Instruments Libraries
  4. Multitimbral?

  • Multitimbral?

    J
    J
    Is the Vienna Instrument multi-timbral?

    Does it load more than one instrument per instance or is one instance needed per instrument?

    So one VI for Violin, one for Viola, one for Contrabass, one for Cello?

    Or I can have all of these in one instance? It doesn't mention anything about multiple channels per instance.
  • J
    J
    No info on this?

    I can't decipher this from the videos. It looks as if its one Vienna Instrument per instrument.
  • C
    C
    Yep. I would say almost certainly one instrument per instance.

    Though presumably you could load matrices for different instruments and switch between them, provided they were only playing one articulation (or sample set) at a time. ie. you could switch between solo flute and solo clarinet patches but not play them simultaneously within the same instance.

    Colin
  • J
    J
    David Ender confirmed that it isn't multi-timbral.

    The matrix switching is cool, no doubt, but you can't have multiple instruments playing that way. It just allows you to switch between them via keyswitch or whatever.
  • T
    T
    The lack of multi-timbrality is also interesting in that depending on your VST host you are going to be limited to the number of VSTs you can host - even with nothing loaded.

    E.G In CubaseSX3 there is a max of 64 VSTs. This then logically means a max of 64 MIDI tracks (1 per VI instance) so even by using freeze/ram save options you will in SX3 at least not be able to have more than 64 Instruments playing at the same time - might be enough, but I'm not sure....
  • D
    D
    I believe that to play 64 instruments at once you would have to use several computers, anyway - or wait for the 128-bit CPU [[;)]]

    regards,
    d.
  • D
    D
    I can't ever remember haing more than 64 instruments playing at a time, although I have got close. Never on 1 computer though [:D]

    DG
  • T
    T
    I've had 70 running on 1 PC. 5 Instances of HALion each with 16 instruments loaded. Of course I use Freeze and RAMSave but still in effect 70 editable instruments. Whereas the max now is 64 and thats if I choose not to use other VSTs such as Stylus or Atmosphere....
  • D
    D
    last edited
    last edited

    @timkiel said:

    I've had 70 running on 1 PC. 5 Instances of HALion each with 16 instruments loaded. Of course I use Freeze and RAMSave but still in effect 70 editable instruments. Whereas the max now is 64 and thats if I choose not to use other VSTs such as Stylus or Atmosphere....


    Obviously not VSL Performance Instruments though [:D]

    DG
  • T
    T
    No, perf instruments too - not all of them, Little Ugly has over 64 instruments in it to, if I remember correctly - the MIDI file is around somewhere on this site.
  • J
    J
    You shouldn't need anywhere near 64 instruments since an instrument used to sometimes equal an articulation of an instrument. Now, each instance will represent an instrument in its entirety. I think you could get a valid midi mockup with maybe 32 instances.
  • L
    L
    You also have to remember that most of the perf. legato samples loaded are usually not used (every sampled interval from every note, etc.) so this new optimize RAM button should greatly increase the number of perf. instruments that can be feasibly loaded at once!

    January seems so far away...

    - Lindurion
  • J
    J
    I'll say this...

    Depending on how complete you make a track before adding more instruments, the RAM purging feature will be a godsend.

    The Kontakt RAM feature is outstanding and this looks just as good if not better.

    In Kontakt I had one instrument go from 156 MB of RAM down to 20 or so. This will allow you to load much more into RAM provided your workflow accomodates this process.
  • D
    D
    RAM purging allows you to continue working on that track within the limits of the samples retained - i.e., you can still change velocity (especially if you're using velocity crossfades), speed etc. as long as the changes don't affect the actual samples played. If you transpose a part, you'll have to reload all the samples, and optimise again.

    Have a look at the video tutorials for more info!

    regards,
    d.
  • J
    J
    I've watched it. And its cool.

    The only confusion around the feature on the forum here has to do with the process. It won't do you much good to purge the RAM if you aren't done with a track as you'll just end up having to reload the samples since the notes you may be wanting may have been purged.

    Its still an oustanding feature. It just may take some of you a while to get accustomed to it.
  • D
    D
    last edited
    last edited

    @Joseph Burrell said:

    I've watched it. And its cool.

    The only confusion around the feature on the forum here has to do with the process. It won't do you much good to purge the RAM if you aren't done with a track as you'll just end up having to reload the samples since the notes you may be wanting may have been purged.

    Its still an oustanding feature. It just may take some of you a while to get accustomed to it.


    I can't see much use for the RAM purge whilst writing a track. However, it could come in handy if effects like VST reverbs are used with finished tracks. Mind you, then there's MIR...

    DG
  • J
    J
    It would really all depend on your work flow. If you know for a fact that you're finished with a track, you could unload some of the samples. This would give you some head room to add more instruments if you need them.

    It doesn't benefit during the 'making' stage or if you come back and need to add a part to a track, as you'll just have to reload everything.
  • J
    J
    Okay, now that I'm asking questions and have become the bain of the VSL community, it won't hurt to ask another.

    How is percussion handled through the new VI? Since it is not multi-timbral how are multiple percussion instruments handled? Hopefully it isn't an instrument per instance as this would not be a good thing. There must be a way to stack multiple percussion instruments in one VI and have the parts play back correctly.

    Just curious.
  • G
    G
    Hello,

    Maybe I understand it all wrong: but how would I then make an orchestral set-up using VI? That's certainly more than 64 instruments!

    Gerard Beljon
  • E
    E
    I must admit that this has me confused as well. Each VI instance only provides a single midi channel, and a single stereo output? So, for instance, a basic string quartet would require four active instances? And if I want to have say Pizz. violins play alongside legato violins this would require two instances? This makes no sense at all. Even the basic NI Kompakt player can handle 8 midi channels/audio outputs...