I have to close Ableton and do a full reboot of my controller to get Kilowhat to recognize my controller… It recognizes my push always, no problem… Kilowhat doesn’t see my Keystep, but disables access to my keystep while it’s open. (denoted by the red)
I am using Chromium, but it’s just Chrome without all the Google crap… On Win10
Steps to reproduce:
1. Start with Ableton open, load Kilowhat in a browser
Note: it recognizes the push, but not my controller or keystep. (not sure if I expect it to recognize the keystep… I wouldn’t expect it to recognize the push yet it does… which would make me think it enumerates all the MIDI devices it finds…)
2. Close Ableton, click “refresh ports”, nothing happens.
3. Unplug the USB port while leaving DC/constant power plugged in, then click refresh, I’m able to select my device in the preferences:
(hmm… it was selected but then it crashed my browser… stay tuned, I’ll get a screen shot)
The popup for where to load the config doesn’t pop up… and when I try to load the config from the device I get an error:
“Could not get device BLOCK 0 to load config”
Actually, sometimes unplugging USB and replugging USB kills Kilowhat and chromium. I use Firefox as my primary browser so fortunately didn’t lose this post!
4. After all of the Above, if I close Ableton, pull the power and USB cable, then plug them back in, I’m able to get Kilowhat working.
EDIT: oh, and when I say it kills Chromium… that’s only sort of correct, because it leaves–whatever the windows version of zombie processes are–running until I unplug the controller. So the UI is closed, but it’s “open” in the background and I can’t start it again until I unplug the controller.
EDIT 2: I think it would be really nice to be able to have Kilowhat and Ableton open at the same time… Maybe there’s reasons that’s not possible? It would be nice to have that/a “workflow” documented somewhere? (maybe it already is?) “Make your changes, push the push and reset button, then close the browser and open your DAW”
I think regardless, there should be “safeguards” to prevent “lockups” (e.g.: detect the controller is in use elsewhere and give the user a message “hey, we can’t do anything until Ableton/“Another Program” gives up control”).
It would be really really nice to have an easy way to transition… I’m working in the app and send the changes to my controller, start my daw, wait for it to load, realize I made a mistake then… have to close the daw, reopen the app… Maybe there could be a “disconnect” or “reset” button in Kilowhat?