Paul et al..... If I turn off VSTs in the plug-in preferences, does that henceforth force VEP to use audio units instead, even if saved in previous metaframes as VST's? Meaning... will old projects and metaframes switch over to AU's? Thanks

Love you guys! I knew you would get on it. Thank you Paul and Martin.

Originally Posted by: MS

I have managed to reproduce the issue and have isolated it to a part internal to DP. I've notified the DP developers about this, and hopefully it will be corrected soon!

Any luck hunting this down Martin? It is sorta killing us. Thank you  !

I appreciate your report Dave! Thank you. Shall wait to update then.

Originally Posted by: Dave Pelman

Appreaciate the confirmation, Labman.  I'm guesiing the recent update doesn't address this.

D

We are mid contract Dave, so cant yet update the plug. Will do when done!

Hey there Martin. THank you for chiming in. We here, use 8 ports per plug, (and require a minimum on mnay of those of 6) Have not tested with just one.

Motu has also confirmed with us here, that with MAS VEP in our big orch template, when attempting to comp audio files, using 'show takes' on even two tracks with only 2-3 takes each can take 3 minutes to open. Removing all our 12 VEP instnaces from session, they open immediately. Sorta weird. But this does correspond to your beachball issue Dave, which we too, have confirmed.

I am sure Paul and the vundervar VEP peeps can address this. 

Originally Posted by: Dewdman42

No you need to minimize the entire vep window unless you actually need to look at it

Arghhh well that is REALLY bad news for 3 of our machines then, as we need to be able to look out of th econrer of our eyes to see the meters. Very sad :(

Originally Posted by: Dewdman42

Are your old mini's stuck on High Sierra and unable to go to Mojave?

for one thing, if you keep the GUI closed on the slaves, the VEP GUI will not hit the CPU.  Only open them when you have to, keep them minimized when not actively using them.

Correct. THe minis dont have a video dicreet video card. Its a chip and uses mac ram instead. 

By keeping the GUI closed, you mean the entire metaframe, or a project, on an instance of Kontakt or whatever? In our normal work scenario, unless changes something in VEP, the metaframe in VEP 6 just sits there as the front application. So we see the fader meter movements about thats about it. Is that OK?

Thank you again Dewd. Very appricated.

So what happens on a bunch of our slaves which are the old quad core i7 mac minis. We have several, all fully loaded and running thunderbolt arrays. All hosts are mac pros. But am very concerned about the hit on the older mac mini machines.

Any thoughts Paul? Or Dewd? or others?

Thanks

Thank you Dewd. That is sad for me. I ceratinly dont wanna upgrade a bunch of computers to Mojave just for VEP7.

Paul, will this be an issue for those of us using the MAS verions too?  Meaning running less effeciient on High Sierra than with VEP6?

Thanks.

Is there a hit in performance for the MAS DP verison, if not running in Mojave? (asking as I am seeing posted for other DAWs on forums). We have yet to install our purchased VEP7 on our manchines and all are on high sierra or sierra

Thanks!

Thank you Pual. I apprecite that!

Paul, is VEP7 compatible with Kontakt 5.8??? (See Gregs post directly above this one)

Thnaks

No one with MAS VEP7?

Would love to hear soem specifc MAS input , as we live and die by the VEP6 mas version on our rigs.

THanks folks !

Subject details the issue :)

Forced to switch to VST, (which works) but that means crazy amount of porting Engine multis over. :(

Can someone help?

Thank you!

Originally Posted by: marnix

Hi labman,

OK, we will have to further investigate then - have you already contacted MOTU in this matter, as it seems that DP 10 now behaves differently than DP 9.52 did?

I have not yet. But shall today!

Originally Posted by: marnix

Hi labman,

I have not installed DP 10 yet (still in DP 9.52...), but Auto-Raise works fine here (when activated of course!) with the VE Pro 6.0.17226 MAS plug-in, so I am afraid this is not reproducible...

Best, Marnix

Hey there Marnix. I apprecaite your response. :) It does seem ok in 9.52, but not in DP 10 for some weird reason. We have tried toggling it on and off, to no avail.

Thank you Paul. Lemme know what you find out. (if reproducible)

Hey there Paul et al. Finally installed the latest verison of VEP6 a few weeks ago. ;) It seems to have broken the "auto raise" funtion for us inside DP10.0. (v17226 of 11-27-18). Any ideas???

Thanks!

Personally, we arent interested in the add-ons in the least. And we do need far more than one license here. ;) 

So we too, are 'concerned' but awaiting more details.

Anyone tested DP10 with current VEP6? if so, is all well?

thanks

We have this too, about other day. Only with VEP loaded K5 files. Works fine inside host daw.

This keeps happening lately here too Paul. Really stops the workflow.

DP 9.12 OSX 10.11.6, 48GB ram