Yes of course, though I’m going to release it in stages
2 Likes
I’ve had struggles with apple silicon but found solutions to everything (until plugins are native ARM [Matt take your time, I’m a paid customer and love it]). Been using Vital for over a year with an M1 MacBook Air with Ableton Live 11. It always went smooth on 11. 11.1 is now native apple silicon.
Short answer: open Live 11.1 in Rosetta mode. See below.
I just want to share my solutions for anyone having similar struggles.
VST doesn’t work on M1, but AU does (any old projects or for vst it has to be opened in intel mode). Native apple silicon mode usually works fine, but sometimes the menu on vital is blank, which usually happens when I open the plugin screen while I’m playing music. So pausing and reopening the window works.
I have export issues sometimes with apple silicon. The way to get around it is to reopen the project in intel mode for the export. You open the same Live application but set it to open in Rosetta first. Navigate to your applications folder, right click the Ableton Live program and select Get Info. On the info window, check the ‘Open using Rosetta’ checkbox. When it’s checked, Ableton will open the intel version. All non-native plugins will work, and my export issues are solved.
Happy music making everyone.
Seriously? Your paying plus customers are not important enough or should upgrade to pro? Never buying another product from you again…
Not sure where the confusion is but as I said a couple posts back, everyone will get the upgrade for free.
Mac M1 users…
2 Likes
Being a little self-righteous, aren’t we? The reality is… 2/3 of the (much more expensive) plugins that I own still do not have native Apple silicon compatibility, so until the larger plugin companies with bigger dev teams manage to update their products to run natively, I can’t really be too upset that a one-man developer like Matt is still working on it. Seems like reasonable expectations to me.
If you “wanted to support the project”, you wouldn’t be bitching and threatening to “go back to Pigments” lmao.
Windows can solve the problem.
Wow. What a flame fest. For those of you that don’t understand, it takes literally three minutes to compile a native ARM binary. I have one. There is one attached to this thread that was compiled by a user. Absolutely zero code updates are required. Matt is working on new features. I get that. Y’all take care now.
The ARM binary attached to the thread is fantastic too…just to provide a little more info for those with M1 machines. I highly recommend grabbing the binary posted in this thread until the official version is released. You will have to move all of your presets, etc to the new folder created when first launching the ARM native VST3 version, but definitely worth it imo.
While I agree it’s in very poor taste (not to mention very unreasonable) to scream at Matt for the totally understandable dev time it takes to release a bug-free update…I think your estimate on 2/3 of the much more expensive plugins not having Apple Silicon compatibility is a little off. Almost every “big” company has updated their plugins to run natively on Apple Silicon…even iZotope had an update last week that brought native support to the bulk of their plugins. That said, Matt is one dude so people need to have a little empathy and manage their expectations. Also, its not like there isn’t a native compiled version available in this very thread.
I think you are misunderstanding as well. I wasn’t screaming at Matt. I might have been a bit direct but I certainly wasn’t screaming. Consider this - It took me, a C# developer several hours of research to get the open-source C++ code to build on my machine. That’s because a) I’m not an experienced C++ developer and b) the commercial Firebase stuff was left in the code that was put up on GitHub. Firebase is part of what’s used to authenticate yourself in the commercial edition and download plugins, updates etc. I did not really have to add anything at all. I had to remove stuff that would only build on one persons machine. That person is Matt. Without his machine I had to just make modifications the he wouldn’t have to do. Once I figured out how to configure it to run “vanilla” it built fine on my machine. The VST plugin attached to this thread was built based on my GitHub repository where I did these several hours of work. As folks have mentioned, it works fine. I have since done quite a bit of clean-up to my fork of the repository and am actively working to convert it over to a CMake based build so I’m not just sitting around here like a bliss ninny asking for stuff.
So I estimate that if Matt had an M1 Mac and opened his own GitHub repo or Private repo at the current version it would compile to ARM fine for him. @Tytel, please chime in and correct me if I’m wrong here. That’s why I half-jokingly asked if he wanted to borrow my computer to compile it. I know of zero reason why the current version cannot be compiled for ARM. So the idea of effort on Matt’s part seems really minor. I suspect it’s just a decision on @Tytel’s part to just move forward with a new version and compile an ARM binary at that time with his machine for all to enjoy. While I don’t agree with the decision, it’s not mine to make. But this is a forum so - you know. Just don’t feed the trolls.
@Tytel, I wouldn’t be hoarding and staring at your code for hours at a time if I didn’t think your work was ace AF. You know that.
You can wait. 
I feel like an absolute ungrateful ass…BIG BIG props to you for forking the OG repo and doing the work to compile an ARM binary for us M1 Mac owners. It runs wonderfully. Thank you friend. Im just gonna stfu about all this, enjoy your ARM native version, and keep up with when the latest build gets posted. Either via you or Matt or whoever else.
Actually the sign in part of the M1 build was the problem in the past (apparently a library he used for that stuff was not compatible with arm at that time)
It’s OK. I was the first to come off like an ass. Looks like there is a beta out there now. Apologies to @Tytel for being impatient and rude. Looking forward to seeing the changes.
2 Likes
Hey, where’d you get my picture? 
No confusion, just think it’s an awkward decision for M1 users: You apparently have the option to build 1.0.X for M1 ARM and are not releasing it yet, in what I can only conclude is just to make more people buy pro. I know we live in a capitalist society and it is your right to do so, but for lack of a nicer word, I think that is a ‘dick move’. That is why I am not buying anything from you again.
If that makes me an ‘angry Apple M1 crybaby’ like @teksonik suggests, so be it.
There is already a 1.51 beta out, that is native on M1 and works great. You can download it even if you are a subscriber, so it will only set you back about $5… otherwise you will have to wait just a little longer
There’s a lot I could say about this.
For the record -
In case it’s not clear, everyone will receive the Apple silicon version once it’s out of early access. Subscribers and pro users can get early access builds, the current early access build runs natively on Apple silicon.
As for my business practice - If I had a “mission statement” it would be to get music software in the hands of as many people as possible. Part of that is making Vital accessible and part of that is supporting the business so there’s more software in the future. That’s why the plugin is free to download and is the same binary across all versions. That’s why there are paid upgrades that come with more presets, wavetables, web services like text-to-wavetable and perks like getting ‘early access’ builds.
If you think that’s too “capitalist” I’m not sure what plugins you could buy instead.
I’m going to close this thread since I have an M1 native build out in early access that will be out to everyone soon.
4 Likes