Vienna Symphonic Library Forum
Forum Statistics

191,343 users have contributed to 42,795 threads and 257,355 posts.

In the past 24 hours, we have 1 new thread(s), 4 new post(s) and 46 new user(s).

  1. Home
  2. Announcements
  3. Apple Silicon Native Transition
  • S
    S
    last edited
    last edited

    @Michael Canavan said:

    What I worry about is the MAS version making it to Apple Silicon. Digital Performer gets ignored a lot these days, and the MAS version is so much better than the AU version in DP it's night and day. I don't have much trust in the VST3 format, 15 years later and it's still buggy here and there. 

    +1 on the MAS. I‘ve pretty much completed migration to my maxed out M2 laptop, all native, & as great as it is, I could see me still getting some use out of my old iMac Pro through VEPro. I‘ll probably never leave DP (unless the others suddenly decides to add wait-for-note capability), please please please….MAS 🙏🏼
  • D
    D

    I see there is a new VSL Pro 7 update, v7.2.1526, and there is something in the notes about this version being a preparation for Silicon. Could you give us more information?
  • PaulP
    VSL Team
    PaulP

    Hi, 

    This will most likely be the last version before the Apple Silicon version, and it will be a reliable rollback option. All fixes have been integrated in our Silicon development environment as well, so we're getting closer. 

    Unfortunately I still can't provide you with an ETA (we will simply release the version when it's there), but the beta versions we're working and testing with are impressively stable.

    Best, 
    Paul

    Paul Kopf Product Manager VSL
  • M
    M
    last edited
    last edited

    @dmansfield said:

    I see there is a new VSL Pro 7 update, v7.2.1526, and there is something in the notes about this version being a preparation for Silicon. Could you give us more information?

    I would skip that version if your are using the MAS version. I'm getting a lot of clicks and cuttoffs with just one track playing (with my buffer set to the max 2048.) Just unusable on my system. Reverting back. Hopefully the proper native M1 is ready soon, long time coming.
  • R
    R

    Really looking forward to the day I don't have to check this forum every morning...
  • W
    W

    Still checking this thread for update every morning...
  • M
    M
    last edited
    last edited

    @Michael Canavan said:

    What I worry about is the MAS version making it to Apple Silicon. Digital Performer gets ignored a lot these days, and the MAS version is so much better than the AU version in DP it's night and day. I don't have much trust in the VST3 format, 15 years later and it's still buggy here and there. 

    +1 on the MAS. I‘ve pretty much completed migration to my maxed out M2 laptop, all native, & as great as it is, I could see me still getting some use out of my old iMac Pro through VEPro. I‘ll probably never leave DP (unless the others suddenly decides to add wait-for-note capability), please please please….MAS 🙏🏼

    I emailed them and they confirmed the MAS plug in is also being ported. 
  • A
    A

    Another week, more crickets...
  • W
    W

    The pain... Apple just announced M2 Ultra machines yet I'm still running Rosetta...

    I know the devs are working hard, but man the wait is just too long...
  • R
    R

    Yup, 8 CPU releases now (plus the DTK).  And yet we are all gonna reward VSL when it does come out by giving them our money.

    Really wish there was a viable alternative at this point...

     

    And yes I've checked out AudioGrinder, but I've invested so much time and thought into my VEP rig that redoing all of that work with a company that is just getting started seems risky.

     

    Maybe in a couple years I'll switch.  Definitely feel left out to dry by VSL right now.
  • W
    W

    I agree 100% I am absolutely shocked! Beta testers (who are friends) are using the silicon version of this product flawlessly! Yet, there is no option for us to at least jump into that version. And even more no clear communication other than we are working on it. I look forward to the day VEP is not needed because computers can handle the task. 
  • S
    S

    It's hard to be too sympathetic to VSL. We're now 3 years removed from the developer release of the M1 chip (WWDC20 in June, 2020). As a software company that makes software for Mac, you'd have to think that they'd have been aware of developer previews of a new chip. I'm sure they were. Even if they weren't, though, the M1 was released to the public in Nov, 2020. That's two and a half years ago. If it was important to VSL, they'd surely have completed the update by now. Yes, it's hard to refactor programs to work with a new chipset, but 2 1/2 to 3 years is a long time in developer time. My guess is that, although this group of users really wants VEP, we are a small group. As a business, VSL is probably more interested in growing their sample library business. I'm sure there's a much larger customer base there.

    Apologies if this has been said - I can't read the whole thread. I too have been waiting all this time, sadly. 
  • D
    D

    I gave up on waiting for VEPro.  VEP only hosts samples on one PC slave now (standalone version, not the server).  The other runs Cantabile.  I moved to digital audio I/O and network/RTP midi to connect my M1 Mac to both PCs.  It works very well, is very stable, and I can stay 100% M1 native with DP, Logic, ProTools or Nuendo without worrying about VEP plugin/server M1 compatibility, and processing overhead is lower.  

    I made the switch from PC to Mac this year specifically to run DP, and it made zero sense to step backwards in speed and buy an Intel Mac just to stick with VEP, especially with M2s already on the horizon at the time.  

    Sorry VSL, but 3 years really is too long.  We have work to do, and little time to make these major changes.
  • D
    D
    I am fed up with checking this thread every morning. How long does it take now? Please please let us know. We are too tired of hearing "we are working on it."!!!
  • W
    W

    Lots of pro users just ordered the M2 Studios.

    VSL: "Hey guys, sorry that the new shining expensive machine you just bought would have to take a performance hit because we still have not updated our software, and there's nothing you can do about it."

    So frustrating...
  • S
    S
    last edited
    last edited

    @dmansfield said:

    I see there is a new VSL Pro 7 update, v7.2.1526, and there is something in the notes about this version being a preparation for Silicon. Could you give us more information?

    I would skip that version if your are using the MAS version. I'm getting a lot of clicks and cuttoffs with just one track playing (with my buffer set to the max 2048.) Just unusable on my system. Reverting back. Hopefully the proper native M1 is ready soon, long time coming.

     

    Thanks Paul! I am just so happy that you are taking the AS update so seriously and will provide us with a version ASAP. I see a lot of complaints, but I really don't think we are entitled to anything. I am just thankful that you are doing a native AS version to continue making our (template) lives easier with VEP!

    I know it's been taking a while, and it's a bummer for earlier adaptors. But we knew that VEP wasn't native and had no date for when it would be. So I really don't think anyone can complain.
  • D
    D
    last edited
    last edited

    @dmansfield said:

    I see there is a new VSL Pro 7 update, v7.2.1526, and there is something in the notes about this version being a preparation for Silicon. Could you give us more information?

    I would skip that version if your are using the MAS version. I'm getting a lot of clicks and cuttoffs with just one track playing (with my buffer set to the max 2048.) Just unusable on my system. Reverting back. Hopefully the proper native M1 is ready soon, long time coming.

     

    Thanks Paul! I am just so happy that you are taking the AS update so seriously and will provide us with a version ASAP. I see a lot of complaints, but I really don't think we are entitled to anything. I am just thankful that you are doing a native AS version to continue making our (template) lives easier with VEP!

    I know it's been taking a while, and it's a bummer for earlier adaptors. But we knew that VEP wasn't native and had no date for when it would be. So I really don't think anyone can complain.

    AS Macs had been shipping for over a year when I bought my M1 Max, so I don't exactly consider myself an early adopter. Apart from VEP virtually all of my plugins could run in my DAW running natively when I bought my AS Mac. VSL's position on VEP's transition to AS in 2021 was nearly the same as it is now. "It's a priority but we can't give you an ETA". A reasonable statement for them to make. The problem is that none of us "early adopters" dreamed it would take this long. VEP is officially pulling up the AS caboose to a train that's been in route coming up on 3 years now. Fortunately AS legitimately seems close now. Fingers crossed we see it this year. 
  • E
    E

    "I know it's been taking a while, and it's a bummer for earlier adaptors. But we knew that VEP wasn't native and had no date for when it would be. So I really don't think anyone can complain."

    Are you joking? 
  • R
    R
    last edited
    last edited

    @Paul said:

    Hi, 

    We are all waiting for the next great beta version from our development team, they're ironing out a few bugs with VE Pro.
    So I'm PERSONALLY calculating with the next weeks, but I have been wrong before, and this is unfortunately not an official announcement. 

    Best, 
    Paul

     

    Six weeks later and no release yet.  Cool...
  • E
    E

    Hi everyone,
    I hope the release will be soon, I've been waiting for months, my patience is coming to an end. Working with VePro MAS, I have to use everything in Rosetta mode and it is tremendously slowing down my system (Studio Ultra). It nearly seems as if I was working on my previous 2010 5.1, very very disappointing. 
    If there had been an alternative for me, I would have switched a long time ago. 
    I am of course ready to pay for the new version.