Vienna Symphonic Library Forum
Forum Statistics

194,027 users have contributed to 42,906 threads and 257,900 posts.

In the past 24 hours, we have 4 new thread(s), 19 new post(s) and 105 new user(s).

  • 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