Vienna Symphonic Library Forum
Forum Statistics

182,187 users have contributed to 42,209 threads and 254,691 posts.

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

  • VEPro 7 is taking forever to load all my instruments

    Hi,

    So I'm working with VEPro 7 and Cubase 10.5. In my 1 instance of VEPro that I use, I have roughly 10 kontakt instruments, 5 play instruments, 1 omnisphere instance, and then some QL spaces reverb (just one that everything is being routed through. Most have their midi channels fully loaded up with master keyswitch patches, so it's kind of a big template, though not huge like others that I've seen. 

    Each time I load the VEPro instance with all these instruments, it takes forever, even though I have everything on really fast SSD's and even 2 M.2 SSD's, so I don't understand why it's taking so long. I've put all of my instruments in the exclusion folder for Window's defender, so that shouldn't be causing the problem. 

    My rig:

    Intel i9-9900x 3.5 --- 192 gb of DDR4 3600 Ram --- Windows 10 64x --- RME fireface 400

    With that much RAM, I have basically everything being loaded into it. Is that a wise choice? I mapped it all out and I think I'm using about 120 GB of RAM from all the samples. I've also mapped all of the cores, except two, to the single Vienna Ensemble Pro instance, leaving one for the OS and one for Cubase.

    Basically what happens is that it'll load the first instrument pretty fast and then wait for a minute or two and say it's not responding, then it'll load another instrument or two. Rinse and repeat. About 20 min later, it'll finish and I switch projects a lot, so you can see how that can be discouraging. The instances are decoupled, so that shouldn't factor into the wait time either. 

    Sorry for the essay, but I wanted to get all the info I had out there. Let me know your thoughts!

    Thanks,

    Danny


  • "Is that a wise choice?"

    Not really, no. Also you can assign all your cores to VEP, seen it said numerous times here by staff, and I always have.


  • The first thing you have to check is are all of your libraries batch-resaved? It makes huuuuuuge difference, it is a must when installing new library. The other question is in which format your libraries store the samples? It there are ncw or wav - it could again make too long load, because some (older) libs can have thousands of such small files (and even hundreds of thousands). Well, the only way to do that is to pack samples into nkx containers. It could be challenging because it can't be done officially and the only way is to install total commander and special nkx-addon. Yeah, it sounds weird when we are talking about such powerful system you own, but nevertheless... I tried to avoid this, but I hate long loads so I managed to pack everything I need to nkx. 

    BUT, I'm 99% sure that your problem comes from not batch-resaved libs, so first try to do this. You can start from only one library (batch-resave can take some time) and then check it individually. I was suffering for years of a similar, about 30-40 minutes for average template. Now it's 10 times faster, not instant, but I think it could also depend on CPU (and yours is pretty good)

    Good luck!