I'm rebuilding my beloved axoloti multi-fx setup in a beautiful new 19'' rack format. Gotta make a few changes to the patch to fit with the new controls, but I've run into a fatal problem:
When the axoloti is connected and a patch is live, if I try to change parameters of an object in the patcher with built-in controls my entire system freezes up - mouse pointer gone, no response from keyboard, no bluescreen or error - just total freeze. The axoloti continues to run, controls on the hardware (using analog GPIO) are still responsive, but windows is dead.
At first I thought it might be USB driver issues, as I'm working with a different PC now, but the problem remains on all USB ports and the drivers are up to date (winusb for Axoloti Bulk Interface and for the Core: drmk, ksthunk, portcls, usbaudio, sysxxui and wmalfxgfxdsp).
Patcher claims to be up to date (1.0.12-2-0-g60a2f99), I'm on a 9th gen i5 with Win10 x64.
Has anyone run into this issue or can share advice?
Windows crashing when when using built-in object controls
Never mind, i've found the culprit: a funky audio cable of all things! Noticed it didn't happen when (by accident) there was nothing plugged in the audio in, so I tried and a different cable and boom - problem solved. I assume the broken cable was causing the Core to send some faulty info back via USB to windows somehow.
Or not... after working away merrily for half an hour the problem returned 
And now it just happened without the patch even being live, making me think it's a software bug in the patcher, although I never had this problem on my old PC...
Will give it a go with the version 2.0 patcher.
The audio cable can't cause a problem for patcher or Windows.
Have you tried using a different USB cable?
Tried it with 2 different USB cables, but it still happens. Also tried reinstalling the patcher but this also doesnt help.
It doesnt happen every time now, like it was this morning, but still quite often.
REDDER_001.axp (16.1 KB)
Here it is, but I don't think it has anything to do with the patch.
Yeah it's definately a patcher issue, not the patch itself or USB drivers. Was just messing around with a completely new patch, axoloti not even connected, and the same thing happened.
Thanks for checking it out though!
I don't know much about programming, but I know that the patcher is related to C++. Should I install a different Visual C++ Redistributable on my system?
The patcher isn't related to C++. Patcher is written in Java. The problem could be some subtle problem in the Java Runtime installed on your system, but I don't use Windows, so I have no advice on versions.
I just updated my C++ Redistributable, seemed fixed for a bit, but after a few minutes the problem returned. Now I've reinstalled Java and, for the moment at least, it seems to be gone. We'll see if it sticks.
Axoloti has nothing to do with Visual C++.
I’m surprised no Windows user has jumped in... could we really all be on Mac and/or Linux?
What I would do in your situation is:
Disconnect Axoloti
Uninstall all Axoloti software
Remove core also from Hardware settings
Reinstall everything according to installation instructions and do not connect Axoloti untill you get an message that it is missing.
I've tried several reinstalls now, but to no avail. I didn't want to upgrade to patcher 2.0, since I use a few of the MI clone objects.
I've managed to finish my patch, so for now I'm good, but it took about a hundred crashes to get there and now I have a nervous tick that makes me save every 10 seconds.
I'll just use my old desktop PC next time I'm working on a patch, there I do not have this problem.
Just a thought... How are you powering the axoloti? Usb?
Have you tried it with external power?
Axoloti is USB powered. I've tried it via direct USB and via powered USB hub, but no difference. But I'm quite sure its a software problem with the patcher and has nothing to do with the core, since I've had the same crash also with no axoloti connected at all.