Ah yes but if you want a String Quartet you can't do this on the standalone without opening renamed instances which isn't supported. However if the standalone was multitimbral rather than omni it could do this.

Julian

In another recent post, Paul said that even when used as a plug-in, the AU version uses its own memory space, apart from the host sequencer, and that all subsequent instantiations will also use that same memory space (as used by the first instantiation). In other words, it is not behaving as most other AU plugs in this regard. I think maybe the instantion of it is just a link to an AU -- sort of running like a standalone plug.

Paul -- can you confirm/refute this again? Thanks.

This is interesting.

Julian, can you confirm in Activity Monitor that you're really loading 5.4GB?

BTW, Very good article I just came across on RAM usage in G5's in Virtual Instruments Magazine. In fact several excellent articles on different things in there. Uncanny the way something I'm currently needing information on is in the latest issue.

Yes activity monitor confirms load of 5.4 GB. With Logic running as well it leaves 67MB free of a total of 6.5GB.

Julian

dpcon, today you are one of the least outrageous people I've ever met.

Thanks Julian, that's good news. So the plot thickens (and if the double-load works well in the real world, that means you want 8GB or more in your G5).

Hi are any of the chaps from VSL reading? Can they comment on this memory load? Also is it likely to be a logic only thing or will the approach work equally well in Cubase SX3 (MAC)?

Also is there any way of having two different versions of the plugin as a VST? For example I believe on a PC that if you rename a VST dll you can cohost them and in theory each would have access to 2GB memory (as per the WindowsXP app limit).

If it is possible to fill a Quad G4's 16GB and really only need 1 machine for a pretty heavy duty composiiton then I may well jump onto the MAC bandwagon now.....

Best

Tim

Yes, of course we are reading. [:)]

We are researching and testing and making sure that everything really works fine, before we can make our comments.

I´m sure you understand.

Thanks for your patience and enthusiasm.

Best, Paul

@Paul said:

Yes, of course we are reading. [[:)]]

We are researching and testing and making sure that everything really works fine, before we can make our comments.

I´m sure you understand.

Thanks for your patience and enthusiasm.

Best, Paul

sure we understand, Paul!!!

once the possibilities are clear, would you please consider making a step-by-step guide available for users on the VSL site?

thanks! [[:)]]

Nigel

Hi Paul - thanks I know you guys are always there... in the dark, listening, watching....

[:)]

@timkiel said:

will the approach work equally well in Cubase SX3 (MAC)?

Don't forget you'll need a wrapper to operate the VIs with Cubase on a Mac - AU only!

[:(] [*-)] [:@]

Argh! I'd not realised. Have we had any official comment on a MAC VST version as in a definte yay or nay?

I believe it's looking like a "nay" (check the recent "VI on Protools" thread) but I may just stamp my feet and holler a while longer. Want to join me?

[:D]

From the preliminary work I've done with the VI's it appears that even when launched as an AU plug-in within Logic the RAM allocation exists outside Logic as far as the single app limit is concerned. Also as I mentioned earlier if, when you reach the single app RAM limit within Logic, you launch the standalone VI a further RAM allocation can be addressed - subject to your total system RAM.

Now if you are putting a large score together within your DAW the last thing you want to do is suddenly start involving external applications (VI standalone) to complete the orchestration as suddenly these are outside of your arrange automation and song saving compass.

Now I wonder, in the same way that it is currently possible to launch more than on instance of VI standalones by copying and renaming the application, could there be a piece of software code that allowed the VI AU's to appear as more than 1 plug-in source. You would select "AU plug-in Vienna Instruments 1" and when you got near to the RAM limits you could start selecting "AU plug-in Vienna Instruments 2" and get an extra shot at more RAM.

As I don't have a clue about primary level software coding this could just be "pie in the sky" but it could also be a lateral solution until we all have access to 64 bit platforms and 64 bit software.

Julian

I think 5.4 GB of VSL might actually be enough. That's five Gigas.

Possibly - but even better if all available within Logic! [:)] [:D]

Julian