I check this page at least once a week.  I always thought VSL was one of the better tech companies, not so much any more.  I would have been so happy if they rolled it out in phases, all I need is the VST plugin to be native.  I, like many other people, host all the samples on a PC.  So I only need the bridge to be native.  Then of course they could have rolled out the host software later.

That seems like such a simple concept, but here we are...still waiting...

Originally Posted by: glasswing

Just got the note that Pro Tools will be releasing a Beta that is compatible with Apple Silicon.  Avid is one of the most cautious software developers out there.  If VEP doesn't step up to the plate soon, that wonderful, unique and incredibly USEFUL Swiss Army knife will become a fossil.   I don't need new libraries.  But I would like to have all the old sessions I did with VEP to work. 
Apple Mac Studio Ultra / Pro Tools

Agreed, I'm constantly shocked that companies such as SoundToys and Avid are ahead of VSL on this.  I know that it's probably more complicated than I know, but clearly other companies are figuring this out.

I really doubt that it'll be another 6+ months.  My guess would be end of year, or January.  VSL has publicly said on this forum thread that they are currently working on M1 native comparability and it will come out soon.  Or something like that, I can't find the exact post.

Btw I'm not saying I'm not frustrated, or that I'm not shocked that VEP is the last thing in my setup that isn't M1 compatible.  But they did say it would be soon, hopefully they actually meant it.

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.

PS: for what its worth, I've been running VEP through Rosetta in Cubase on a Mac Studio M1 Max since June and it's been mostly stable as long as I don't go below 512 buffer size.  If I go below that VEP starts to crash and act up.  I'm very much looking forward to a native version so I can drop my buffer size, but otherwise it's been very stable.

I haven't used it in a long time, but Bidule by Plogue might work for you.  At the very least it's worth checking out.

Also @VSL as an alternative to silence, check out what NI did.

https://community.native-instruments.com/discussion/comment/30577/?utm_medium=email&utm_source=newsletter&utm_campaign=Community%20NL%20en%20%7C%20community%20members%20%7C%2025/09/22&utm_id=42b64c1f-5b78-43be-8c1b-35d8a39c9bcc#Comment_30577

They posted an estimated timeline and sent everyone an email about it.  Just saying, some companies choose to communicate.

I've found another form of a work around.  (dare I call it a fix)

I have an insanely large template 1000+ instruments spread accros 6 VEP instances.  I found that not all of the 6 instances were getting CPU spikes during tempo ramps.

I then narrowed it down further by disabling external sync in Kontakt to find specific kontakt instruments that would cause spikes.  I found that in my case Action Strings were causing the spike.  If I removed them - I no longer have spikes during tempo changes.

So I'm going to go through my whole template and find patches that are tempo sync'd and causing this spike issue.  I'll then place them on a seperate VEP which I'll know to disable if I'm gonna have a tempo ramp.

I'll just have to learn to not write with those specific patches during a cue with a tempo ramp. But this way it frees up the rest of my 1000 instruments and "quarenteens" the few problem children.

I'd be curious to see if this helps anyone else.