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.
-
I'm limping along with my old Mac Pros waiting for this update, but clearly VSL has hit a wall somewhere with the M1 port, maybe multiple walls. I'm finishing up a score in the next few weeks but can not limp along with my bunch of old cheesegraters any more, I have to make the switch before the next serious project comes in. Does anyone have a workaround (compatible with DP 11)? A substitute for VEPro that can run native?
-
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.
They posted an estimated timeline and sent everyone an email about it. Just saying, some companies choose to communicate.
-
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.
-
Ditto here with DP11. Stable with Rosetta. But it is getting old staying at 512, as is a lot of other aspects of running DP in Rosetta....for better or worse I've actually grown used to playing with a 512 buffer over the years.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'm strategizing how to divest myself of using VEPro. I get that there are technical complications with how to do this, but if VSL can't keep up with the technology (and it's been over a year) then they no longer have my business. Such a shame.
-
I'm strategizing how to divest myself of using VEPro. I get that there are technical complications with how to do this, but if VSL can't keep up with the technology (and it's been over a year) then they no longer have my business. Such a shame.
are there any realistic alternatives?? The lack of urgency is intolerable.
-
are there any realistic alternatives?? The lack of urgency is intolerable.
When I have time I am working through configuring Cantabile to run as the host on my i7 with RTP midi to connect to DP on my Mac M1. That's my longterm plan. The downside is being more limited on audio streaming back using hardware I/O. But the upside is that is very stable. I've been running an older i7 slave this way for years.
This probably won't work for some, but it is an option, and one I know works well now.
-
are there any realistic alternatives?? The lack of urgency is intolerable.
AudioGridder is native. I haven't used it so I don't know how well it works, I still would prefer to stick with VEP. But I'm still not in AppleSilicon yet (but soon!) so I can wait, unlike some of you folks. Hopefully you find an alternative, even if its temporary.
-
… 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?
