201,452 users have contributed to 43,248 threads and 259,287 posts.
In the past 24 hours, we have 3 new thread(s), 23 new post(s) and 65 new user(s).
Anyone else running into this issue? After updating to version 1.2.461, VA keeps going unresponsive, and all my installed libraries suddenly show up as “Not installed.”
Every time I try to reinstall or select “add existing library,” it just freezes and stops responding. I’ve tried restarting a few times, but it’s still happening.
Anyone know how to fix this? It’s making it impossible to get anything done…
This issue still persists in the latest 1.2.483 version on macOS 15.2. I believe the problem lies with the VSLHelper utility, which appears incompatible with macOS 15.2 and later versions. Whenever you install a new library or add an existing library, it triggers the VSLHelper utility, causing the software to freeze.
When I try to install each library, I manually delete /Library/LaunchDaemons/at.co.vsl.viennaassistant.helpertool.plist every time. This allows me to complete the installation process. However, once I reopen Vienna Assistant, all libraries are still marked as "Not installed," even though I can use them in Synchron Player.
I have several things now that VA believes aren't installed. I know which ones they are, and have decided it isn't worth caring about.
The thing doesn't have to get this right, If they work, they work and that's all I need. I learned today that here, add existing libraries only works if the top directory is selected, select an individual folder for a library and it is sure to hang. And it's a brutal hang, force quit doesn't, causing me to shut down from the power button. Moving libraries around isn't easy. Delete one and you have to go to "Products" and delete the json file or it's Catch 22.
and now selecting the top directory always hangs. So NOTHING can be moved as nothing can be recognized by VA, everything has to be downloaded, meaning hours of time wasted. It's also really tedious to find the json among hundreds to delete so it doesn't do "cannot be located" in every case. This is a really sorry state of affairs that just got worse.
fortunately uninstalling VA fixed that last SNAFU. IME this has to be done quite frequently.
