Vienna Symphonic Library Forum
Forum Statistics

199,046 users have contributed to 43,151 threads and 258,882 posts.

In the past 24 hours, we have 3 new thread(s), 10 new post(s) and 58 new user(s).

  1. Home
  2. Sample Libraries
  3. Vienna Instruments Libraries
  4. 4 GB Crashes with VI in Logic

  • 4 GB Crashes with VI in Logic

    P
    P

    I had thought this was solved. Now I realize that I was flying under the 4 GB ceiling all this time.

    This is a Virtual Memory ceiling for me. No more than 2 or so GB are filled in real memory (and my Mac 8-core, running 10.5.8 holds 18 GB total). But when I load any new VI and VM stands perched at 3.91 GB, over it goes, and Logic 8 crashes. (I have read that Logic 9 at least gives you a warning.)

    Could some users give me an update on the methods used to work-around this? I had thought Plogue would do it, but Plogue within Logic just opens the same (non-stand-alone) VI, and the crash happens the same way. 

    Is it still Soundflower and Jack? Has anything changed in the last two years or so? 
  • PaulP
    VSL Team
    PaulP

    Hello plowman, 

    this is still the "old" 32 bit memory limit on OSX, we´re working with high pressure on the 64 bit VI/VE, that will solve this problem.

    For now, you can use more than 5 GB on OSX, with a combination of Vienna Ensemble (2.5 GB) and Vienna Instruments (another 2.8 GB).

    Another solution: Instantiate more than 1 Vienna Ensemble as stand-alones on your Mac, each one can access up to 2.5 GB of RAM - then route back the audio signal into your Logic, either with an audio routing software or physically. 

    Best,

    Paul

    Paul Kopf Head of Product Marketing, Social Media and Support
  • P
    P

    Thanks Paul. If you or others might help, I must sadly re-familiarize myself about the situation. 

    1. "we´re working with high pressure on the 64 bit VI/VE, that will solve this problem."

    To clarify, will your new 64 bit VI / VE work within Logic as a plug-in (even though Logic is 32 bit) and still solve the 4GB crashing problem? This is confusing because I can crash Logic with an Ivory instantiation, due to the same 4 GB threshold. In other words, I didn't think the third party plug-in was at fault. 

    2. "a combination of Vienna Ensemble (2.5 GB) and Vienna Instruments (another 2.8 GB)..."

    Are these numbers for real memory or virtual memory? My crashes occur long before real memory reaches 2.5 and 2.8 respectively. 

    3. "then route back the audio signal into your Logic, either with an audio routing software or physically."

    Am I correct that Plogue Bidule cannot be used to this end? From my tests, if you open Plogue, then VI / VE, they do not run in stand-alone mode, and the memory they require is drawn from the same 4 GB limit that Logic has already used for its own VI / VE plug-in channel strips. 

    4. Okay, so I launch VI / VE in stand-alone mode on the same computer running Logic, and I physically re-route a MIDI out and back in. But I have no soundcard. Do you recommend Jack or Soundflower to get the audio back into Logic? Or perhaps you have no preference. 

    Thanks as always. 
  • H
    H

    If I may request a feature .. please try to make it so that the G5, and logic 8 can still use the 64 bit version when its out. Pretty pleaseeeeeee!!!
  • P
    P

    Paul, no need to answer 3 and 4. Plogue is a moot point, and I have Jack working. 

    I remain curious on 1) will a 64-bit VI / VE in a 32-bit Logic still access all of the Mac's memory? And 2) is 2.8 and 2.5 for VI / VE respectively a real memory, virtual memory, or real-plus-virtual memory total? 
  • PaulP
    VSL Team
    PaulP

    Hello plowman,

    sorry for the delay, here are your answers:

    1) yes, because VE/VI are not depending on the host, being separate applications.

    2) real memory. But memory management on OS X is a bit tricky, it´s sometimes hard to follow. 

    Best,

    Paul

    Paul Kopf Head of Product Marketing, Social Media and Support
  • P
    P

    "...VE/VI are not depending on the host, being separate applications."

    I understand. But I am talking about a 64-bit VI / VE running WITHIN Logic as an AU plug-in. Wouldn't it still use host memory and remain limited to Logic's 4GB, even when VI / VE itself goes 64-bit? Thanks for any clarification. 
  • C
    C

    Hi Plowman

    32bit VE already has it's own memory allocation (2.xGB or whatever) when used as an AU plugin in Logic. When it becomes 64bit you'll only be restricted by the total RAM in your computer.

    Colin
  • P
    P

    Thanks Colin. I'm working with some false assumptions here. 

    So let's see if I understand this gerbil-simple equation. Currently our 32-bit AU plug-ins launched within Logic can hold 2.8 and 2.5, VI / VE, and that's the limit. 

    It's all VI / VE RAM, not sharing any memory with Logic. 

    As long as it's 32-bit, we're limited to 2.8 / 2.5 as AU plug-ins. 

    As AU plug-ins, the 64-bit will allow us to load as much total memory as the Mac has.

    And until then, if we want to maximize our RAM, we have to do the stand-alone / MIDI and audio internal / external routing. 

    The 4 GB crash has nothing to do with Logic maxing out its memory. 
  • C
    C

     Hi Plowman

    As things stand individual VIs use up RAM from Logic's allocation, only VIs within VE address  separate memory. Roll on 64bit!

    HTH

    Colin