Hardware Wavestate problem

[cs759]

Hi,

I am going around in circles with this problem. It's been a month now.
Korg UK Support concluded that my first Wavestate was faulty as it should not say usb audio device. Their suggestion was that I should return it.

I've just received a replacement wavestate (but they said they could not find a problem).

But I have exactly the same problem again.


This is what's just happened today (the same thing as for the first unit).

Initially the Wavestate was at version 1.0.5 and RNDIS

I ran the 210 updater, stopped before running the firmware updater.
I configured the Network Adapter RNDIS device in device manager.
The Wavestate Editor connected successfully.

Then I ran 210 firmware updater.
Now in Device Manager "Sound, Video and Game Controllers", I have "USB Audio device" with a yellow exclamation mark.

MIDI does not work.
Doing "Properties" on the "USB Audio device" gives "This device cannot start. (Code 10)"


I don't understand what I could have done wrong.
I have a modwave, and that all works fine, editor and midi.


Hopefully someone can help,

Best,
Rod


I should add, that I've tried all the different usb cables ports. uninstalling, not using a hub etc (using the same cable port that the modwave works with).

I've tried it on 3 computers, all with the same result, Device Manager "Sound, Video and Game Controllers", I have "USB Audio device" with a yellow exclamation mark.


I'm on Windows 11, Cubase 12, Reaper 6, Scan Computers FZ370 (i7, 32GB)

[cs759]

I've given up with this and sent it back for a refund.

[pplastic]

This is exactly what happens to me and my Wavestate.

I've tried every fix under the Sun but nothing works.

USB does work though with my Akai MPC One, and with the editor so I cant figure if its a problem with the Wavestate or Windows (even though I've tried different PC's and its the same).

I love it so much though I am just having to work around it using a comb on USB midi and the MPC One and MIDI DIN on the Soundcard when I use my PC.

I've posted on the forum about it before but I don't think anyone knows how to fix this.

[pplastic]

SleepIsWrong found a fix:

http://www.korgforums.com/forum/phpBB2/ ... p?t=126974

Revert to 2.01 then back up and it seems to fix it.

[cs759]

I saw that, but I did not have a way to, or know how to revert to 2.01

I just got completely fed up with the idea and sent it back.

I'll just stick to using the Native version and save myself £500.