When I load up a Digital Performer project and it starts connecting to my VEP instances, VEP will often crash. Anyone else running into this? Makes me wish I had my samples on SSD drives...

Mac OS 10.10.3.

No problem! And the site redesign certainly is looking great!

Version 5.3.13407 on Mac OS 10.9.5 crashes when I make it check for updates. I assume this has to do with the recent restructuring of the website? (maybe the location of the files change and VE Pro doesn't know it)

I should provide an update:

Ever since I updated from Mountain Lion to Mavericks, Kontakt 5.3.1 now works perfectly. So I'm hesitant to upgrade to 5.4.1 ;) I didn't even know it was out! I guess I can always easily downgrade to 5.3.1 in case there are problems. Thanks for the heads-up.

Ok, problem solved. Kontakt's memory server was enabled, apparently that's a bad thing, though I had it enabled before on Mountain Lion and it wasn't a problem. Things are working much better now.

Aha! My system ran out of RAM. Now, the obvious question is, why on earth did I not have this problem under Mountain Lion, but this is now an issue under a clean install of Mavericks? I've got 32GB RAM total. When idle, with just a couple small apps running, I'm using only 5.5GB. That should be plenty to load up 11GB of Kontakt samples.

I'm hoping someone can help me with this, it's a pretty serious issue. I'm not sure if this is VE Pro at fault or Kontakt (5.3.1). I'm on Mac OS Mavericks, and randomly when loading my template (which consumes about 11GB of RAM), it'll stop suddenly. Sometimes after a couple gigs are loaded, sometimes more.

And if I click the arrow (next to purge) and choose an option like purge samples or reload samples, I get the spinning beachball of death. I have no ideas how to even start troubleshooting this. I guess I could start by reverting to Kontakt 5.3.0. Not sure where the problem lies, though (VE Pro vs Kontakt). Any help would be greatly appreciated!

I'm having stutter issues too in 5.3.1 within VE Pro. Majorly annoying. I've worked around this by using 5.3.0 for now, but the problem is that newer Kontakt libraries are requiring 5.3.1 and it's becoming frustrating.

Native Instruments is aware of the problem. See their email to me below:

Uh, yeah.. it's quite odd to say that Kontakt does not work as well in VE Pro as it does within the sequencer.

I think I'll contact official tech support. :)

Buffer settings make no difference.. again, sometimes VE Pro works fine, sometimes not. Directory Manager doesn't matter, since I'm not using any Vienna instruments. Kontakt only.

It just spiked a while ago at around 60-70%. In Activity Monitor it said 450% CPU usage! The only thing that fixes it is restarting VE Pro and reloading my template. Now it's idling at around 25%. Activity Monitor reports around 170% CPU usage.

Not sure what settings I need to post. I've got 2 threads per instance. My buffer in Digital Performer is set to 256 which works fine for me.. 512 introduces a little too much latency for my tastes. But regardless, the CPU doesn't seem to be connected to buffer size at all. Like I said, it's totally random. Sometimes it's running at 9%, sometimes 90%. When it's that high, yes, I get lots of stuttering and skipping.

Correct, no network.. single machine. And the CPU problem is sporadic like I said. Sometimes it's at 10%. Other times, I'll open the same project and it connects to VE Pro and then the CPU says 45-60%. Doesn't make any sense.

I'm not using the VST3 version. Digital Performer doesn't currently support VST3.

I'm not entirely convinced that's the issue.

I've noticed the CPU usage meter in the bottom right varies greatly, but randomly. Sometimes it hangs around 10-15% which is great. Other times it's above 70%, even just idling. I can't figure out why it's doing this.

I'm on a Mac Pro, 10.8.5, 8-core 2.66GHz, 32GB RAM, running VE Pro and DP8 on the same machine. (though this issue occurs w/ Cubase as well) I'm open to suggestions!

You're quite welcome. Happy to pass along solutions to preventing frustration-related hair loss! ;) I'm gonna become one of those paranoid types who never upgrades their software now.. or maybe from now on I'll keep a journal of when I update things, so it'll help me target the culprit more easily going forward.

Solved it. Kontakt 5.3.1 was the issue. Downgraded to 5.3.0, all is well!

A few of my samples (in Kontakt, within VE Pro) are now stuttering. Never had this problem before this most recent update (5.3.13151). And one of them is not CPU intensive in the slightest, and has never caused issues before now.

Hi Paul,

Using Kontakt 5.3.0.6464. I don't think I'm hitting my RAM limits, no. I've got a RAM meter on my menu bar that says I still have 8GB left. And unfortunately I can't reliably reproduce this issue. It just happens kind of randomly when I remove a patch. If there's anything I can do to help pinpoint the problem, please let me know! I'm also pretty tech savvy so if you need me to run some sort of diagnostic tool or a special version of VE Pro with verbose debugging info, I can do that. Let me know.

Just had another lockup, this time from trying to simply remove a Kontakt patch. This is extremely frustrating.

I've been noticing more lockups in 5.3.13045 on Mac OS 10.8.6, where I have to force quit. This usually happens when loading up a Kontakt instrument. Just thought I'd report this so Vienna is aware, and to see if anyone else is having stability issues. It's a huge bummer to have to reload up 16+ GB of samples in the middle of working.

Yeah, I was talking to a friend about this last night, who recommended using track automation to send out MIDI volume/pan on every track at bar 1. Good idea. :)

I have a particular Cubase project and when I load it up, some of the instruments in Kontakt (within VE Pro) do not adjust their volume properly. Yet when I build a test Cubase project and VE Pro metaframe to test (with just a single Kontakt instrument), loading up the test Cubase project makes the fader within Kontakt/VE Pro adjust accordingly as soon as the Cubase project loads up.

Is there any reason VE Pro would ignore MIDI volume signals coming in? (or perhaps Cubase is not sending it..?)

This bug has returned, looks like. If I have several instances (disconnected), and I delete one, VE Pro crashes.

Crash dump here: http://pastebin.com/LtsNbJZL

Paul,

I figured not. Guess I'll go bug them for a while. ;)

Linux is arguably one of the best server platforms out there. You get the robustness and leanness of any UNIX based system (e.g. Mac, but MUCH lighter on resources), but without the subpar filesystem and registry structure of Windows. I know this is no small undertaking, especially since the e-Licenser control software doesn't exist for Linux, but I'm curious if the Vienna team would consider this. Being able to put together a PC and then install Ubuntu or Debian on it and use the ext4 filesystem would be fantastic! But maybe I'm in dream-land. :)

Thoughts?