Is Gigastudio VI + VSL redundant?

[luga00]

Hi, we are currently upgrading/researching our composition setup and it's been quite a trip.
First we thought to upgrade to Gigastudio 3 + Vienna Library. Then we saw that now we could bring Gigastudio into a host machine using FX Teleport and Giga Teleport (sorry it's been a long time [:)])
Hold on, GVI has now been released so GS3 is out of the window.
What's this? - Vienna Instruments means that GVI is out of the window......

Or is it..?

My question is, If one was planning to use a slave machine purely to run as an orchestral machine using FX Teleport , is VI on it's own satisfatory or is there some advantage to having GVI + VSL + FX Teleport?

For most of the Fable project I was able to trim down the memory use by singling out only the instruments I needed to be loaded (eg single clarinet line, trills etc.) but it seems that maybe VI is not quite as flexible as this(?).

thanks for any replies
Russ Shaw
Lionhead

[Christian Marcussen]

Hi Russ... the VI is completely independant of GS and GVI. The only reason you would want any of them is if you wish to run giga libraries on the slaves as well.

What you may want however is a host application for hosting the VI's. These could be V-Stack, Forte, Chainer or some of the other apps made for this.

Regarding the VI and it's flexibility.

a) The VI can unload all the individual samples of a patch that you arent using.

b) The VI sample engine can load twice (yes TWICE!) the amount of samples as GS.

So dont worry about that.

Does this kind of answer your question? If not, just keep shooting [:)]

I beleive I might have seen you on the VGM list - if so, see you there [H]

[luga00]

Hi Christian

What a great reply, thanks very much for that.

I remember you from VGM also, although I don't post there any more as it got a bit catty at one stage.

I think I'm going to go for the VI in that case. I have a plethora of Gigastudio samples but rarely (if ever) use them, so I think Gigastudio may be resigned to the shelf.

I was hoping to use FX Teleport straight into my DAW via LAN rather than V-Stack, although I'll probably research a bit more into this sometime today.

Thanks again for your reply.
Russ

[cm]

@Another User said:

b) The VI sample engine can load twice (yes TWICE!) the amount of samples as GS

i'd say actually 3.5 times as much - the needed sample buffer ist the half (64 instead of 128 KB per stereo sample) and you should be able to use at least 1.7 GB RAM on a 2 GB machine instead of 1 GB)
christian

[Christian Marcussen]

Now dont you get technical with me! [:D]

hehe - point is. The VI rocks [H]

[luga00]

Sorry, been away from my machine for a while...

Thanks for the reply CM, that sort of power is just what I need.

Sacrilege, I know, but I'll only be using VI on a single machine and as a sketch tool from which the outputted scores will go straight to my orchestrator - I don't really use it to it's full potential so I like to keep the memory usage trimmed down as much as possible.

Russ

[Christian Marcussen]

Then the memory purging function will be your hero. It's not relevant here at the PC farm, but for your use it will be a Godsend. The VI absolutely sounds like the way to go for you!... [H]

[luga00]

Sold! [:D]

[Nick Batzdorf]

@Another User said:

i'd say actually 3.5 times as much - the needed sample buffer ist the half (64 instead of 128 KB per stereo sample) and you should be able to use at least 1.7 GB RAM on a 2 GB machine instead of 1 GB)

And then the programs you end up loading are three 3.5 x as big... [6]

(But only because the big programs are so tempting, of course, since one phrase played in real time with the Speed control and the modwheel might require a dozen cuts and slidings to another MIDI track using the original versions.)

[cm]

@Another User said:

And then the programs you end up loading are three 3.5 x as big...

hehe, the question only was about the amont of samples which can be loaded [:P]
of course you could configure your *gigalike - pro edition - long notes only* patch to only save RAM, but who would want this finally?
IMO the optimize option in VI would be the most efficient way to allow as much instruments as possible, but this depends on the personal workflow.
christian