December 15, I used Vital (standalone) on my Ubuntu Studio 18.04 machine in a class – perfect. Everything worked fantastic. The kids were really impressed.
Today, when I run the standalone, it displays the GUI but is completely unresponsive after that. Even the close-window button doesn’t do anything.
Today, I also tried it using the vstplugin~ external for Pure Data. This can open a generic editor with sliders for parameters (limited usability), but the native Vital GUI likewise fails to load.
According to /var/log/apt/history.log, the last time any software was updated on my system was December 14, one day before the successful demo in class. If the log is to be believed, nothing has changed since then… but, now Vital isn’t working.
OK… after a reboot, I think I see what it is. While launching Vital, I also opened the network monitor. Vital hangs at the moment of accessing the network. (In the classroom, there was no network connection – so the network attempt failed immediately and I could use Vital. At home, the network attempt didn’t fail immediately, but didn’t succeed either.)
I’m in mainland China, by the way.
After several minutes, it finally gave up and now the interface is working. But nobody would/should accept multiple minutes of delay when opening a plug-in, no matter where they live.
If the program is checking for updated content, this could be done upon user request. It’s OK to check automatically, but please time out within 5 seconds (and perhaps put up a message somewhere advising the user that there might be available updates but that automatic checking failed).
Vital is generally fantastic, but its current networking usage is a near-total impediment to adoption in some parts of the world. The network requirement really needs to be made optional. I’d love to promote it to my students but they will simply not bother after it hangs once like this.