Hi Rob,

there´s quite a few options you have here. You will find out quickly which options you need for different kinds of orchestrations, so you can build your own presets for each instruments, with different levels of complexity and then set up different Vienna Instruments on your PCs.
There´s a lot more articulations coming your way, and as everybody has a different templare, it really depends on your preferences and featured instruments.
Your Ram Management always keeps you informed about your ressources, so when you load another instance of Vienna Instruments, you also know how much you can still load in.
The Solo Strings alone will give you 105.000 Samples, so it´s really up to you to design your favorite settings.

Best, Paul

@Paul said:

Hi Rob,

there´s quite a few options you have here. You will find out quickly which options you need for different kinds of orchestrations, so you can build your own presets for each instruments, with different levels of complexity and then set up different Vienna Instruments on your PCs.
There´s a lot more articulations coming your way, and as everybody has a different templare, it really depends on your preferences and featured instruments.
Your Ram Management always keeps you informed about your ressources, so when you load another instance of Vienna Instruments, you also know how much you can still load in.
The Solo Strings alone will give you 105.000 Samples, so it´s really up to you to design your favorite settings.

Best, Paul

Geez Paul - you guys sleeping over there???


Thanks for the quick reply.


Right now my GS templates have your instruments across 3 PCs (each having 8 ports with assigned panning, midi channel, Gigapulse assigments, etc.)

When I start up my systems with the new VI - how exactly will I load up my template. Will there be a MACRO loader that starts up the 10-20 instances of VI's on each of the 3-4 PC's or do I have to load up each instance on each PC seperately - each day (I'll be spending so much time just getting things up and running each morning)?

Am I making myself clear on that [:)]

Thanks for your reply.


Rob

Rob

Sleep? Hm, good idea.

Again, some options, i would suggest to program a short macro, there´s a lot of good freeware out there, you can also setup your tenplate in any VI chainer...

Does that help?

Best, Paul

@Paul said:

Sleep? Hm, good idea.

Again, some options, i would suggest to program a short macro, there´s a lot of good freeware out there, you can also setup your tenplate in any VI chainer...

Does that help?

Best, Paul

VI Chainer, huh. Haven't used one to date (because of GS) but will look into it. Is V Stack one of these options?


Rob

Yep, good example.

Paul,

Are the VI instances not saved with you rproject by the DAW?

Can we not setup templates within Default Projects etc.?

Colin

Yes, they are saved, yes you can.

But we were talking about using some computers as slaves, without synchronizing many sequencers.

Gotcha, sorry to interrupt! [:O]ops:

Colin

So - I would save a template in SX (Host PC - for all the midi tracks on the slaves) and save another template in V Stack (for the slaves to load up the preassigned template patches?) Sound about right?


Rob

Yes. But V-Stack does not load the templates up when you change projects in your daw. What you do is have a standard template which works regardless of what project you load up on your daw.

Fx-teleport on the other hand loads up different templates on the slave computers as you change project. The problem with this is that it needs to load each template each time. So the advantage of V-Stack is you load your template once on the slave. Then when you load another project the template in V-Stack keeps loaded, and works perfectly with the new track.

Wow.. did you understand that? I almost lost myself there

[edit] spelling

@Christian Marcussen said:

Yes. But V-Stack does not load the templates up when you change projects in your daw. When you do is have a standard template which works regardless of what project you load up on your daw.

Fx-teleport on the other hand loads up different templates on the slave computers as you change project. The problem with this is that it needs to load each template each time. So the advantage of V-Stack is you load your template once on the slave. Then when you load another project the template in V-Stack keeps loaded, and works perfectly with the new track.

Wow.. did you understand that? I almost load myself there

Thanks Christian for the reply. That helps. On the surface, V Stack looks like the way to go. Since I have ONLY used GS these last years on the slaves I know nothing about V Stack. I'll spend some time researching it today.

Thanks again.


Rob

Would anyone care to elaborate on this subject from a Logic user's perspective?

Also, I'm curious how/whether the new software deals with the OS X limit on number of files open in RAM (currently somewhere over 8,000). With 105,000 available for solo strings alone ... well, as you all know, there was no way to use VSL on a Mac without also using EXSManager Pro (which circumvented that limit by stitching together many WAV files into single files).

Does the new software allow more than the OS X limit to be loaded into RAM at once? (I think I read somewhere on the site that it allows 48,000 articulations, but I don't know what that means in terms of files).

Thanks.

- Paul

Also, will it work on Logic Nodes like EXS didn't (sorry I'm new to Logic just this week - haven't even opened it yet).

Colin

@cwillsher said:

Also, will it work on Logic Nodes like EXS didn't (sorry I'm new to Logic just this week - haven't even opened it yet).

Colin

48000 samples I think. The Logic node thing now becomes very interesting.

Anyone care to educate an idiot on VStack. Steinberg doesn't give much informaiton on their site (suprised [:P] ).

I have 3 slave PCs and one Host PC running SX (latest build). A few details of how this Vstack will work in the new VSL VI.

Thanks in advance.

Rob

Brainspawn Forte is apparently far more powerful and better all around VI host - or so I've been told by an intense VI user.

@dpcon said:

Brainspawn Forte is apparently far more powerful and better all around VI host - or so I've been told by an intense VI user.

Thanks Dave. Anyone else have similar experience? VSL - this is a critical element for your new VI technology. Have you tested one over the other? Recommendations?


Rob

We will release all testing results once they are ready and confirmed multiple times.

And yes, of course we are aware of the importance of this issue.

Thanks Paul for the fast response. I have to weigh in HOW I will make this transition and how it will least affect my production (as clients will not care I am basically rebuilding my template / work flow.) Just looking for as little of down time as possible. [[:|]]

Of course another option mentioned throughout the forum is let everyone else 'test' it out and buy into the new program in 5-6 months.


Rob