A Few Basic VI Questions

[JJRoach]

Paul,

I read the FAQ last night (of course, at like 3:30AM) and I found some good stuff in there, but I've been left wondering a few other things (forgive me if I've missed these in a post somewhere or overlooked them in you FAQ)...and am wondering if you, or anyone out there might have some advice:

1)MIDI routing into VI standalone. It looks like the Instruments only recognize Entire MIDI Ports, and not discreet channels. I'd like to have Instance 1 receive Port 1 Channel 1, and instance 2 receieve Port 1 Channel 2...etc..you get the idea...is this a change in the future or have I missed something?

2)Audio Outputs from VI...Again, it looks like there is little control as far as routing out of the Standalone is concerned...I've only seen Audio Drivers/interfaces available...(in my case, either CoreAudio, or MOTU 82[H]. Again, I may have overlooked something.

**My current work-around is using a host that incorporates VI as a plugin (like Bidule or..maybe, DP)**

A Playing Question:

1) it seems as though the Key velocity is the only way to affect the strength of a played note...as compared to your Kontakt 2 Orchestra, where Mod Wheel affected the dynamic. I've been thinking about using the Volume control to help with this, but is there a way to get the samples to behave like your traditional use of the Mod Wheel. ...don't get me wrong here, I know VI uses Mod Wheel for other things, and I LOVE how you've incorporated CC control as a means to access different matrices (hopefully, when I really get the technique of this library into my head and hands, this will eliminate ALL keyswitches...right now I'm learning aobut an articulation tool/macro that someone recently created for the Logic Environment)...

...a few more words on what I'm trying to achieve...Key Velocity will determine Attack, and some sort of CC controller controls linear musical phrasing (crescendi, dynamic expression)...For example, as of right now, I can get harsh attack and strong sustain, soft attack and soft sustain, but it's difficult to get broad attack and full sustain (this is so simple that i'm sure it's already in there, I just haven't found it.)

having spent a couple days with the library, I can't wait to master it!!!

Josh Roach

[david ender]

Hello Josh,

I may be able to answer some of your questions.

1) The standalone can't receive on different MIDI channels for different slots - actually, it's intended for live play where you (normally) play only one instrument. So your workaround is the right way to go, especially since the plugin has the same functionality as the standalone.

2) The same goes for the audio outputs - standalone only routes to the designated main output of your sound card. If you use several plugin instances in a sequencer, you can route your outputs to meet your needs.

3) Key velocity: on the perform page of VI, right-click on the Velocity XF slider to assign a controller of your choice - if your matrices don't use the modwheel, you can also take that, or change modwheel matrices to another controller if you prefer velocity control to work with it. In order to make velocity crossfading work, you also have to activate the Vel XF button.

When you customise existing matrices (or create new ones from scratch), you have to save them in your Custom folder.

I think what you're trying to achieve partly has to be done with Cell crossfading - check out the manual for a bit of info there, or load one of the XF matrices to see how they work (provided they're in your Collection, but I think there are)!

Regards,
David
VSL manuals

[Nick Batzdorf]

Would Jack OS X (http://www.jackosx.com/) be a solution for routing the output of the stand-alone version to your sequencer?

[david ender]

Seems like it could, but why would you want to do that? Of course, if the sequencer doesn't support AU instruments, it might be an approach worth trying.

Regards,
d.

[julian]

Hi David,

A very good reason for wanting to route the output of the standalone to your sequencer and for that matter to have the Matrixes react to different midi channels (to obtain multitimbrality) is RAM!

With opening the standalone you suddenly get, subject to you having the available memort installed in your computer, an extra 2.7GB of loadable sounds!

Yes this isn't as elegant as using VI as an AU plug-in but until the single app RAM limits are resolved it is a solution that works today!

Julian.

[julian]

@JJRoach said:

Paul,


2)Audio Outputs from VI...Again, it looks like there is little control as far as routing out of the Standalone is concerned...I've only seen Audio Drivers/interfaces available...(in my case, either CoreAudio, or MOTU 82[H]. Again, I may have overlooked something.

Josh Roach

Josh,

Couldn't you use the MOTU console to route the outputs of wherever the VI Standalone actually comes out back to the inputs of your DAW - not perfect, agreed, but perhaps a work round.

Julian

[david ender]

@julian said:

With opening the standalone you suddenly get, subject to you having the available memort installed in your computer, an extra 2.7GB of loadable sounds!

Good reason ... not being a Mac user, I didn't know about that!

Cheers,
d.

[JJRoach]

yeah,

That's an idea...I don't think it will give me control as to what outputs I'll be directing audio...I think it only goes out the main outputs...which means I can't split audio...the answer, I've found since I started this thread, is to load VI as a plug-in...(duh, I know)...

I've got master, sending audio to slave, and I'll load VI as a plug-in within Plogue Bidule or Logic, then route out of 828, into Digi 002 of Master DAW....or, I'm also trying out routing all audio to ProTools...so many options, and each one with pros, cons and kinks to work out.

Josh