Thank you for the reply. I really do appreciate your willingness to keep sharing how this all works even though newbies like me probably ask you the same question(s) over and over.

Hi Dietz,

Am I understand this correctly in the way MIR takes over the panning duty? If Alan Meyerson kept the panning default on each of the violin tracks he had and put a MIR insert on each track instead of the group you could achieve the similar result by tweaking each of the individual objects that would be represented on the MIR stage?

And a 2nd question. Is the choice between using MIR insert on each virtual instrument vs an instrument group come down to what sound you're trying to achieve and the sound sources your feeding into MIR?

I vote for the performance legato

If you happen to be a Keyboard Maestro user you can make a quick macro to help with this

I made a group that activates only when Mir Pro is running.
Create the action to trigger on space bar with a condition that if Mir Pro is in front and Logic is running as well then send the spacebar keystroke to Logic. Otherwise just send spacebar. Keyboard Maestro gets the keystroke before Mir does and seems to be working okay for me.

Just to clarify, you can't use Vienna Suite Pro with the Synchron-ized / Synchron libraries correct? Only the Vienna Instrument libraries

Thanks

Thomas

If it's helpful (or for someone to point out that I'm doing something wrong) here is a quick screen recording creating the issue I see. Apoligies in advance for the terrible chord progression

https://www.dropbox.com/s/tps64ryyeicjz80/Cubase-VEP7-CPU.mp4?dl=0

I'm also seeing the CPU issue when the GUI for an active instance is displayed. I had this issue on 6 as well and opened a ticket (Case 297541) about the problem.

My steps to reliabliy recreate the issue are below. It makes sense there would be additional CPU usage for drawing the meter but from my observation using the test outline below jumping from ~20% to ~100% showing a single meter seems like something else could be going on as well.

Launch VE Pro Server 
1. Create two Instances
2. Load Instrument in the first instance (I picked the VSL Concert D)
 
Launch new project in DAW (I'm using Cubase 10.0.20)
1. Create a new VEPro Instrument
2. Create a simple midi part (I wrote in a couple block chords for a 4 bar loop)
3. Start Playback
 
Launch Activity Monitor and find the Vienna Ensemble Pro process
1. Observe high cpu usage
2. Go to VE Pro and change the selected instance to the 2nd instance (the one that has no activity)
3. Go back to Activity monitor and. observe the cpu usage of VE Pro