Same here running Ableton 10 suite on Mac OS 10.15.6 with 0 issues and it runs more efficient than most Ableton stock plugins.
I run in to the same issues as this post. Primarily that I can never log in, it just gives me “signing in…” and nothing. When I click past the little login box it lets me use Vital as normal but I cant access TTW. It will also crash for me randomly. I have been sounding desiging in blank projects with only one channel to try to minimize other plugins/ cpu and it will still happen randomly. Had it happen twice last night over the course of 3 hours. Both times when I was moving around a parameter relatively quickly to see its effect and if I liked that movement.
I have a 2017 Macbook Pro running Mojave version 10.14.6 running ableton live 10.1. Using an external monitor and have norton installed.
Another thing on the external monitor that is minor. When I move ableton to that screen and I open vital occasionally I will only be seeing the bottom left corner of vital where the filters are taking up the whole plugin screen and the text will all be enlarged. Typically I exit out of it and open it back up and that problem resolves. I also can not make the plug in bigger which is quite frustrating
GOOD NEWS EVERYONE
I have fixed my issues, and I believe this will fix many other Mac users issues.
It has to do with the firewall in OSX. I discovered this when another plugin I bought couldn’t perform it’s authorization in Ableton, but was able to do so in Logic (same as Vital minus the UI lockup). It was quite an easy fix, though.
- Go to System Preferences > Security & Privacy > Firewall
- Unlock to make changes (enter admin pw)
- Click “Firewall Options”
- On the next screen, click the plus “+” and select the Ableton Live app from Applications
- Make sure it says “Allow Incoming Connections”, click OK
- Lock back up to prevent changes
I thought simply turning the firewall off would accomplish the same thing, but it doesn’t. You need to tell OSX to let Ableton (and the plugins its hosting) to talk to the interwebz. Have not tried this in Bitwig yet, but I suspect it will work.
Would love if some of y’all could give this a shot and see if it works. If it does, I bet we could save Matt a ton of work replying to messages, etc. Maybe pin these instructions somewhere?
Happy this monster is breathing now!
1 Like
Ryan I’ve just tried this and unfortunately it still doesn’t work for me. Thanks for the info though!
I had my firewall off, just tried this. Will report back after using it if I get any random crashes still
bobbs, do you happen to own Logic Pro X? I am wondering if maybe me having successfully run the app in one DAW first may have something to do with it? Also and if not, try opening the standalone during the firewall procedure and while opening it in Live. There is absolutely no science behind this idea mind you, I am literally throwing things at the wall to see if anything sticks.
Also, you mention the VST in Ableton. Have you tried the AU?
I don’t have Logic no, only Ableton. Just tried the AU and that also froze Ableton. Also tried having the standalone open while launching Ableton and also while doing the firewall thing. I guess I’m unlucky!
dang, that is rough my dude. sorry I couldn’t be of more help. I didn’t really expect mine to work without a new version from Matt, so maybe I just got lucky. I can promise you it will be worth whatever wait you have to put in. tbh it started crashing on me again, I would run the standalone and make mudpies out of it (long recordings of tweaking sessions to chop up later) because I like it that much. the sound of these wavetable sweeps is priceless!
Same issue here. MacBook Pro 2019. macOS 10.15.6 / Ableton Live 11 Beta 11.0b19
Tried the firewall, made no difference. Tried launching the standalone first, no change.
What DID fix it, was turning off WiFI and leaving my machine with no connectivity while trying to load the plugin.
I’m connected via ethernet…I wonder if that could be some sort of issue?
Hey Tytel - any solution on the email login issue ?
I have the same issue on my windows, my specs are intel core i7, 16GB ram, 500GB SSD, I’m also running windows 10, and since the 1st day that I installed vital it was crashing every time I closed Vital, freeze the track or try to switch vital out for another vst, basically, I’ve vital is on a midi channel there’s no way to get it out there since trying to delete it will crash my Ableton and well I cant freeze it. Also, suck that I think Vital is super dope, I love sound design with all my heart and soul but I’m definitely not using vital until there’s a new version, it’s not worth all the crashes.
I have tried repeatedly to use with Ableton Live 10 Suite as a VST3 plug-in. It just hangs Ableton, and cannot be used.
System specs are:
OS: Windows 10 (10.0.19041)
Make: Alienware
Model: Area51m
CPU: i9-9900K
RAM: 64GB
GPU: nVidia GeForce RTX 2080
App: Ableton Live 10 Suite (full license)
Repro Steps:
- Launch Ableton Live 10 Suite
- Select “Plug-Ins” from left navigation
- Expand VST3 category
- Drag “Vital” to Midi From (1)
- Control surface opens with frosted dialog (white) with title “Vital/1-Vital”
- Ableton Live 10 Suite shows “Not responding” in Task Manager
At this point, I have to forcibly end the Ableton Live 10 Suite.exe process. I don’t see a way to share a file, but I do have the Able Live 10 crash report (zip file), and I’m happy to share it.
I can also capture a memory dump for you, so please feel free to reach out directly to me. I’m willing to help you with any in depth debugging detail. You’ve done really nice work with this app, it seems a shame to see the VST3 issues blocking full enjoyment of Vital.
Thank You,
Paul
Not sure what changed but Vital AU and VST no longer work in Ableton. I have not updated the app, DAW or computer since posting my fix so I assume something has changed on the back/server end.
I really wish there was a way to run the plugin offline / locally. This whole having to connect to the internet thing is honestly kind of annoying. I would be willing to pay extra to be able to use this thing reliably. As it stands I now have several project files that are unusable because I used Vital as the main synth.
For real though. Pro users shouldn’t have to deal with this.
In the latest version you can work offline. Just logout and click ‘Work offline’. In that setting it doesn’t attempt any web connections. You can get it at https://account.vital.audio
Also, what do you mean it doesn’t work at all? Does it launch at all? It’s possible that when I updated my mac build server it invalidated the old code signature, but I thought it would still function if you had been using it.
I was getting a plugin screen hanging in Live 10, Windows 64 bit. Turns out I had changed my password on the account. After I logged in again plugin loads fine (1.05). Probably just need a timeout handler for the firebase auth stuff so it doesn’t white screen like that. Thanks for a great product!
The hang issues on opening in ableton are fixed (as well as the ‘Work Offline’ option) are in the latest version at https://account.vital.audio
Could you try that out? Also @paulwimmer
Hi Matt,
It seemed to work better: I could not open Vital GUI without freezing Ableton 11 in OSX 10.15.7.
I updated to Viatl to latest version and i could open the GUI and no edit, but when i close the GUI Ableton freezes. This is super annoying!
I have used Viatl a lot it has been working, but now it itseems to crash Ableton all the time. This one is a new project where i have vital preloaded. I can edit it via pre mapped macros but using the GUI freezes Ableton. Ican’t add another instance of Vital as i can use the GUI.
I have heard that there is a problem in OSX 10.15 with plugin GUIs. But no other plugin GUI crashes my Ableton like Vital does.
I can still mix my on going projects as long as i don’t open the GUI, but i hope this get fixed at somepoint. I really donät want to update my OS to Big Sur.
And yes, it is a system specific as it works for some others. But it is still a Viatl issue as it is only plugin that keeps Crashing Live 11.
@Tytel can i send you my crashing Ableton project if that would help?
Have you tried setting it to “Work Offline”?
If that fixes your issue let me know, if not let me know what plugin version you’re using (AU/VST/VST3).
Sorry, didn’t know about Work Offline option. For now it seems to work. But i’m a subscriber so then i don’t get updates. I use AU on Live.