I see why you might think there’s no development activity because I don’t push changes to the public repo. Maybe I should make a note of that on the public repo that I have a separate private repo where I push all development changes.
About M1 compatibility -
As you can probably tell I planned to have an M1 out by now. Life got in the way a bit and that hasn’t happened yet.
That said, I do have an M1 build out in early testers hands (along with the extra features). When it’s ready to send out I’ll make a post here.
I’m sorry to hear that you’ve had to deal with some personal stuff that got in the way of Vital’s development but I’m also glad to hear that you’re still working hard on the next Vital update!
Hi just wanted to add, I absolutely love Vital (after discovering it a couple of weeks ago in a debate about the Waldorf Iridium - blows that out of the water in terms of sound and interface IMO), so I bought the Pro version straight away. Im nervous now, as I have a Mac Studio about to arrive that I plan to run in Logic X optimised for M1 etc (my other plugs are now supported). I’m hooked on Vital now, and don’t want to run Rossetta just for one plugin. Please update your code ! Love your work on this but can I suggest you give users a estimated timeline so we can plan accordingly ?
Just wanted to chime in here that NVIDIASC’s shared VitalM1 package is working beautifully on my M1 Pro MacBook. I haven’t measured the precise performance improvements but the increase in speed is VERY noticeable. I can now see myself using Vital as my primary synth. Thanks for sharing NVIDIASC
There’s a private beta that is native on M1 along with a few new features. When it’s ready I’m going to make it available to Pro users and subscribers.
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.
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.
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.
