Anyone experiencing higher cpu useage over VEP6?

Also normal functions are painfully slow now. Basic functions such as inserting effects, color change, moving channels etc..are taking way too long.

Anyone else experiencing this?

i7 5820k· 3.30 GHz· RAM 32GB DDR4· 1TB HD x3· 500 GB SSD x3· Video HD-5450 1GB· Win 10 x64· RME FF400

For VEP 6 and VEP 7 you should disable ASIO Gurad in the Cubase plugin manager (see VEP7 User manual page 35). This solves a lot of issues with VEP.

I have to use ASIO Guard. It does the opposite of harm here.
I'm on Mac OS BTW.

Yes. Same happening here. The sampler computer running Ensemble Pro 7 is pretty much the same but Cubase is loading much slower the templates with the connection plugin to the VE Pro 7 samplers. Feels like it is taking longer to establish tracks/connection to the sampler for every instance. 

It's bad enough that we're rolling back to VE Pro 6. Can't work like this. This is with Cubase 10 latest on Windows (as is the VE Pro.) ASIO guard completely disabled for VE Pro. Installed with latest VE Pro 7 just yesterday.

Update to the above.  I have VEP6 (latest version) running fine again.  For anyone that decides to rollback to VEP6 on a mac, watch out for the following thing:

On VEP7 they renamed the name of the VEP server app bundle to remove the words "(64-bit)" from the app bundle name.  Previously under VEP6, this was the name used for the 32bit server.

So after I rolled back to VEP6, I tried to launch it by using the icon in my dockbar, which had been configured for VEP7 to point to the app bundle WITHOUT the words "(64-bit)".  After rolling back, the dock icon was now pointing to the 32bit server and I didn't realize it.  

When I tried to load a viframe into the 32bit server, it was crashing, who knows why.  But after correcting the dock icon to point to the VEP6 bundle with "(64-bit)" in the app bundle name, it now seems to be humming along fine....

VEP 7 has been extremely unpredictable and inconsistent, temperamental, or the system is temperamental with it. Yesterday learning automation from BFD3 would beach ball o' doom each time. Today not at all.
I experienced slowness in other ways and then didn't. All very stable and responsive today.

There are already two updates - less than a week after the initial release. 

Anyway I notice a slight increase in idle cpu compared to last version of VE6 but absolutely no other issues - this is on a project inovlving 77 channels/VIs,  and 900 articulation sets within all custom matrices, MIR pro  on every channel.  Works exactly like VE6 except with all the new features. So this is one system not experiencing any of the issues reported here. 

Though - this is the standalone version - a single VE running 4 MIDI ports on a 12 core Xeon Windows 10 slave wth 64GB ram.  

Well that is very frustrating.  Because VEP7 uses 10-20% more cpu when the window is active for me here.  I have reverted to VEP6 and run exact same project and VEP6 is using less CPU.  Both VEP6 and VEP7 use a significant amount of additional CPU when the VEP window is open vs when its minimized.  Personally I think that is concerni as well.  Its even worse with a retina display.  VEP7 is just a little worse then VEP6, those are MY results.  I spent an entire afternoon running a precise test that would gather the results in a repeatable and exact way to be sure and I shared the test case with VSL.  I can observe the additonial CPU usage as a percentage in the activity monitor and I have observe it in the loadavg value.  they are correlated values.

If their answer is that their results are opposite of mine, I don't knwo what to say other then we have opposite results and that is frsutrating because my results are what they are.

I will not be able to run any more tests because the past few days I wasted of time with VEP7 and I am now reverted to VEP6 and will not try VEP7 again until at least a month goes by and poblems are more resolved.

regards

if you have it on a slave and you are accessing the slave via remote desktop, and the remote desktop window is closed, then that is the same as VEP7 window being minimized.  Run your test with the VEP7 window showing on a screen somewhere and updating its UI elements...