Hi all,
I started V2 again for a change and it got stuck while getting to the step of loading VST instruments 64 Bit (as the program mentions).
Before that I picked the Midi ins and outs and it started loading "stuff" (I saw Asio drivers mentioned). When it came to
Loading.
VST3 Insruments 64 Bit
It sort of froze. While I gave V2 time to load all plugins of which there are plenty it did not seem to come to a natural end. The program behaves very stubborn in this state an does not allow for tast switching in the operating system. Even the tasks manager does not manage to get in front to kill the task of vArranger2. Annoying.
I think I have the most current 1.16 version that was available.
How could a trouble shoot might look like under these circumstances?
Thanks for your wellcome tipps.
Cheers Stefan
Hello Dan, colleagues
I am at a loss as vArranger2 is not booting.
Is my description before unsufficient for a hint as to get vA2 running through the full boot routine?
If I can provide more information from the little visual representation I get, let me know. Maybe a short video of my monitor?
In my opinion everything I did was no change to previous program launches.
Is there a log file, that shows more details where the booting is interrupted/hanging.
Thanks for advice.
Cheers and Merry Christmas
Stefan
Hello Stefan
I would try backing up the "vArrangerData\vArranger2.ini" file by moving it somewhere else.
If vArranger can't find this file, it should reset itself to its default state.
You will need to reset everything again, but this should fix the startup issue.
Cheers
Vaclav
Hi Vaclav,
unfortunately no different outcome after renaming the ini file.
vA2 is still hanging up on loading VST instruments 64 Bit.
In task manager I also see no consumption of CPU time while it seems "hung up" in the process. Possibly there might be individual VSTs not on the same spot - but I would expect some other meaningful error message, if these issues cannot be skipped.
Any more ideas?
Need I reinstall?
Cheers Stefan
You can try to move all the vst3 files from the C:\Program Files\Common Files\VST3 folder
And see if it works
It is easier to rename the VST3 Ordner to VST and then VA2 should boot.
Then, you can put back every vst3 file, until you find the one that is doing problems
Not much fun with 100+ vsts in this folder :-(.
There is no logging possibility to find the culprit?
TIA
Stefan
Will add a log in a future version
For now, you can remove half of the VST, to find faster, then half of the half etc...