Yes, you did, Paul. :-) My bad. I thought I had removed the comment on another thread. 

Read my follow-up. The issue has been resolved.

Quick update:

The culprit seems to be a arbitrary resetting of the buffer settings for each VEP instance in Cubase. The template is rather large with 64 instances of VEP connecting to three workstations. I noticed that a significant number of instances were reset to using the "none" setting for the Latency Buffer in VEP. This resulted in the extremely high CPU load and makes perfect sense. After setting them back to using 2 buffers, the CPU load has moved back into the range it was before.

Additionally, save time in Cubase increased to a tremendous amount. I noticed that "Decouple from Instance" had also been reset.

So, all that to say that the issue has been resolved by checking that all instances are using the previous (2) buffers and that all instances are decoupled.

Note: I assume at this point that this was caused by upgrading to Cubase Pro 9, which must have reset some of the VEP instances, and upgrading to VEP 6, which may have confused tracking down the issue at first.

Having performance issues using Cubase on Mac OS X 10.10.5 or MacOS Sierra and Cubase Pro 8.5 or Cubase Pro 9. Tested with all combinations, which result in the same issue with VEP 6. The CPU load goes through the roof with version 6.x, which did not happen with version 5.x.

I have a project that connects to three slave computers using VEP. Prior to updating to VEP 6 there were no issues. Using VEP 6 is unsuable at the moment due to the CPU load issue.

Still tracking down the source, but at this point it solidly points to VEP 6 as being the culprit.

Anyone experiencing similar issues? Anyone found a remedy?

Note: My issue has been resolved. Look for thread [SOLVED] Significant CPU Load Issue with VEP 6 and Cubase on Mac OS

Having performance issues as well. Using Cubase on Mac OS X 10.10.5 or MacOS Sierra and Cubase Pro 8.5 or Cubase Pro 9 results in the same issue with VEP 6. The CPU load goes through the roof with version 6.x, which did not happen with version 5.x.

I have a project that connects to three slave computers using VEP. No issues ith VEP 5 and unusable with VEP 6 due to the CPU usage issue.

Still tracking down the source, but at this point it solidly points to VEP 6 as being the culprit.

All good. After installing the Konzerthaus room pack, I was able to get the MIRx presets in MIR 24.

Might have been just me not understanding that the MIRx room packs are strictly just for use within VE Instruments. :-)

Again, thanks for the quick reply, Paul!

A couple of things:

I suppose I was confused by the mention of the MIRx settings in the MIR Pro product description. I assumed that they are "included" based on the MIRx room packs I already have installed on the system. However, it seems that separate MIR room packs are required to enable the MIRx functionality in MIR Pro.

I started the download yesterday and have yet to install the Konzerthaus room pack. I'll check back in if that for some reason doesn't address the issue/question.

Thanks, Paul.

When I enable the MIRx Mode in MIR 24, the dialog states "NO MIRx VENUE-PRESET AVAILABE". What is required to enable that? Licenses for the MIRx rooms (the 3 I have) are properly registered. I have the Teldex and the GrosserSaal and Mozartsaal room packs.

I'm evaluating MIR 24 after having purchased three of the MIRx room pack licenses previously for the Vienna Instruments Pro player. I'd like more control over the MIRx reverbs, thus the thought of switching to MIR 24. :-)

It seems that I still have to download room packs for MIR 24. Are the MIRx room packs not being used by MIR 24? If not, is there an upgrade path from MIRx to MIR 24?

Thanks!

How do we set the sample rate for VE PRO Standalone? Default is 44.1kHz but I need to set it to 48kHz.

Thanks!

JB

Paul,

I side with noiseboyuk's assessment. I also have issues with Cubase Pro 8 running on a 12-core Mac Pro (2013) Mac OS X 10.9 with plenty of CPU power and am getting severe CPU spikes, audio dropouts, and distorted audio across the complete audio buss as long as ASIO-Guard is enabled. 

In my template I have 1,000+ MIDI tracks connecting to 50+ VE Pro Rack Instruments that connect to three workstations. I have not tried to run with the ASIO-Guard lowest setting, as the other two settings caused such severe issues that I simply just disabled it.

Just another viewpoint. :-)

Jurgen

Which is a real shame, of course. I understand the technology challenges behind it. In the same way that you can swap out a plug-in in the interface, it would be great if there would be a function that allows us to swap out plug-ins before a project is loaded. Looking at the metaframe files, I'm sure that information of which plug-in is being used is stored in there.

At stake are the many different metaframes and projects one might create on one OS and having to migrate to another. If the original system/OS is not available anymore, you're really sunk, having to do what you pointed out DG.

I need to move metaframes using Kontakt AU from a Mac to a PC and open them there within VE Pro using the Kontakt VST versions. Is there a way to do this without having to indivdiually replace the Kontakt plug-ins in VE Pro?

Thanks,

JB

Agreed. All workstations in the network have static IP addresses, which are defined by the DHCP server and tied to their respective MAC addresses. We should be good on that part.

The workstations themselves are set up to get their IP addresses assigned by the DHCP server based on their MAC addresses registered with the DHCP server. 

My understanding is that this should ensure that no IP address changes occur. Perhaps I am mistaken.

At any rate, checking on the IP addresses of the workstations, they don't seem to be changing. From that I take it that all is set up properly.

Thanks for helping to diagnose the issue. The IP address is always the first thing that is changed when a new workstation is introduced in the studio. Dynamic IP addresses can wreak havoc. It's always best to do this from the router or DHCP server rather than the individual workstation.

In this case, that doesn't seem to be the issue, although it's entirely possible that some system or gadget in the network is trying to grab that IP address. I'll check on that, just to be sure.

I still feel that something else is at the root of this.

I am having very intermittently dropouts from one of my workstations, which is the only PC in my setup of Macs. The dropouts only occur on the PC. I'm also running the latest version of VE Pro.

The dropouts are a fraction of a second and affect the audio from all the VE Pro instances on that PC, while the audio from the Macs continue without interruption. The VE Pro instances all have multiple audio outputs enabled and I am bringing into the DAW on the Mac a number of audio streams from the PC.

Capacity of the CPU, hard drives, and the network connection are all more than sufficient, so no performance related issues that I can detect.

Looking at the network performance meters in the Windows Task Manager, I do see a short drop when the dropouts occur, either because something is interrupting the network connection temporarily, or the VE Pro Server is having some sort of issue.

What would be the best approach to further diagnose the issue?

Thanks, Paul!

Shouldn't the cells that were previously enabled in the project automatically be enabled again on loading of the project?

Additionally, I have the "Enable Cells on MIDI Activity" checked. However, when MIDI notes are coming through, the cells still are not loading, unless I double-click on them individually, or use other steps to load a row or column of cells.

Thoughts?

This may be a configuration setting issue, but I haven't been able to pinpoint it. So, pardon, if this is covered and straight up.

Here's the issue:

When I load a VE Pro Server metaframe, a Vienna Instruments Pro instance will load fine, but none of the cells previously enabled will load in their enabled state. In other words, all cells are disabled and I have to double-click on the individual cells I need/want to enable them again.

This is with VE Pro Server 5.1.12337 on a Windows 7 system, running VI Pro 2.4.12535.

Am I missing something?

Thanks!

JB

Yup, after watching the videos, it became all clear. Great work on the updated version!

Got my head stuck in too many scoring projects that the new version totally escaped me.

Thanks again for your great support!

JB

That's great, Herb! Thanks for the heads-up. I hadn't updated the library itself, so never saw the V2 matrices and patches.

Now I'm dealing with a different issue in that the matrices and patches from V2 don't load the samples, but I'll dig through the forum and post a separate thread if I can't find the solution.

Thanks,

JB

This may have been answered elsewhere, so my apologies if that is the case. Couldn't immediately find it by searching through the forum.

How can we control the speed of the runs and articulations in the libraries? Even better, is there a way to synchronize the speed to the host DAW's BPM setting?

Thanks,

JB

Been looking through the manuals, but can't seem to find a definitive answer.

How can we find out what the tempo of runs and arpeggios is so we can apply the proper percentage ratio to speeding them up or slowing them down? 

I see references in the manual for the Woodwinds library, for example, about seeing tempo information in the matrix cells, but can't seem to locate where that should be.

Thanks,

JB

This may already have been posted, if so, my apologies.

I just downloaded and installed the latest version of VI Pro 2.0.9753 and noticed that the Reverb seems to cut off early. This is with the standard settings. It sounds like the tail of the reverb suddenly cuts out. 

I am running this on a Win XP 64 system with the latest version of VE Pro.

Anyone else noticed this?

And that will explain the obvious.

Thanks for the reminder. I had forgotten about that.

I just added a Mac Mini Serve with Mac OS X Lion on it to my hardware line-up. One of the problems is that the VE PRO sees all the AU plug-ins, but not the VST plug-ins, even though they are present in /Library/Audio/Plug-Ins/VST

Has anyone run into the scenario? How can I best adress it?

Thanks,

JB

This has been something I wish Apple would change in Logic. Many of us found ways to work around it and here is my approach:

I work with the Environment by setting up a Transformer object that translates all CC7 (Volume) messages to CC11 (Expression). I then connect the Instrument object to that Transformer object, while the Transformer object is connected to the virtual instrument track in the Mixer (in the Environment).

This allows me to work with the faders in the mixer (for automation, etc.), while at the same time getting around the issue of altering the volume for the multi-timbral instrument.

One thing you'll have to make sure is that your virtual instrument channels (such as for any Kontakt instrument) is set to alter the volume with the CC11 message it receives. Requires a bit of mapping MIDI CC messages, but works like a charm.

I put up a screenshot of what this should look like in the environment, which you can find here