I try to install it with the application Pacifist instead of the installer system
And now it’s work …
strange !
nb : mac only
I uninstalled Vital 1.5.3 and then installed 1.5.5. The same crash happens.
I tried installing 1.5.5 to a computer with Windows10 operating system.
The plugin seemed to work ok. So maybe this has something to do with Windows7 or just my old computer still using Windows7. Where early versions of Vital worked though.
Has anyone got a solution to Vital crashing on GUI screen? @Tytel maybe?
I can’t open it in standalone or as a plug in since updating (had no issues with the older version) Or where can I install the older version? I’m running it on Windows 10 64 bit.
Same issue for me. V 1.0.7 works very well but 1.5.5 doesn’t open.
If you have an issue then provide more information like system specs.
Vital 1.5.5 opens and works just fine on two different systems and five different DAWs here including this system which is my internet computer, an ancient i5 3470. Both systems run Win 10 21H2.
There were significant graphics changes between 1.0.8 and 1.5.5 so something to do with those changes is affecting some systems and not others.
The more information you can give the better the chances the cause of the crashes can be identified.
1 Like
It seems that from Sep’22 there are people with the same problem, Vitality crash opening Standalone or as VST. I think everyone of them with their OS (Mac,Windows,Linux…), their Processor, Graphics card, DAW, etc. and all of them doesn’t have problems with the older 1.0.7/8 version. Perhaps Vital was made with an OS and computer specific and it isn’t plenty tested.
My system is:
Windows 10 Home
Intel Quad core 2.40 GHz, RAM 8Gb
DAW Reaper V6.73
Graphics card NVidia GT 630, 2GB video RAM
Open GL 4.6
Audio Asio
I hope somebody can solve this problem and give a solution.
Hi, what i think we should do here is cross reference the systems that work and the systems that dont so people can identify…then its a process of elimintaion…evidence points at it being a graphics issue for some,not by my pc right now but ill upload my spec when i can…gotta find a solution to this as i love this synth…big ups Matt !!
Vital is crashes on my setup too.
I use flatpak version of Bitwig studio 4.4.6
There is a reason why some systems have issues with 1.5.5 and some don’t. It’s all the same code in Vital so the problem lies with either systems specs, OS, or with certain DAWs.
Like I said 1.5.5 works just fine on two systems here, one of which has onboard Intel graphics and the other with an Nvidia GTX 1050ti card, both running Win 10 21H2 and both with Intel CPUs.
Whenever anyone reports an issue (with any software) we need the weigh the number of people who report the same issue against the number of people who do not report the same issue.
The fewer people who report it usually means the more obscure the issue/bug is and I can say that as someone who has been a private beta tester for a lot of plugins.
Perhaps the people who have reported the issue are using some odd system scaling or dual monitors etc.
As you say if people submit their system specs a pattern can be established and the cause of the issue might become clear.
Ok that helps. For the record my internet system has Intel HD Graphics 2500 and Vital works fine here. (1920x1080).
Look likes the installed drivers are pretty much the same.
What does it show when you run dxdiag?
I HAD the same (or similar) problem. I could run multiple instances of Vital, but could only have one displayed. As soon as I opened another existing instance, Reaper crashed. I checked that Vital was using my GPU, which it was. (It showed “Reaper/Vital app using GPU”).
I have a 5 year old i7 Windows 10 laptop with an Nvidia 960 GPU.
So I figured maybe my GPU was too old. (It’s not supported by GPU AUDIO, so their effect vsts don’t work on my laptop).
BUT… I just updated my Nvidia GeForce driver (which I hadn’t done for ages because I forgot my login details), and Boom…
I now have 4 tracks of Vital on screen, with the song playing, and all Vital displays displaying all the moving modulations etc.
It’s beautiful to watch.
I shall go to bed happy!!!
1 Like
I also have an issue with multiple VST3 Vital in Live 11.2 - can’t have more than 4 windows open at the same time. If I open any more, then the last one I open looks like this:
When that happens I can’t resume song playback and have to quickly close all of them, and save the project because if I don’t, Ableton will crash immediately when I’ll play anything. It will still randomly crash while opening the GUI, so it’s safer to just reload the project. The VST2 version seems to be working fine, but I haven’t tested it too much.
My specs are:
Windows 11 Pro
Ableton Live 11.2
AMD Ryzen 5900x
Nvidia RTX 3070Ti 12GB
32GB RAM
NI Komplete Audio 6
1440p180hz and 1080p165hz monitors
As a workaround for now can you avoid the issue by only having one plugin’s GUI open at a time?
If you load say six instances of Vital but only have the GUI of the latest one visible does it still have the same issue?
Try in an empty project so you don’t lose any work and just load one after the other and keep the GUIs open. Does the forth or fifth one show as in your screenshot above but the 6th 7th 8th etc load just fine?
I have dozens in my project files, as this pretty much is the only synthesizer I use, and all of the Vital instances work fine, even within a project that has literally 50 of them. The problem just appears after I have multiple GUIs open, so I’m just gonna have to remember to close them as I go until an update drops.
That was my point above. Until (if) an update is released the workaround would be to only have one GUI open at a time.
It would have been nice if you had run the test I suggested above because that would help provide some clues to Matt should he choose to address and seek a fix for your issue.
Just tested that and only the 4th window is broken, doesn’t matter which one of the ones I have in the project gets opened as the 4th. Other Vitals opened after that do work (at least visually).
Also I noticed that the broken GUI is still fully interactable.
1 Like
Thank you, that’s what I’m getting here in FL Studio. Only the 4th one is broken and all others before it and after it are fine.
So that’s got to be a clue for Matt. Why only the 4th one? Why not the 6th or 8th or for that matter the 2nd or 3rd ?
Anyway the more info we provide to Matt will only help him find the cause and cure.