I'm connecting VE Pro to Nuendo 11.0.41. So, both are under the Rosetta translation. 
Performance is fantastic. VEP seems to load a project a wee bit slower, or than I'm expecting, Nuendo is loading a project really taking its time, and the slowness is loadiong audio channels with plugins, most of which are Vienna Suite.

For me, if I go to Cubase 12, I may "need" VEP to be native. However I don't feel the need for that at this juncture. So, not to be contrary, but the VEP plugin here is the same priority as the other plugins once I, if ever, get there.

sorry, except for VI and Synchron plugins, I'm going to run those in VEP, period. But VS being native is almost as important (mostly because I'm having to run BFD3 in Cubendo). But again, the performance is through the roof good here, with various niggles per the UX.

Totally agree I have a M1 Mac Mini and VEP7 is the last on my list to refresh the environment of a silicon native. It's a shame that all the main DAWS are inside M1 now and VEP7 which is the bridge for all of them is not!

I demand as Vienna User a clear response under this matter.

@snattack said:

As people have already pointed out in other threads and forums:

We need the VEP VST3 plugin first and foremost converted to Apple Silicon, the server can wait since that could be off-loaded onto other computers, and/or can be run in Rosetta as it is not as dependent on CPU as the DAW that uses heavy audio processing with effects and signal chains.

If a plugin is not native Silicon, it will not show up if the entire DAW doesn't run in Rosetta. Which is much slower than running native. So basically, that makes VEP useless for any Apple Silicon user at this point since it will vastly reduce the performance of all other plugins.

I understand that iLok had to be a priority, and that software developers (which I partly work as myself) can't just wave a magic wand, but it would be nice to have some kind of roadmap made public now that it's been more than two years since the release of M1, so we can start planning the transition. My Mac Pro 2013 is running on fumes, and it seems like a total waste to have to buy an Intel machine just because VSL can't give any information about this.

VEP does seem to be brining up the rear among developers in the transition to M1 at this point. Everything in my system apart from VEP is running M1 native now. It's been a while since VSL has chimed in on this thread. An update would be appreciated - even a reaffirmation of VEP's priority would be good to hear. 

Re "We need the VEP VST3 plugin first and foremost converted to Apple Silicon"

I'm a MAS user so it would be my priority, but I agree. If it's possible to make the VEP plugins M1 native ahead of the server (which seems okay running in Rosetta), that would make life better.

I am waiting for Apple Silicon M1 support, too.

Although VSL announced sth. long time ago, nothing has happened until today!

Still, I have to restart Studio One in Rosetta mode to work with the VST version of the Synchron Player. In native mode there is only the AU Player available.
The same with Dorico. Not a single VSL plugin or player shows up when you run it native, forget about the templates... !?!

Frankly, that's a big shame! The Player environment is CORE.
I can understand that the transition from elicenser to ilok was a big thing. But as it seems, there are enough resources to come up with new libraries every month – hmmm?!?

VSL must also take care for the existing customers, who already spent a lot of money for their products.
Most of the big brands, also the smaller 3rd party plugin developers have updated to M1 support – why not VSL.

This situation is ridiculous, sorry VSL team!

Just a small side-note here on the releases of new VSL libraries while many customers are waiting for M1 native coding in VSL's current software products.

Library editors, whose painstaking, highly skilled craft and art play a huge part in making VSL's sample libraries world class, aren't necessarily also skilled in programming and coding software.

What were VSL's library editors supposed to do while all software hands were on deck working hard to get the iLok transition done? Just sit there twiddling their thumbs?

Tired to wait for Apple Silicon M1 support.. so disappointed

Hello VSL people! I read most of the post here. Is this the issue here. I have a VEP template on my PC set up on multiple MIDI channels for using on Logic with   VEP AU3 plugin, and now I bought the M1 Mac. VEP 3 plugin does not show up even though it has passed validation. It has been a lot of time already since invention of the M1. Is this the issue of the plugin and I need to work with Rosetta on Logic just for this reason??? No??????????!!!!! Errata it is not validating !!!! Shame for VSL if this is true. IS there any solution?

So is the support doing SOMETHING? Is there ANY reply for my question? I would like to here from you, OK I understand you were busy with converting iLok but we have M1 machines and we need to work properly. at lease with VEP Plugin AU3. Any solution??

"Are we nearly there yet Daddy?"

Lolol.

Adding another plea for an M1-compatible VEP plugin, above all else.  It really doesn't matter what new libraries come out if we can't access them with VEPro. 

Now that the iLok transition is done, and we all spent hours reinstalling VSL libraries to accommodate VSL's change, please give us customers something in return- access to them through VEPro on M1 Macs.  PCs run all of my libraries in VEPro, and will for years to come.  The server can wait.  The plugin is long overdue. 

@Macker said:

"Are we nearly there yet Daddy?"

Lolol.

"I told you we are going far, far, faaar-away, son."

😉

@Macker said:

"Are we nearly there yet Daddy?"

Lolol.

c

"We should always remember that sensitiveness and emotion constitute the real content of a work of art."
~ Maurice Ravel

I've always found it amusing how people who project this image of "sensitiveness" often fall short of that supposed ideal. Your quote states something different than your post. 

@Michael Canavan said:

I've always found it amusing how people who project this image of "sensitiveness" often fall short of that supposed ideal. Your quote states something different than your post. 

Yeah, but when will can expect a VST3/M1 native version?

Hi, 

It's high on our list, but I can't give you an ETA - it usually only causes disappointment when things don't go as planned. 

But rest assured that we're on it!

Best, 
Paul

Really appreciate the reply - I love my M1 mac and like others very eager for a compatible update (so I can tap back into my PC-hosted samples in particular)...hearing that it is at least a priority is a relief.  

Thanks for the response. Even periodic no-update updates reiterating that M1 compatibility is a priority for VSL are reassuring.  

Is VEPro MAS for Digital Performer not currently working with M1 Macs?

I can't seem to find information about this anywhere.

DP needs to run in Rosetta mode to work with VEP currently. The MAS VEP plugin doesn't work if DP is running natively.