@bdr said:

are there any realistic alternatives?? The lack of urgency is intolerable.

AudioGridder is native. I haven't used it so I don't know how well it works, I still would prefer to stick with VEP. But I'm still not in AppleSilicon yet (but soon!) so I can wait, unlike some of you folks. Hopefully you find an alternative, even if its temporary.

I began exploring Audiogridder (silicon native) with Cubase Pro 12 today on a Mac Studio (M1 Max) as my DAW computer, and a 2013 Mac Pro and 2018 Mac Mini as farms. Audiogridder is working beautifully, with the added (and significant) bonus of letting me use effects (CPU-hungry reverbs etc) residing in the farms. There are several Youtube videos on the subject. Oh, and Audiogridder is available for free. As I've only now started exploring this avenue, my remarks reflect a very optimistic assessment, but nothing more, at least for the moment. Having said that, I have a project that can no longer wait, and VSL's schedule is a mystery, so I must move on to Audiogridder. I had hoped otherwise.

@manu_28410 said:

… Same here.

It really doesn't look good now — Cf. linked image — for a high-priced products company.

The demo I've been running lately on my brand new Mac Studio clearly presents pops and glitches when I run even a small session. Compare to other software and libs, that's awkward; but maybe not… if you add Rosetta to the equation.

Now every time I want to buy a VSL product, I'm very hesitant: for instance, I could be on the verge of jumping for MIR … but… Will I regret putting an extra 1K in this company in 6 months?

I fully agree and it makes me mad that they did not do until today, October 18th. Maybe they sell it to us as a Christmas Gift.

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.  VEP is now officially the last plugin I own that is not M1 Native.

@manu_28410 said:

… Same here.

It really doesn't look good now — Cf. linked image — for a high-priced products company.

The demo I've been running lately on my brand new Mac Studio clearly presents pops and glitches when I run even a small session. Compare to other software and libs, that's awkward; but maybe not… if you add Rosetta to the equation.

Now every time I want to buy a VSL product, I'm very hesitant: for instance, I could be on the verge of jumping for MIR … but… Will I regret putting an extra 1K in this company in 6 months?

I came across this today and remembered where I first saw it...

https://github.com/DigiDNA/Silicon

@bdr said:

I came across this today and remembered where I first saw it...

https://github.com/DigiDNA/Silicon

@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.