Page 1 of 1

Keybed and kaos pad not responding after 1.1 update

Posted: Sat Oct 23, 2021 8:42 am
by benjaminrosberg
as the topic descripes my modwave does not register my keybed and kaos pad after updating my new modwave to v.1.1

I can confirm that the update went fine and under utilities it states version 1.1.0

I can play sounds from the virtual keyboard in the editor app and changing knobs physically is register by the editor app.

I wanted to use the "restore boot partition" but it is greyed out in the updater app. When I get the modwave into "usb boot" the updater app is not reconizing the modwave :(

(windows 10 installs another driver "BSCM use BOOT" under device settings. That is not recognized by windows default, just like the UsbNcm Host Device" driver (that I installed manually).....but i dont know what driver I should use under the new "boot" device.

hope the get some help, really wanna play with my new modwave :)

Posted: Sat Oct 23, 2021 12:17 pm
by QuiRobinez
it sounds like that you have your local control set to off on your modwave

to check that:
- press the utility button
- go to the midi & usb page
- the second option says Local Control, this has to be set to On if you want to use the keyboard and the kaos pad.

Posted: Sat Oct 23, 2021 4:01 pm
by benjaminrosberg
OMG :) thank you so much.
Thought I had a faulty modwave.
Im so happy now....thx for you time!!!!

Posted: Sat Oct 30, 2021 5:53 pm
by lys_knight
Dear QuiRobinez 'Approved Merchant' you wouldn't have a miracle solution for the ERROR 4 when trying to use the UPDATER with Modwave/Wavestate and Opsix by chance ?

"Connection Error / Unable to connect to the device <KORGNAMEHERE>1.local. responded with: 'error 4'

Thank you for your time !