What generated this list of what plugins are running AS native, or not, in your system?… 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.
-
… 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
-
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.
Please inform us VSL Team. It's almost 2 years since m1 machines released.
-
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!
-
..... that's great news that it's 'imminent'.
I wonder what performance gains might be expected ?
-
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
-
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.
Ben@VSL | IT & Product Specialist -
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.
-
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.
Ben@VSL | IT & Product Specialist -
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.