Confused about VI Player - do I really need 25 instances?

[rgames]

I just started using the VI with SE and I'm a bit confused about the player - based on a search in the forum it seems that I need a separate VI for each instrument. In other words, where I used to have one instances of Halion with 10 channels used, I now need 10 separate VI's. Is that correct? So, to run the entire orchestra, I'd need something like 25 VI's. How in the world do you keep track of all those windows?

I must be missing something because the library came with presets that include separate violin/viola/cello/bass in the same VI instance. But I don't see any way to select instruments other than with keyswitches. So if, for example, viola and violin play at the same time (which happens pretty darn often!), I'd have to use two separate instances of the VI.

I'm certain I'm missing something obvious here...

Thanks in advance,

rgames

[plowman]

The short answer is yes, you'd need twenty-five different instances. This is not an uncommon dismay to people from a Giga or Halion background.

I'm not an expert with VST plug-ins outside of the sequencer. But if you get a wrapper like Plogue Bidule, you can open all your VI's within that program and have a main point of access, allocate channels to each VI, etc.

Many of us open our "twenty-five VI's" within our sequencer per Audio Instrument (track). The channelizing happens there.

"How in the world do you keep track of all those windows?" I often ask myself the same thing. But over time, you adapt. As you build your template, you'll find that you don't have to look under the hood of each VI that often.

[Conquer]

Hi rgames. You're not missing anything - as Plowman says, that's the way the VI works. The lack of multiple MIDI channels is a shock at first, but I've found that the extensive switching facilities - you can choose keyswitches, CC commands, pitch wheel, velocity or playing speed to change patches - partially compensates.

I use the VST host Forte to run multiple VI instances alongside other programs such as GVI and Kontakt. It works well. To keep track of the instances it's best to create a score-like template. All the playing styles for one instrument/ensemble can comfortably be accomodated within one VI, and if you give each VI instance a clear name (e.g. 'VSL Solo Trumpet', 'VSL 1st Violins', etc.) within your sequencer or VST host, it's not too hard to keep track of where everything is.

Good luck!

[JWL]

@Plowman said:

As you build your template, you'll find that you don't have to look under the hood of each VI that often.

That's so true. Each instance can be set up pretty much the same way with a certain variety of short/long/perf etc patches on the same keyswitches. Even where these patches/keswitches may differ from one instance to the next, a cheat sheet helps.

Here are some ideas:

Method 1. On a sheet of paper (horizontally) you can print a jpg of a keyboard of about two octaves--- Something like this can be easily assembled in Photoshop (or some other graphics app-- even MS Word or Apple Works will work). http://www.abcteach.com/free/p/piano_keys_bw.jpg

Cut-paste-edit, etc.

Print out as many of these on one page to represent each VI instance you have loaded. Use as many pages as needed. Chances are you won't need more than two pages if you size the keyboard just right. If you really wanted to get clever, you could make three columns of 10 keyboards each to keep it all on one sheet. Again, this is horizontal (landscape) letter size, A4, or what ever works best for you--

Mark each key with the appropriate articulation: C0= matrix 1, C#0 matrix 2... C1 patch 1A, C#1 patch 1B, etc... You could also simplify it further by just writing the actual articulation (ie: sus, leg, perf4L, stacc, det...)

It's a great quick visual reference.

Method 2. Make a print of just one keyboard actual size, label the keys and attach the sheet to some heavier poster board or cardboard. Align the sheet on your keyboard. Make one sheet for each instance which may have a different arrangement of articulations. Mark each sheet with the instrument name (and even MIDI channel or other helpful info).

Method 3. If you have a separate mini keyboard such as one of the Novation or M-Audio Oxygen 8 models, you can just label those keys without having to print out anything.


Method 4. Use a piece of white surgical tape directly on your 88-key controller just above the notes where keyswitches are. Label the white tape.

Once you get a workable template, you'll memorize your keyswitches quickly, and as Plowman says, you won't find yourself needing all VI instances open at once.

[jbm]

I actually like this about the VIs - it's what makes them Vienna "Instruments", not just Vienna Sampler Player Thangs... [;)]

The instrument-based model keeps everything very clear, particularly if you're writing from score, like in Sibelius or Finale. Nice, old-new-school technology. Sweet. Though it's true that keeping track of instances can be a bit hair-raising at times. But, as mentioned, you'll find you seldom go to the VI GUI once you've got your setup sorted out, and arranged everything into templates.

J.

[rgames]

Well, I guess all I can say is that I'm surprised that's how it works. So far, that's the only downside I see to the player, but it's kind of a big one. At least I think so right now, maybe I'll come around...

I suppose it doesn't matter so much for the full libraries because you really can't have too many instruments on one machine. But with SE, you're stuck with one machine for the entire orchestra. If I could at least spread it across two, that would help. Especially since each VI instance takes something like 15 MB of RAM. That's 375 MB lost to just the interface for a reasonable orchestra! That seems very inefficient...

Any rumors of an update that uses channels instead of keyswitches?

(please please please...)

rgames