Korg Forums

..yep, still same here. Updated wavestate. All new korg software on PC. Set up both network drivers, software is just saying "waiting for device". I can see the wavestate using ssh (i.e, I get the login prompt, I obviously don't know the login credentials), so the network connection seems to work ...

I have the same issue with one PC, but another one worked. No idea why. Worked earlier. Have tried rebooting. The network connection clearly works (I can try to ssh to the wavestate, for example), but neither updater nor librarian sees the device.

From a quick glance all the files seem to follow some structured binary format, but I don't recognize it as any standard format that I know of.

I think reverse engineering the formats should be a relatively straightforward (if tedious) job.

It doesn't transfer samples *yet*. Wait, do you know something I don't? Will it be possible to transfer user samples to the Wavestate? :roll: I don't know anything you don't. There's no physical limitation that would stop user samples. The synth even says when booting that it's loading samples to ...

Bozzy wrote:As for the assumption, the librarian doesn't transfer samples, it only transfers "patch" data (which can be quite big anyway, considering the amount of parameters each performance can have).

It doesn't transfer samples *yet*.

Just so I'm clear, Is it just the Librarian and firmware updates that are affected by this, or is it Midi over USB? (New owner - Black Friday Purchase!) :) As far as I know the midi over usb should work, as it uses a different interface (haven't tried, though); the firmware updates and librarian ...

Okay, either it was the updates or the fact I unplugged and inserted the usb cable, but librarian seems to work under the VM now.

If you'll use VirtualBox, please also install the Extension Pack and configure the VM to support USB 2.0, we need it to run the updater (at least I think so... maybe it'll work also with USB 1.1, but it'll be veeery slow). Well, it at least doesn't work without the extension pack, the driver won't ...

So - forgive my ignorance - I have never come across RNDIS before and maybe by coincidence have never had this kind of issue with usb on ANY OTHER device before. Would it be possible to get the wavestate to work in a more standard way over usb? is that possible? One where you don't have to go ...

Windows 10 version 20H2 does not fix the issue.

Does a specification of the wsperf file format exist somewhere, so that a third party could make an editor for it?

Not that there's any hurry considering we can't even connect to the synth from windows at the moment..

Started playing around with my new wavestate and hit this exact problem. Unfortunately I've already updated the windows machines in this house to version 2004 so no luck there. I've also sent queries around and general answer is that there's no official answer at this time. I'd be curious to know ...