196,189 users have contributed to 43,015 threads and 258,397 posts.
In the past 24 hours, we have 1 new thread(s), 9 new post(s) and 172 new user(s).
As a followup, I am seeing identical performance on both my late 2012 Mac Mini i7 and my new 2021 Mac Mini M1 with no performance improvements on the new M1. This is a little surprising given that I receive CPU overloads on both with identical settings.
I look forward to seeing an update that utilizes the M1 architecture.
One thing that's missing from this conversation in general is this. It would be absolutely fantastic to get the plug in VEP in VST, MAS, AU etc. ported to Apple Silicon first. this seem entirely possible and solves a major issue with Apple Silicon Macs in general, i.e. you could run your DAW (well most DAWs at this point anyway), in native and host x86 plug ins on a VEP server on an older Mac or PC.
I'm actually kind of shocked this isn't or doesn't seem to be the plan? Most of use obviously have an older Mac or PC with enough RAM, the new M1s anyway are a bit short on RAM, but the idea of being able to offload x86 plug ins, in some cases permanently (Alchemy, older versions of plug ins etc.), with VEP makes total sense.
I will probably end up using the AU version, but as a DP user I really want to use the amazing MAS version on the Apple Silicon Macs, reducing the possibility of incompatibility and exponentially upping track count!
I came here to search for and inquire about exactly this scenario - an M1 running the host sequencer, with VEPro on high-RAM slaves. All we need is the VEP plugin to work (MAS for me, AU for others).
I am considering adding an M1 for exactly this purpose, but if native support is months away for VEPro plugins (server can wait), I might not get an M1 and add another slave instead.
One thing that's missing from this conversation in general is this. It would be absolutely fantastic to get the plug in VEP in VST, MAS, AU etc. ported to Apple Silicon first. this seem entirely possible and solves a major issue with Apple Silicon Macs in general, i.e. you could run your DAW (well most DAWs at this point anyway), in native and host x86 plug ins on a VEP server on an older Mac or PC.
Yeah I have to say I don't get it at all?
If Vienna released the VEP plug in as native Apple Silicon, they could make a strong argument for new customers to purchase VEP7 to run plug ins on their old machines as VEP slaves, that currently do not work in M1 macs.
Currently it seems that the plug in works as an x86 under Rosetta, but it's mixed results. The MAS version doesn't work for instance.
I just think it's weird, I would think getting the plug in version of VEP out quickly would be a priority, but I don't know the mechanisms at place.
Agreed, first order of business is the plugin, one may simply use slaves for the samples, being able to instantiate VEP on the host machine is only truly needed if the local host is all there is.
There with you. I would love MAS support, I've only had an M1 Air for a few days now but it just really does seem to be ridiculously solid. The only three Rosetta devices so far are VEP, Slate Raven and dependent libraries in UPDD and V-Control Pro, and Amplitube. Waiting impatiently for native versions.This really can't come soon enough. Truly begging for VEP native Apple Silicon at this point and sending all the good vibes/well wishes and anticipatory gratitude to the amazing programmers at VSL to make this happen! (especially MAS for DP which is already ARM native!).
It's really sad, and in my opinion poor customer relations that VSL have provided no information on their plans and timeline for M1 compatibility for about a year now.
I've always felt that VSL is a PC centric company from comments by the developers/programmers. It's likely they develop on PC first and then port over to MacOS which often results in disregard of Mac development guidelines and aesthetic issues as well as slow adoption when Apple makes changes to the OS.
They are not willing to officially say so, but I do believe VSL would actually prefer if everyone just used PCs.
Hi guys,
We'd love to get to M1 upport right away and it is high on our list, but the transition to iLok is our top priority right now.
All our developers are working on Mac and have done so for years. It doesn't matter to us which OS our users prefer.
Best,
Paul
Thanks for the update! Is a native VE Pro MAS plugin version in the works as well? As you may know the MAS version doesn't work in Rosetta2. My templates rely on the functionality in the MAS plugin. Thx.Hi guys,
We'd love to get to M1 upport right away and it is high on our list, but the transition to iLok is our top priority right now.
All our developers are working on Mac and have done so for years. It doesn't matter to us which OS our users prefer.
Best,
Paul
Hi guys,
We'd love to get to M1 upport right away and it is high on our list, but the transition to iLok is our top priority right now.
All our developers are working on Mac and have done so for years. It doesn't matter to us which OS our users prefer.
Best,
Paul
I'm sure it doesn't help that PACE is taking their sweet time to release m1 native build and all the various support files developers need to build their own m1 native versions. Seems like every single developer that relies on iLok has been at a standstill for the past year as far as I can tell, just waiting on PACE.
Thanks for the update! Is a native VE Pro MAS plugin version in the works as well? As you may know the MAS version doesn't work in Rosetta2. My templates rely on the functionality in the MAS plugin. Thx.
As a way of managing expectations: Would we be correct in assuming this transition will take place after iLok can run natively on M1? A lot of developers seem to be in this position.Hi,
Our transition to iLok is still our #1 priority, but native Silicon support is high on the to-do list after this. Thanks for your patience!
Best,
Paul
