Vienna Symphonic Library Forum
Forum Statistics

202,937 users have contributed to 43,313 threads and 259,540 posts.

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

  1. Home
  2. Software
  3. Vienna Ensemble Pro 7
  4. VEP extremely sluggish GUI. RAM issue??

  • VEP extremely sluggish GUI. RAM issue??

    B
    B

    Hi all.

    I’ve noticed my (large!) Vienna Ensemble Pro template is really slowing down, taking ages to switch between tabs and instances. GUI is not especially responsive. Very sluggish to bring up the guis of individual VSTis like Kontakt, SINE, Synchron player etc

    There has only been two recent changes that I can attribute to this: 1) I have recently upgraded from 128 GB to 256 GB of RAM, and 2) I have finally switched to iLok on Vienna Ensemble Pro and all VSL libraries. I think 2) is less likely to be causing the issue because VEP on my slave computer is not sluggish and is also iLok (of course)

    It’s early in my investigations, but one possibility is that now that my template is expanding beyond 128GB RAM, VEP doesn’t like it. Can you think of any reason why VEP would slow down with large templates using in excess of 128GB RAM? Or perhaps it’s not a VEP issue at all but a Windows 10 or BIOS issue? Why would any single program struggle when accessing greater than 128GB RAM? Could the other half of my 256GB be technically unavailable to a single program? Is there a limit?

    I’m using VEP decoupled on a master and a slave (both W10) with many disabled instruments within VEP. As mentioned above, the Slave version of VEP doesn’t seem sluggish and it too is the iLok version.

    Can anyone help??!

    Thanks all, and Happy New Year
  • L
    L

    Hello Brett. On our one MacPro, we have 768GB of ram, but when we load up around 600GB of items into VEP, it will crash. No idea why. Has nothing to do with which types of libs or VIs are loaded. Even though we still have almost 200GB open, VEP7 just doesnt seem to like if we load close to our full ram. Weird.
  • B
    B
    @labman said:

    Hello Brett. On our one MacPro, we have 768GB of ram, but when we load up around 600GB of items into VEP, it will crash. No idea why. Has nothing to do with which types of libs or VIs are loaded. Even though we still have almost 200GB open, VEP7 just doesnt seem to like if we load close to our full ram. Weird.

    Hmm, that’s interesting @labman. I’m about to forensically start removing libraries to try and see if something is triggering the slowdown, but I’m currently only using just over half of my RAM and should have plenty of capacity

    Do you use disabled channels / instruments in your template or just have everything loaded? I’ve recently started using disabled instrument and am wondering perhaps if this too is a factor., contributing to large save files and somehow placing a different burden on my machine.

    driving me crazy! 😝

  • B brett referenced this topic on
  • L
    L

    We do disable items in VEP mac template, yes. Only started that, after finding we couldn't go above a certain ram % though. Not a great way for us to work but it is what it is.

  • M
    M

    Hi @brett

    @brett said:

    Hi all.


    I’ve noticed my (large!) Vienna Ensemble Pro template is really slowing down, taking ages to switch between tabs and instances. GUI is not especially responsive. Very sluggish to bring up the guis of individual VSTis like Kontakt, SINE, Synchron player etc


    There has only been two recent changes that I can attribute to this: 1) I have recently upgraded from 128 GB to 256 GB of RAM, and 2) I have finally switched to iLok on Vienna Ensemble Pro and all VSL libraries. I think 2) is less likely to be causing the issue because VEP on my slave computer is not sluggish and is also iLok (of course)


    It’s early in my investigations, but one possibility is that now that my template is expanding beyond 128GB RAM, VEP doesn’t like it. Can you think of any reason why VEP would slow down with large templates using in excess of 128GB RAM? Or perhaps it’s not a VEP issue at all but a Windows 10 or BIOS issue? Why would any single program struggle when accessing greater than 128GB RAM? Could the other half of my 256GB be technically unavailable to a single program? Is there a limit?


    I’m using VEP decoupled on a master and a slave (both W10) with many disabled instruments within VEP. As mentioned above, the Slave version of VEP doesn’t seem sluggish and it too is the iLok version.


    Can anyone help??!


    Thanks all, and Happy New Year