GUYS,

Here is the deal .....

When launching a VI plug-in in Logic7 (or any daw), the memory used by that plug-in does NOT go to Logic, it goes to VSL-server...

If on the same computer you launch VI stand-alone the memory ALSO goes to the VSL-server.....


So you CANNOT gain access to more VI memory since even when using VI as plug-in it is actually stand-alone.

The thing to do is have a 2nd computer, on which you create a Plogue Bidule session, that you pipe back into the main Computer....you don't even need a Midi Interface on the MAC since you can go to AudioMidiSetp and run Midi over ethernet cable.

So if you only have 1 computer, your DAW will allow for it's own 3gig of EXS24 AND an additional 3 gig for VIs...............it took me a gruelling week of trouble shooting to figure all this out [;)]


SvK


ps: Maya confirmed this

the good news:

In Logic you have access to circa 3 gig of RAM....Use that RAM for old EXS24 VSL and you can still open in the same session another circa 3gig of VI instruments (since the VI RAM does not increase the RAM used by Logic.

SvK

On my main G5 in one Logic session I am running 2.9 gig of VI plug-ins (violins,violas,celli,basses)....AND 2.9 GIG of EXS24 VSL (epic horns, flutes, percussion, misc)

that is a total of circa 6 gig......

To be totally clear: When you launch your daw, and open up 3 Gig worth of VIs......none of that memory went to your DAW, it went to VSL-server (that is why it is called a server)....You now still have access to 3 gig worth of EXS24s.

SvK

SVONKAMPEN wrote: "When launching a VI plug-in in Logic7 (or any daw), the memory used by that plug-in does NOT go to Logic, it goes to VSL-server...

If on the same computer you launch VI stand-alone the memory ALSO goes to the VSL-server..... "

This does not appear to be true on my Mac running Logic VSL AU and VSL Standalone. Try this test: Open the Apple Activity Monitor (in utilities folder in applications). Start up Logic. Load the VSL AU. Activity Monitor will show VSL-Server gaining RAM space as you load a preset into the VSL AU.

Now run VSL Standalone on the same computer and load a preset. Activity Monitor clearly shows NO MORE RAM going to VSL-Server, but instead a new process starts up called 'Vienna-Instruments-Standalone', and it gains RAM space (the VSL-Server process does not). You can clearly see *both* the 'VSL-Server' with its own amount of RAM dedicated to the VI loaded into the Logic VI AU PLUS the 'Vienna-Instruments-Standalone' with its own amount of RAM dedicated to the VI loaded into it.

As far as I can see, this means these are two different processes each capable of using their own maximum RAM within the computer [:D]

Figured out a way to run both Logic with its VSL VI AU + VSL VI Standalone, and access Standalone from within Logic such that Standalone becomes a type of 'external' sound bank.

Try this (this assumes you are using Core Audio for Logic):

A) Run the MIDI PIPE app mentioned above in this thread:
Start this app first. Create a 'Pipe' with virtual MIDI IN and virtual MIDI OUT (MIDI IN= MidiPipe Input 1; MIDI OUT= MidiPipe Output 1 with 'Pass Through' option checked).

B) Start LOGIC:
Part I: Preferences... Audio Hardware and Drivers: Use Core Audio, such as Built-in Audio Driver. Logic is set up to receive MIDI input from the master keyboard. Create a VSL V.I. AU instrument in Logic's arrange page.

Part 2: Environment... MIDI Instruments... Create a multitimbral MIDI instrument named 'VI Standalone', and set its Port to 'MidiPipe Input 1', and Channel = 'All'.

Part 3: Set up a MIDI track in Logic's Arrange page dedicated to the new 'VI Standalone' MIDI instrument. Make the track record-ready; playing the MIDI master keyboard will send MIDI to Midi Pipe (ie: to the VSL V.I. Standalone- see next step below).

C) VSL V.I. STANDALONE:
Preferences... Settings... Audio Driver = Core Audio, such as Built-In Audio; MIDI IN = MidiPipe Output 1.

@svonkampen said:

GUYS,

Here is the deal .....

When launching a VI plug-in in Logic7 (or any daw), the memory used by that plug-in does NOT go to Logic, it goes to VSL-server...

If on the same computer you launch VI stand-alone the memory ALSO goes to the VSL-server.....


So you CANNOT gain access to more VI memory since even when using VI as plug-in it is actually stand-alone.

SvK


SvK

I have been able to load 2.7 GB in Logic using VI AU's then open a standalone and load 2.7GB in that then open a second instance of VI Standalone (re-named) and load another 1GB. All the samples play though I can't vouch for long term stability. I notice in Activity monitor that the Logic AU samples alocate RAM to "VSL-Server" and the stand alone samples allocate RAM to "Vienna-Instrumen".

Julian

The IAC bus is an internal OSX solution for routing midi frol 1 AP to another.

Full thread on Logic + RAX as an AU host (with VSL & other Au's) here :
http://community.sonikmatter.com/forums/index.php?showtopic=30308&hl=

There is also the AU Net Send/Recieve plug-ins that are integrated in the OSX system and that allow you to stream audio from 1 ap to another.



Question : What is the exact maximum limit of RAM accessible by the VSL server?

Some of you seem to be talking about 3 Gigs? Is there an official quote on this?

Thanx.

Chari....

Maya told me the max was circa 2.9gig for VSL-server.

SvK

@svonkampen said:

Chari....

Maya told me the max was circa 2.9gig for VSL-server.

SvK

What?
I can't believe this....

Isn't there an alternative VSL could offer, like running an ap called VSL-server B...

Can anyone from VSL comment on this? Thanx..
I honestly cannot imagine that this is not a momentary situation....
Everyone's been openly waiting for ages for Apple-Emagic to raise the number of open exs instruments in a Logic song...

..And now I learn that the VSL team came up with a Virtual instrument that's limited to 2.9 Gigs...

Surely there's a mistake in their communication..

Sorry.. If this is true it's pathetic...

I know there is a RAM purge function but I really don't think this is very practical. Re-loading samples to Ram takes ages...

Charl, it's not VSL it's that we're in a 32-bit memory access world. The max per program running on a Mac is 4GB, from which you subtract Frameworks and Libraries (shared among all open programs). That comes to about 2.9GB.

The other factor seems to be the number of samples you can have open. Herb posted that 45,000 is the maximum.

I haven't tested Windows yet (every time I do a new review I have to buy at least one more hard drive!), but it's extremely unlikely to be any better.

Charl.....

remember....

just run 2.9 gig of AUVIS's in LogiC AND you still have another 2.9 Gig for EXS24 VSL (since vsi-server doesn't touch thr RAM used by Logic)

so you have 6 gig available on one MAC [;)]

not bad!

@Another User said:

I haven't tested Windows yet (every time I do a new review I have to buy at least one more hard drive!)

[:D]

Yeah, here I am complaining about a limit of 3 Gigs... It's surreal..
I now look like I'm one of those eternal moaners... (+ I was into the bitching fest when VSL announced there was no VIP path into the standard VI... Oh no..) [:)]
But the VI's are just too good, I bought them... I have to say Herb's kind proposal of doing the apassionata strings helped a little..

Still I'm sure there's an easy solution for the gig limit... Maybe not totally elegant but I'm sure they can come up with something.
N'est-ce pas Herb & Co?

Id' rather have a second (and third) AU than have to use the standalone...