I can’t open the Standalone version on windows, when you try to open it it closes quickly.
It happens the same to me too
I have not been able to use the standalone version (Windows 10) from the start. I just downloaded v1.0.5 to see if might work now, but no luck. It begins to load but crashes before the window can even really display anything. In the Task Manager it switches from Apps to Background processes and holds onto about 350MB of RAM while using 0% CPU for at least a few minutes. While it’s in this state it holds on to my MIDI keyboard and won’t let go. End Task takes a few minutes.
Does Vital now have some error logging that might point to what’s going wrong?
what happens when you try it whitout the keyboard?
sorry no help, just curious.
Thanks for the suggestion. It crashes and sticks in the Task Manager for a very long time, but it doesn’t hold on to the MIDI keyboard.
There must be something specific to my system that Vital standalone doesn’t like. Oh well. The VST works fine. That’s far more important.
it seems if you use onboard graphics causes some issues. (if your system is like this try update drivers, maybe cpu is blocked with graphic task that it can´t do)
and with graphic card it still uses more cpu in standalone.
or just use vst.
- Exact same behavior here, minus the MIDI keyboard issue. No hangup for my MIDI…
- Windows 10 Pro, all updated
- Integrated video GPU and CPU (old i7-2600K), all latest drivers from Intel
Tried giving rights to the .exe admin and other rights, no luck.
Works fine as VST and VST3 in Cubase 11 and Blue Cat.
- VST does not update automatically or gives any signal. I was at Vital 1.0.3 and downloaded manually and installed 1.0.7. Nothing changed regarding my previous issue.
Mike from Sweden
I have the same exact issue
Regarding issue 1. Older machines with Windows 10 with Intel onboard GPU, does NOT support higher versions than OpenGL 1.1 and Vital needs OpenGL 3 or higher to work as standalone.
There is (of course) workarounds like this one… :workaround-link …but I will, personally, be content with no standalone version until I get a newer machine.
To be clear, I have NOT tested the suggested workaround in the linked content above.