Today for some reason I am unable to load my VE Pro server project that I have been using for months. No updaets have been applied in the past few days so I'm not sure what's going on. I can tell by looking at the stack trace it has something to do with Kontakt. I thought maybe I should try loading each instance, however, I only saved the server project. Would anyone know if there is a way to extract the server instances from the server project?

I recently posted something very similar, however, my issue is with Pro Tools and VE Pro. Were you ever able to resolve your issue?

Here is a link to my post: https://www.vsl.co.at/community/posts/t47983-Pro-Tools-12--VE-Pro-6-and-High-CPU

Some additional information I discovered today...

As I stated, once I have VE Pro and Pro Tools up and running my CPU usage can be very high. What I discovered today is if I go into VE Pro and disable a few channels, the CPU usage is drastically reduced. An example today is the CPU usage was around 1700% and after randomly disabling 4 channels the CPU usage went down to around 400%. If I then turn around and re-enable the channels the CPU usage remains low. I tried this out 3 times and every single time I saw the same behavior.

I have no explanation for this but I wanted to add this information in case it helps someone to help me.

I am a fairly new VE Pro user. I was first having an issue with VE Pro crashing but I have resolved that by reducing the number of instanes of Kontakt that I have loaded. I now have a VE Pro template that seems to be stable. I have a corresponding template in Pro Tools 12 that is built to work with my VE Pro template. I have noticed that when my Pro Tools template loads up, the CPU jumps up anywhere between 1500% and 1750%. If it's too high the audio is garbled and it basically doesn't work. Here is some information on my configuration:

My Computer:

• Mid-2012 Mac Pro running macOS Sierra 10.12.6
• 128 GB RAM
• Two 3.33 GHz 6-core processors (24 virtual cores)
• Three 2TB SSD SATA drives. One of the drives contains all of the libraries loaded into VE Pro.
• Pro Tools and VE Pro are currently running on the same computer.

My VE Pro template:

• Seven instances.
• Per instance: 3 threads, 16 MIDI ports, 32 audio outputs, 2 audio inputs.
• Each channel has one instance of Kontakt.
• Most instances of Kontakt have one or more libraries of the same kind of instrument. Ex: Violins 1, Horns, Oboes, etc. There are some instances where this is not the case.
• All instruments are purged so that by default no samples are loaded.
• Multiprocessor support in Kontakt is turned off.
• Each instance of Kontakt can route to up to 16 stereo outputs. For instances where all of the libraries are the same type of instrument, they all route to the same stereo output (st. 1). For the ones where they aren't the same instrument, each library routes to it's own stereo output.

My Pro Tools template:

• One MIDI track for every instrument loaded into VE Pro.
• One aux track for each output that is used from each VE Pro channel.
• Seven aux tracks have the VE Pro plugin inserted.
• Each VE Pro plugin is configured to be connected, preserved and decoupled with 2 buffers.
• The template is configured with a 24-bit bit rate and 96KHz sample rate.
• Pro Tools is configured with a buffer size of 1024.

I have fully verified this high CPU usage is definitely when my Pro Tools template loads up. I execute the following steps:

1. Start VE Pro
2. Load my VE Pro template
3. Load at the CPU usage (it is consistently a low number)
4. Start Pro Tools
5. Load my Pro tools template
6. Look at the CPU usage (at this point it will be significantly higher)

I can get around this by disconnecting the VE Pro plugins that I am not using but I was wondering if anyone might have some suggestions or thoughts as to why the CPU usage goes so high?

Here is a summary of the latest and greatest info...

I reverted Kontakt to the previous version and I reverted VE Pro to the previous version (uninstall and then install), however, I was still constantly crashing. I decided to update both VE Pro and Kontakt back to their latest and greatest versions.

VSL Support did get back to me and told me they saw NICloudCommunication in the logs and this indicated it was Kontakt that was crashing. I sent this to NI and am waiting on a response from them. However, the response from VSL Support didn't sit well with me so I continued to explore.

Using a Time Machine backup I was able to go back to a version of my Pro Tools session from Sunday.. I had to redo several things but this seemed to get me going for awhile. This says to me that maybe some bad/corrupt data ended up being stored in my session.

I continued to work on building my template throughout the day and then eventually VE Pro started crashing regularly again. It seemed to crash anytime I attempted to connect to one specific instance. I tried this 3 times and each time it crashed every time I told it to connect to this instance. This points to my earlier hypothesis that there is some bad/corrupt data getting stored in my Pro Tools session. So, I decided to delete the instance and start setting it up again from scratch. This seemed to be going well, however, after adding 9 or 10 plugins to the instance it crashed once again.

I have sent 4 crash reports to VSL Support, all of which look a little different. Only the first one had something about NICloudCommunication.

So, at this point in time although I am still experiencing a ton of crashing and I'm not sure how to proceed at this point in time.

I just sent my most recent crash report as a reply to a support email I recieved.

Here are the answers to your questions:

1) I have not tried with a different template. This is a large template that I am still in the process of creating. It has taken me a lot of time to setup and I am really hoping I don't have to start from scratch.

2) I just downloaded the previous version of VE Pro. I will send an update once I know more.

3) The only other change I can think of is I have also updated Kontakt 5 and MASCHINE 2 to the latest versions. I also just switched to using a wired mouse instead of a bluetooth mouse. I just reverted back Kontakt 5 to version 5.7.0 but I am still experiencing crashing.

A few days ago I downloaded and installed the latest version of VE Pro (6.0.16502). I am trying to use it extensively today and it is CONSTANTLY crashing making it completely unusable. I can't even say it happens whenever I repeat certain steps because no matter what I do it crashes. At this point within the last 4 hours it has crashed 15 times.

My typical steps are:

1. Start up VE Pro
2. Load a saved server
3. Start up my DAW (Pro Tools 12.8.2)
4. Load up my template (which by default starts off disconnected from VE Pro)
5. Connect to various instances as I need them.

I can usually connect to one or two instances but then it will crash sometimes when connecting to a third or fourth instance, sometimes when I'm in the middle of recording on a MIDI track, sometimes I go to click on an inserted plugin in VE Pro and then it crashes. I have even tried forgoing step #2 and then for step #5 I connect to unpreserved instances. Eventually it still crashes.

In VE Pro I currrently have 10 instances and each instance has multiple Kontakt libraries loaded up as inserted plugins. Admittedly I updated Kontakt over the weekend to version 5.7.1.

I am currently running my DAW and VE Pro on the same machine. Here are the specs:

Mid-2012 Mac Pro
128 GB RAM
Three 2TB SSD
Two 3.33GHz 6-core processors

The Kontakt libraries I have loaded into VE Pro are:
Cinematic Studio Series Strings and Solo String
Spitfire Symphonic Strings, Woodwinds, Brass, Hans Zimmer Percussion, and Albion 1-3
Cinesamples CINESTRINGS Core, CINESTRINGS Solo, CINEWINDS, CINEPERC

Help PLEASE!