@rockdude9k said:

Wait, what did they do today? I don't see a native version yet. Also, and I can't believe I'm saying this, but Sound Toys (the slowest tech company in the world, lol), beat Vienna to the M1 Native punch. VEPis now officially the last pluginI own that is not M1 Native.

Hi there!

We are currently in the process of finishing and testing Apple Silicon compatibility for our software.
We can't announce an ETA yet, but we'll let you know as soon as we are confident everything works as expected.

Best, Ben

@Ben said:

Hi there!

We are currently in the process of finishing and testing Apple Silicon compatibility for our software.
We can't announce an ETA yet, but we'll let you know as soon as we are confident everything works as expected.

Best, Ben

Thanks for the update!

Hi Ben, this update is seriously appreciated!  Thanks!  Good luck to the entire team.  Wishing for a speedy and smooth transition to AS Native!

Cheers,
Evan

This is indeed great to hear. A lot of my setups are in VEP and I can use Logic in Rosetta only on my MacStudio Ultra because of your uncompatibile plugins.  I hope it will be out soon.

..... that's great news that it's 'imminent'.

I wonder what performance gains might be expected ?

@Louis C said:

..... that's great news that it's 'imminent'.

I wonder what performance gains might be expected ?

@Another User said:

We are currently in the process of finishing and testing Apple Silicon compatibility for our software.

Ofd course things can pop up and send it back to alpha but December sounds reasonable to predict. My issue is I suspect they just "had" to get all of their products besides VEP AS ready as well, which makes it slow to fruition. :-/ 

Well, they should know, we would be happy to pay for the upgrade.  I don't know how it is for Vienna, but there are a LOT of Apple users doing audio. - at least in North America.  When I started my studio (eighties), it was the only game in town.  It's possible there is a concern that, with the tremendous increase in machine ability, Vienna Ensemble Pro might be suffering from 'writing on the  wall' syndrome.  As in, there's not a lot of need for it.  Having a Mac Studio Ultra I can see that, but I would still use VEP.  
I just wish someone would find something better  - less rickety and cranky - than Kontakt. I would pay big money for that! 
Or for all virtual instrument folks to switch to dedicated plugins - as many are doing - which I AM paying big $$$ for.  

Case in point - I'd been wrestling with VEP and the dreaded Kontakt for two days - which is a LOT of time at 74 - trying to get the outputs working correctly.  Out of habit and being an old timer, I always do individual outs for audio.  Nothing was working.  In a combo of fury and panic I decided to try bypassing VEP and just running Kontakt - figuring my machine - Mac Studio Ultra - could handle it.  Sure enough!  After dealing with the incredible convoluted weirdness of Kontakt's tedious take on output architecture, I got it all working in about an hour.
This doesn't mean I don't miss or won't keep using VEP.  If nothing else, it's a great organizing tool and, once set up, it's incredibly plug and play.  
If I was a Vienna CEO, I wouldn't drag my feet too long on the VEP / Silicon problem.  
And I would design a better alternative to Kontakt.  They would have to widen the doors of their bank to make room for all the money they're hauling in.  The competition in orchestral virtual instruments is profound, but there's only one Kontakt and, to me, it's a sitting duck. 

VEP (licenser) / Pro Tools HD 2022.9 / Mac Pro Ultra 128G RAM / 2X Sonnet Echo Dual NVMe Thunderbolt Docks

Hi together,

I understand, that it may be a bigger undertaking to bring VEPro to M1. But I guess upgrading the Plugin alone can't be that hard. I have the server on a Windows machine but I cannot run Cubase on my Mac natively, ONLY because the VEP Plugin is not M1 compatible. Super annoying.

Hope they will bring it asap

@HONEYHILL said:

Hi together,

I understand, that it may be a bigger undertaking to bring VEPro to M1. But I guess upgrading the Plugin alone can't be that hard. I have the server on a Windows machine but I cannot run Cubase on my Mac natively, ONLY because the VEP Plugin is not M1 compatible. Super annoying.

Hope they will bring it asap

Could you please double check? I'm not a Mac user and today is a national holiday, so I can't ask my colleagues right now, but if I'm not mistaken the VEP plugin itself is already M1 compatible for quite some time.

@HONEYHILL said:

Hi together,

I understand, that it may be a bigger undertaking to bring VEPro to M1. But I guess upgrading the Plugin alone can't be that hard. I have the server on a Windows machine but I cannot run Cubase on my Mac natively, ONLY because the VEP Plugin is not M1 compatible. Super annoying.

Hope they will bring it asap

Could you please double check? I'm not a Mac user and today is a national holiday, so I can't ask my colleagues right now, but if I'm not mistaken the VEP plugin itself is already M1 compatible for quite some time.

Ugh! this is pretty depressing when someone from VSL doesn't even know their own products compatibility status. No, the VEP plug in is not Apple Silicon native, only the AU version will run in a native DAW. 

The solution of having VSL code the plug itself to be native first and foremost was suggested in this thread a couple years ago. It makes total sense, and would have been and ideal solution until the rest of the application could make it over, it did not happen. 

@Michael Canavan said:

Ugh! this is pretty depressing when someone from VSL doesn't even know their own products compatibility status.

Yeah, right, especially since answering questions in a forum is my only job...

Like I said, I'm not a Mac user, so I usually don't care about Mac issues and forward them to colleagues who are more qualified answering these. Today is national holiday, so most of us don't work right now.

@Michael Canavan said:

Ugh! this is pretty depressing when someone from VSL doesn't even know their own products compatibility status.

Yeah, right, especially since answering questions in a forum is my only job...

Like I said, I'm not a Mac user, so I usually don't care about Mac issues and forward them to colleagues who are more qualified answering these. Today is national holiday, so most of us don't work right now.

So you're a platform loyalist, Ugh! Why are you the only person from VSL that is replying in this thread then? It makes your announcement of Apple Silicon in beta that much more useless that you "don't care about Mac Issues". 

Why would anyone work for a cross platform company and not follow their own companies compatibility issues, that have been going on for two years now? I'm sorry but this is one of the worst most dismissive responses I've seen from a company in years. I'm not trying to be harsh, but I have no idea if you're paid or not for participating in the forums, I'm glad someone does that's not even an issue. It isn't as much of an issue to me as the fact that you openly admit you don't know or care about issues for half of your own companies customers.

  You deserve this dressing down, pay attention to your own products issues on both platforms, and don't act rude when people call you out for not knowing two year old information about your own product. You're literally adding flame to the fire here. 

I am not part of our support or marketing team. This is a user forum; if you like to get support here is our official support channel: support@vsl.co.at

I do my best to be helpful in forums just because I like doing music and I also like our products.
And just because I don't use an Apple device I "deserve this dressing down"? No thanks, I'm happy to leave this conversation. Have a nice day.

Regardless of what Apple has said so far, M1 users are still early adopters, especially with regards to audio production.  In my view, it's still most sensible to remain on Intel Mac hardware for serious audio production, for at least one more year.   This is not only because of VSL software which is clearly not transitioned yet, but numerous other software and plugins which are still not native.  You MIGHT be able to get some rosetta functionality, but me personally, I won't get an Apple Silicon Mac until I know that I can run pretty much everything I want or need to run in native mode without ANY rosetta shenanigans...which the industry is simply not there yet in many cases.  They will all get there eventually..including VSL, but all I can say is that you have to be patient.  I feel the pain for anyone that jumped on the M1 bandwagon, but what I can say is that my cheese grater is still running absolutely everything without problems...and that is a solution that anyone can still choose to follow today.  Even the current Apple MacPro is still Intel and will run everything just fine.  It was your choice to be early adopter.

@Ben said:

I am not part of our support or marketing team. This is a user forum; if you like to get support here is our official support channel: support@vsl.co.at

I do my best to be helpful in forums just because I like doing music and I also like our products.
And just because I don't use an Apple device I "deserve this dressing down"? No thanks, I'm happy to leave this conversation. Have a nice day.

 It's a mess, and it will be a mess until VSL complete the transition, it's why you see people talking about other solutions in this thread, or the guy above my post just slamming VSL. It's really too bad, because I'm probably not alone in having kept a Mac Pro with 12 cores being a great server withe an Apple Silcon laptop that will be a great DAW host once everything is Apple Silicon ready. 

@Dewdman42 said:

Regardless of what Apple has said so far, M1 users are still early adopters, especially with regards to audio production.  In my view, it's still most sensible to remain on Intel Mac hardware for serious audio production, for at least one more year.   This is not only because of VSL software which is clearly not transitioned yet, but numerous other software and plugins which are still not native.  You MIGHT be able to get some rosetta functionality, but me personally, I won't get an Apple Silicon Mac until I know that I can run pretty much everything I want or need to run in native mode without ANY rosetta shenanigans...which the industry is simply not there yet in many cases.  They will all get there eventually..including VSL, but all I can say is that you have to be patient.  I feel the pain for anyone that jumped on the M1 bandwagon, but what I can say is that my cheese grater is still running absolutely everything without problems...and that is a solution that anyone can still choose to follow today.  Even the current Apple MacPro is still Intel and will run everything just fine.  It was your choice to be early adopter.

While I can mostly agree with this, but it's been 2 1/2 years since Apple Silicon was announced, along with developer Minis, and 2 years since the first M1 Macs came out. I was around for the first transition from PPC to Intel machines, and I remember only NI dragging their feet a little, they had foolishly not headed Apples warnings to switch from Codewarrior to to Xcode. 

  Part of the problem is Rosetta this time works really pretty well, a maybe 10% CPU hit on average, but it doesn't work at all for VST and MAS if the DAW is not in Rosetta. So the hit is compounded when your DAW is also in Rosetta. Anyway I thought the VEP plug in would be a rather quick port considering the opportunity for VSL to pick up new customers as people used VEP to transition, but that's not the case apparently.