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. 

@Dan Wool said:

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

Thanks Dan, much appreciated. 👍

  OK so my last post seems a bit harsh, but let's look at one simple obviously not scientific but glaring example of why thinking that Apple Silicon support is a low priority is a blatantly bad business move. This thread has 13,903 views, look at the other threads here and tell me this isn't an important topic? There was a comment from a VSL employee here in the forums on the thread on the iLok transfer stating that there weren't that many users using M1 Macs, wonder why this is a hot topic then right?