I'm working with VSL in Nuendo and Dorico. I needed a computer replacement and upgraded to an M1 Mac Studio (20-core CPU and 128GB memory - so as grunt as you can get). I've had to stop using VSL for my large orchestral project because running Nuendo or Dorico in Rosetta mode isn't functional - there is too much processing overhead. I've temporarily swapped to using Spitfire's BBC SO to make do while I'm waiting for the VSL native release. I'm sure many other users have had to purchase new M1 machines, and Apple is converting its whole product line across. Having to make workarounds for an extended period isn't ideal. I'm hoping we are going to see a release ASAP. Lots of professional users don't use Logic.
-
I am considering moving my sample hosting to Cantabile for this reason. I already have a 128G server at the studio with Cantabile hosting, and it works extremely well - quite possibly lower cpu usage than VEPro. I/O is limited to hardware, but I've done this with another sample server for years. It may take a while for a stable version even after an M1 native release. I could be wrong, but it really is impossible to wait this out and let the M1s sit idle. Thing is, once I make the move, I won't likely revert back to VEPro anytime soon.
-
I agree that the speed with which the VSL software is adapted to M1 is disappointing however they are certainly not the only company having problems getting their software adapted. Apart from Kontakt all Native Instruments soft and Hardware still needs Rosetta.
Do you really have such big issues using Rosetta with Dorico? I am running a Dorico 4 project using Rosetta with 70 instruments in the VST rack, 49 VSL Synchron and the rest BBCSO and a few Kontakt Percussion instruments. It takes bit of time till the project is playable but I have no big issues when it is ready to play. Sometimes a few clicks when 2 or more instruments are played at the same note for the first time in a session (a CPU peak). You also see it very well in the Logic CPU monitor. When you play it a second time there is no peak nor clicks.
Before my M1Max I had to use VEPPro for this size of project as I had only 16 GB on my Intel MBP but with the new M1Max and 64 GB this is not needed.
I did test VEPPro with a similar size template but only with Logic (so no Rosetta needed). The main reason at the time was that the Synchron player did not work directly in Logic whereas it did work when accessed through VEPPro. Now the Synchron Player works directly in Logic.
-
Any news? M1 support
It is taking a very long time... Digital Performer 11 (Universal) was released over a year ago but I can't use it because VEPro 7 MAS is unusable with Rosetta 2 and DP11. So I'm stuck with Digital Performer 10 under Rosetta 2, which only just works and crashes a few times each day.
-
Any news? M1 support
It is taking a very long time... Digital Performer 11 (Universal) was released over a year ago but I can't use it because VEPro 7 MAS is unusable with Rosetta 2 and DP11. So I'm stuck with Digital Performer 10 under Rosetta 2, which only just works and crashes a few times each day.
I'm finding Rosetta 2 stable with stereo projects in DP. It's getting very old having to switch back and forth between native and Rosetta simply to accommodated projects with VEP, but it's working here. It's off-topic for this thread, but you might try posting on motunation.com re this, if you haven't already. I'm not optimistic VEP will become native anytime soon.
-
I'm not optimistic VEP will become native anytime soon.
Why? Both Paul and Ben said they were working on it. Since MIR Pro 3D is out and the transition to iLok is complete, the can fully focus on that.
Good point. Call it professional pessimism on my part. I couldn't guess how long a transition like this might take, but having those two items completed should speed things up.
-
I'm not optimistic VEP will become native anytime soon.
Why? Both Paul and Ben said they were working on it. Since MIR Pro 3D is out and the transition to iLok is complete, the can fully focus on that.
Good point. Call it professional pessimism on my part. I couldn't guess how long a transition like this might take, but having those two items completed should speed things up.Hopefully that's the truth. NI, Audio Ease and VSL are my biggest laggers, and NI is oddly stepping out in front with Kontakt and Guitar Rig both AS ready.
-
Any news? M1 support
It is taking a very long time... Digital Performer 11 (Universal) was released over a year ago but I can't use it because VEPro 7 MAS is unusable with Rosetta 2 and DP11. So I'm stuck with Digital Performer 10 under Rosetta 2, which only just works and crashes a few times each day.
Oh my! I'd started a new thread figuring all of this would be figured out by now and that the answer would be easy. The e-licenser version is working fine with Pro Tools Ultimate HD, Mac Studio Ultra / Monterey 5.1 - I'm just worried it will up and die on me at some point.
Thanks
-
Hi Paul,
We really need some kind of ETA now. Personally, I use VEP in game production on a daily basis, and spent years refining my template, balancing, relying on VEP. I've been a VSL user since 2008, so been around here for quite a long time, also educating university students to use VEP, among other things.
My old computer is getting less and less reliable, so I bought a maxed out Mac Studio now, and still the processing overhead by using Rosetta in Cubendo is simply too high for any serious work to be done. Doesn't really matter if VEP works well, it's the other CPU demanding plugins that are forced to run Rosetta that will be bottlenecks.
If VEP is not made compatible within a reasonable time frame (months, not years, it's been almost 2 years since Silicon was first released), I'd have to redo my entire template internally in Nuendo, and after that I will never ever go back to VEP, or recommend any of my university film scoring students using VEP for that matter.
Please, give us something.
Hi,
It's high on our list, but I can't give you an ETA - it usually only causes disappointment when things don't go as planned.
But rest assured that we're on it!
Best,
Paul
-
I am inclined to agree. 2 years is patient. The amount of other libraries being released by your company, you clearly are paying the people to do thatā¦ can you not spend the resources on coders to finish this transition? The problem is that now your hold up is not just effecting your products, which if were just your products being run then you would swallow the extra overhead with rosetta as a āthat sucks, but it is what it isāā¦ but it isnāt just yours, itās now an overhead which is forced onto any and all other software because you canāt run both rosetta and native at the same time. 2 years is a long time VSL. Genuinely. You are in a tiny tiny minority of music software developers and developers in general to have NOT upgraded, or not even delivered a beta yet? I am, like so many others getting to the point where I canāt put off upgrading any more. True, music is one of the least taxing affairs amongst the creative workspaceā¦ but a lot of people donāt have the luxury of ONLY doing music, forcing upgrades in order to stay current with other software, or as hardware fails not wanting to spend a lot of money on completely outdated mac hardware that has less support life and is nowhere near as good bang for buck or investment. I myself have put off upgrading my hardware now since 2017! Originally planning for 2020, then postponing again until software moves overā¦ You are the last on the list, by a good margin. My computer getting old, and I will have to upgrade soon, and to be honest the rosetta 2 tax on your software is MORE than the tax of not running your software and just loading each instance into logic. Whilst I would be unable to run a slave computerā¦ the Apple silicon is so good that I might not need it. At that point, I would not bother with Vsl. Instead of my original plan, to grow my software with you and start transitioning to more of your libraries over East West and others. People are getting put into a position now that they will be forced to choose between abandoning your software in order to stay with Apple, and as time goes on, that number will not get smaller, only bigger. 2 years is rather a long time for nothing more than a āwe are working on itā.
-
Hi everybody,
We understand your position, and those last 2 years were very intense for everybody, in many ways.
Here's the catch with ETAs in software development: High probability of disappointment for both users and developers. We have been there, and it's not a good place.
So we decided to announce our products or essential updates only when they are ready and tested, good to go to make your world a better place.I can tell you that it's looking good at this point, but I still can't give you an ETA.
I will post and news in this thread first!
Thanks for your understanding!
Best,
Paul
Paul Kopf Product Manager VSL -
Way to stick to your guns Paul š Its probably the correct reply, even though we want to strangle you for it š I'm not in the AS boat yet even though I'm about to hop on, so I'm not as frustrated as many here...yet. I assume quite a few might need to move on or change their working ways, but I guess that's something VSL is willing to deal with. Best of luck and really hope things move smoothly, and quickly!
-
I have complete two commercial projects while swimming in the sea of VEP bugs, crashes note hangs and useless waste of processing power because of rosetta simulation. I just can't believe how long it's taking VSL to make this native silicon move. Very frustrated with no end in sight!
VEP and MIR PRO are the only two softwares in my HUGE template that still do not run natively..
-
-
I'd like to add my voice to the discussion here. At this point, having migrated successfully to a Mac Studio, Vienna Ensemble Pro stands out as the only software in my studio not yet ported over to silicon, or at least (and to be fair), the only critical piece. My sincere hope is that VSL will soon release a version capable of running natively on the M1, and I mean within days or weeks. Frankly, I'm starting to consider other options, and as at least one other poster has pointed out, once another solution is adopted, there may be no going back to VSL. I've always held Vienna Ensemble Pro in high regard, it is an elegant solution for professional composers. But VSL's sluggish response to the inevitable is disheartening.