Oh my!  I'd started a new thread figuring all of this would be figured out by now and that the answer would be easy.  The e-licenser version is working fine with Pro Tools Ultimate HD, Mac Studio Ultra / Monterey 5.1 - I'm just worried it will up and die on me at some point.  
Thanks

Sorry but I don't have time/energy to scour the conversations for the answer.  I'm still using the ELicensor version of VEP as, last I checked, the iLok version wasn't working at all with Apple - and esp Apple Silicon.   I'm not expecting Apple Silicon compatibility yet.  I just need to know what version of VEP folks are using.  I'm using Monterey 5.1  I no longer need a second machine. Pro Tools Ultimate HD.  Everything else works like a charm here!!!  Thanks.  

I have a Mac Studio Ultra / 128 Ram / 2 TB internal / Sonnet Echo Dual NVMe Docks (2) - one JBOD 2TB for Pro Tools sessions and one Raid 0 (4TB) for virtual instruments.  I JUST got VEP w the new Kontakt 6 working.  I'm using the eLicenser 1120 VEP 7 for now - just to simplify the transition. 

Everything's running under Rosetta.

Is it faster?  I can't say.  Does it work like a dream - absolutely!  Does it use much CPU power? hardly any.  
On my old dual Mac Pro cheese graters (5.1's maxed) they couldn't even play everything at once without freezing tracks and plugins all the time.  
Not to mention that they heated my studio in winter.  Now I have to use heat!!!

I live in Canada.

Do the NVMe's get hot?  Not at all.  The MC Ultra is cool to the touch all day long and dead quiet to these old ears.  

I use VEP within the Mac Studio Ultra.  I don't think you need a slave unless it makes organization easier. I have one session with maybe twenty five or so Spitfire Audio plugins running hard.  On Pro Tools there's a System Usage Meter and it barely moves unless a plugin makes it crash.  

I couldn't even use Spitfire's Symphonic Motions on my old Mac Pro's.  It would just crash every time. 
Since I straightened out Kontakt 6 no crashes.

 
I'd worry that a Mac mini wouldn't have enough RAM.  
I use VEP mostly to be a buffer between nasty Kontakt and Pro Tools.  They aren't lovers - to say the least. 

You've made a good purchase.  I think you'll be very pleased with it!

Just installed VEP7 and it's working just fine with a server!!!  All within the Mac Studio Ultra - and the system is barely lifting a finger!  I downloaded it directly from Vienna and installed from the download thinking the Vienna Assistant might be the culprit.  It recalled sessions from Pro Tools data like no time had passed - and this session is a few months old. Now the server is on the desktop and I don't know what that means.  Is it running via Rosetta or not?  So far Rosetta has been invisible. 
I'm a very happy camper so far.  Most of the weirdness I've encountered hasn't been from any glitch in the works as much as me remembering to set preferences and filter MIDI coming into Pro Tools.  Any program change stuff - which seems to leap out of the Doepfer Mk4 when I change presets - throws Pro Tools into a serious funk.  Quit - Restart etc.  
Now that I've cleared up most of those it's running like a rabbit!

So far so good.  Straight, no instrument Pro Tools seems to work quite well.  I've been installing giant spitfire, Ivory, Omnisphere etc (instruments to a 4TB NVMe Raid0 drive) and a ton of plugins today.  Haven't tested most that I've downloaded today - and it's the plugins that drive P Tools crazy. I have only tested a few of the main audio plugins I use.  Rosetta seems to be working.  HDX - the PCIe card and I/Os seem to be working very well. 
As far as VE Pro not installing an AAX server - this is new territory for me.  I've worked with a slave machine for so long and I'm so gun shy about learning anything I don't need to learn (brain overload) that it's going to be all new.  IN the past I hosted Omnisphere, Trillian, Ivory and a few Kontakt instruments in VEPro.  
I should know more over the next few days.  I'll try to do an update on progress soon. 

Thanks for the encouraging words and really cool info.  Now I understand that Pro Tools, and most DAWS, use only a few cores at a time.  Based on that, I'm not sure about how Pro Tools parses out VI's across cores, so my question is about how VEP uses cores - and whether it's smart to continue using VEP in one fast machine - no slave.  My understanding is that VEP can make good use of the 20 available cores.  Now... maybe I've answered my own question and I WILL go ahead and install it on the Mac Studio Ultra.  

I'm not terribly worried about RAM at this point because I've never had more than 48 GIGs in the past!!!  And I don't use enormous libraries usually.   BBCSO is the biggest I have right now and I only use small sections of that. 
Thanks again

I'm reinstalling my world after ten years on two 5.1 Mac Pros.  One machine was a VEP slave -  with Pro Tools HDX on the other.  Over time and with the expanding libraries (Spitfire etc) things got very unpredictable, so I bought a Mac Studio Ultra / 128 RAM / 2TB internal / 6TB NVMe (2XSonnet Echo Dual.Thunderbolt)  One NVMe = a 4 TB Raid for VI libraries.  The other for Pro Tools sessions.  I'm wondering if I should still use VEP on the Mac Studio Ultra?  It seems to make better use of hyper threading / cores etc.  Any Pro Tools VEP users out there who can comment?
It would all be running via Rosetta, so I'm HOPING VEP will work.  
Thanks

VEP 7 - Didn't get more than one activation code so can only activate on one machine. Help!

OK! Just tried it and all VEP sees is SSD4. Then tried opening stand alone VEP and same thing. Will poke around more later but thanks for the hope!

Interesting. All I've tried to far is to instantiate it within VEP6 on the slave machine. I kenw it was AU and couldn't see why it wouldn't work. Havent really needed it yet cuz I'm doing a project with real drums that sound spectacular. But I'll poke around as time allows. 

Thanks so much! This is good news

Got an answer from Slate - No! New SSD5 does NOT work with VEP! Too bad. 

Has anyone tried using the new SSD5 with VEP? Haven't had any luck at all yet. 

Yeah I have full Kontakt, latest version. Am going to experiment with putting it on my server machine today. Will keep you posted

My first Spitfire library - bought yesterday 6 OCT/18! MIDI only gets through to one of the sections - second violins, MIDI channel 2. I can see the MIDI activity light (MIDI channel 2) following input but see nothing else. No signs of life in Spitfire. Have other libraries working fine in this config. 2012 Mac Pro 48GIGS Ram, Sierra, Pro Tools HD 12.5., installed on 1TB SSD (not OS) drive. I am hosting this on the main machine, not the slave. Opened other libraries to check and they worked fine. 

OK! This is strange. Works FINE in Stand Alone VEP6!!!

Doesn't work at all in Server. Just keeps "Loading"

Anyone using VEP6 with Wave Alchemy's wonderful Revolution (drum machine)? I can't get it past "Loading". Works fine in Kontakt but inside VEP6 it's a no go. 

I've been using it in Pro Tools 12.5 HDX and it's a Pro Tools eater. Frequent reboots, frequently deleting preferences etc. I really love the sounds though so put up with the lost time - which is of course very precious. 

Any tips would be great! I'm talking with Marnix about it and no solution yet. 

Are you using Kontakt? The relationship between Kontakt and VEP - and the naming and routing of outputs is convoluted, to say the least.  That is if you're used to DAWs or analogue etc. 

Having a terrible time getting Session Horns Pro (SHP) to work.  It worked in earlier versions of VEP.  I love VEP, btw.  

What happens is, it loads, everything looks great but nothing works.  In standalone it works fine.  I can select instruments, presets etc, but nothing in the server app.  I've redownloaded SHP, I've Batch Saved it in Kontakt, which should help.  I've even rebuilt the database of Kontakt Ultimate (took a while) and still no go.  But it works fine in stand alone. 

Any clues?  

Seems to work Paul! Not sure how I would take ONE INSTANCE from a past metaframe with multiple instances, but I'm working on it.  Very rarely saved 'projects' (separate instances) in VEP5.  

If you're a user reading this, if you try this, it looks like it's going to replace your existing instances - goes through the 'save this project' like it's going to close the existing instances routine, but it doesn't.  

Still experimenting.

VEP6 seems to be working very well with my setup - Pro Tools HD 12.5.2.  Great changes, but crashes when PT is running sometimes.  Haven't installed 22OCT16 build yet.  My Pro Tools machine is a 2012 Mac Pro, Mtn Lion, 48 gigs RAM, SSD drives and the slave machine is early 08 Mac Pro, Yosemite, 28 gigs RAM, SSD main drive, 40 TB Drobo storage hanging off the buss!

Next up is experimenting with Yosemite on the 2012 machine.  Will try on separate partition first, of course. 

I was wondering the same thing!  No import option anywhere that I can see.  I was trying to build the mother template I could subtract from.  

May have figured out the metaframe weirdness. Give me time, I'll probably figure out the connection problem

Figured out that I could do it the old way by starting VEP with no instances and could recall the metaframes by calling up different projects from Pro Tools HD.  But new VEP6 doesn't see the slave machine.  Tried IP address and still no connect.  Guess it's time to look it up in the manual!

Hi Paul.

Problem for me is I saved almost everything as metaframes.  Saving projects will mean I have to rebuild metaframes from projects?  Do I need to go back to VEP5 and save all the projects from the metaframes?  I produce pop music pretty much (Universal Music USA and Canada) so many metaframes were similar with tweaks per song!  I'll wander around the software for a bit to see, but don't have tons of time to explore. 

Thanks