Originally Posted by: musicman691

Clarification on the license issues:

If we upgrade to VEPro 7 will we still have the three licenses we now have in VEPro 6?

Can VEPro 6 and 7 coexist on the same computer and Vienna key?

I just purchased the upgrade and eLicenser shows VEP7 as a separate license from VEP5 and 6. So my guess is yes, you still keep your 3 VEP6 licenses.

Originally Posted by: LAJ

Originally Posted by: David Molina

Wow, I would really hate to have you all as customers. They haven't disclosed all the details yet and you guys are already whinning about things you don't know yet. Just be patient and wait for them to reveal all the details. Once they reveal everything and you still don't like it, send them an email. Amazing.

Such an idiotic statement!

The firm does not tell us anything further ... so it should be OK to ask some questions!

Of course it's ok to ask questions. Complaining without having heard their answer is not. They said they will be revealing everything in the days to come.

Wow, I would really hate to have you all as customers. They haven't disclosed all the details yet and you guys are already whinning about things you don't know yet. Just be patient and wait for them to reveal all the details. Once they reveal everything and you still don't like it, send them an email. Amazing.

I've been looking through the manual and online but can't find anything on how to automate Enable/Disable Channel in VEPro 6. Can anyone shed some light? I'm using Cubase 8.5. Thanks!

Hi, I’m in a bit of a workflow rut with Cubase/Vienna Ensemble Pro. I’m hoping someone can suggest something. 

A few months ago I purchased Vienna Ensemble and I’m working to incorporate it into my workflow. 

Here are a few notes before I start:

- I’m using separate VEP instances (instance per instrument) to avoid the routing hell that results from having to use midi tracks and have the audio route back into a different track. CPU is about 15% higher than using one instance per group of instruments (Strings, Brass, Winds, etc), but so far I can work with the higher CPU usage.

- I only have one PC. (i7 Quad-core 3.6GHz, 32GB RAM, SSD's)

- The main reason I'm using VEP is to be able to keep instruments loaded while switching projects. That way I don't have to reload instruments which takes up so much time and breaks workflow and momentum.

This is my current workflow:

- Created a metaframe with the instances I need for a main template. (Vln 1 Long, Vln 2 Short, Vla Long, Vla Short, etc)
- Created a template Cubase project with each instrument track going out to corresponding VEP instance. 

1. Load VEP metaframe.
2. Load Cubase template project.
3. Tweak instruments. Record.
4. Save Cubase project. 

This is where my issue lies. Let’s say the next day I come back to work on the same project (or switch to another project), I load my main VEP metaframe, load the Cubase project but now the tweaks I made on the instruments for this project are gone. Apparently, VEP or Cubase can't recall the VEP plugin settings for a specific project. 

A solution to this would be to save a metaframe for each project. But seems like this would defeat the whole purpose of using VEP since I have to reload all instruments every time I work on a new project. And with a large template it would take a very long time to load, which is one of the main reasons I read people use VEP, and why I purchased VEP; to avoid having to reload instruments every time I switch projects. 

Is there a way to save the state of my instruments for this specific project so that I can move on to other projects and come back to this one and recall the instrument state (settings) without having to reload a new metaframe each time? 

Can anyone suggest a fast and efficient workflow on a single computer and separate instances per instrument (to avoid routing hell)?

Thanks!