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

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....

@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

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.

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.

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

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.

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.

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.

@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

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.

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.

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

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...

You wouldn't want pizz and legato violins playing at the same time though would you? Unless you were simulating 1st & 2nd violins, in which case they should be on seperate tracks anyway.

The idea is basically 1 MIDI Channel per 'Instrument' or 'Section'. Each instrument having many articulations available to it via keyswitching, velocity, modulation or whatever controllers you have, plus the automated features built into the VI to save you having to load say all the release patches.

For string quartet or string orchestra you would only NEED 4 well-constructed instances.

Colin

Edit: Percussion, I can understand - We'll have to wait and see how they that one, though again, things like Timpanis, mallet instruments will have a number of articulations so they should probably work just the same.

I still do wonder how this will all work with percussion. Even if you switch matrix's emulating 4 real players changing instruments, you could have to use 4 VI's just for percussion.

Is that true?

Hi Joseph,

there will be designated Vienna Instruments for Percussion.

Gerard,

the loading times of the Vienna Instruments are amazing. So you can go through your arrangement instrument by instrument and use RAM Optimize after the instrument is recorded and then load your next instrument. As you can create your own matrices and presets for each purpose, you simply load the file you need (create instruments with different levels of complexity, always depending on what you need).

The more instruments you want to keep loaded, the more computers you will need to hold the samples.

Of course you can also work with your existing library for a quick layout and then simply reassign the MIDI tracks to the Vienna Instruments....

Best, Paul

Thanks Paul. I look forward to more information on that when its ready.

@cwillsher said:

You wouldn't want pizz and legato violins playing at the same time though would you? Unless you were simulating 1st & 2nd violins, in which case they should be on seperate tracks anyway.

This was just an example - and who is to say what is the 'right' way and what is the 'wrong' way? The fact is in the past I had the flexibility to accomplish usage like this within my workflow. And you actually make my point - they would have to be in separate tracks - but within Giga this was no problem. Having multi-instance floating around to do something as simple as performing multiple layered articulations just doesn't sound like fun.

And BTW - I get frustrated enough with having to jockey with and switch between multiple instances of a competitor's NI Kompakt interface because it only has eight midi channels... [[:|]]

The more I learn, the more the new VI instruments seem more appropriate for live performance...