Vienna Symphonic Library Forum
Forum Statistics

200,402 users have contributed to 43,197 threads and 259,080 posts.

In the past 24 hours, we have 2 new thread(s), 9 new post(s) and 79 new user(s).

  1. Home
  2. Software
  3. Vienna Instruments Pro (legacy)
  4. Does each 32 bit instance of VE Pro have 4 Gig limit?

  • Does each 32 bit instance of VE Pro have 4 Gig limit?

    R
    R

    As I'm working with Logic, using VE Pro on the host and on one slave, I sometimes, with Kontakt, get a message that it cannot load the patch I wanted because it could not find a large enough empty block (or something to that effect).

    Does each instance (in 32 bit mode) of VE Pro have the 3.4 or so Gig limit that Logic itself has?  Or can you keep loading  up an instance of VE Pro until you run out of memory?

    What might be causing Kontakt 4 to give me that message, and be unable to load (like a fairly simple StormDrum loop)?

    I'm in Snow Leopard 10.6.3, with Logic 9.1.1, and the latest version of VE Pro.  I have 17 Gig of RAM on a Mac Pro Quad Core 2.66 Ghz.
  • D
    D

    The 32bit bit server has a 32bit memory limit, in other words a total of about 3-3.2GB usable memory for sample loading. However, AFAIK Kontakt has its own memory server, so do check that you are using this.

    DG
  • R
    R

    You know, it was Kontakt's pre buffer that was causing the prob.  Somewhere in all this I read someone say to increase Kontakt's preload buffer from the default of around 60 up to 200.  Once I put it back to the lower setting, all the problems went away.

    But it's good to know about the 32 bit limit.

    I've heard 2 schools of thought now on Kontakt's memory manager.  Some emphatically say don't use it if you don't have to, others say use it all the time..

    With VE PRO is it best to use the Kontakt Mem Manager all the time?

    Thanks for the input!!
  • civilization 3C
    civilization 3C

    Interesting; in my case I'm using the default 60 number for that buffer, and this occurs occasionally; this is particular in my case, to an instance where Kontakt 3.5 (KMS enabled) is using 1.5 GBs according to activity monitor. I have 24 GB of RAM on my slave and in this case there is no need for virtual memory to be tapped, it's just not that huge a project overall, around a 7GB metaframe.

    If KMS does transcend the ca 3GB limit of a 32-bit instance of VE Pro, I would want to take advantage; at this point I kind of suspect it's more trouble than it's worth, KMS inside VE Pro.
  • civilization 3C
    civilization 3C

    I had a project lately that wouldn't load without KMS enabled, so who knows. That instance had not exceeded 3GB but was about to get there.