Korg Forums

When I try to run the latest updater 1.0.4 or even the Librarian, the message I get is Waiting for Device...

I've tried several different USB cables and several different USB dongles (My MacBook Pro has Thunderbolt ports, not USB). Is the software just not ready for prime time?

Well there is no editor for the Wavestate yet.

There is the System Updater for 1.0.4
The Librarian is at 1.0.1.

You haven't mentioned what OS you are on, but Korg does not support Big Sur yet.

For the Wavestate, Big Sur software compatibility is listed as "under consideration".

I am having this same issue. I don't understand why Korg can't address this... I have tried to update my Wavestate on two different computers, two different Mac OS's and two different USB cables and it WILL NOT SEE THE WAVESTATE!!! This is a known issue and they don't seem to care! If we cant do something as simple as updating the firmware what is the point? I'm so frustrated that I think I'm going to return the Wavestate. This shouldn't be a hard thing to do in 2021 with a modern flagship synth!

i fixed my Wavestate librarian/computer issues since Korg would not = sold it

i fixed my Wavestate librarian/computer issues since Korg would not = sold it

The wavestate as it stands on it’s own, without the librarian, and without the forthcoming editor is still a truly amazing instrument at an unbelievable price. I fear you maybe sorry you sold it in time. I know I wouldn't dreaming of selling it.

Regards
Sharp.

It's PITA for Korg and any vendor to keep up with what Apple and MS are up to these days.

And then Apple changes from Intel and every piece of code and library, some probably purchased like cross platform stuff, need to be recompiled for ARM processor. And tested as well.

I have been looking at alternatives for pc for the time that my windows 7 computer dies. Never had updater issues with Windows 7 either. Korg midi drivers been so so, but worked if I uninstalled it with KingKorg.

Think I found my pc replacement today Akai MPC X. Full featured recording unit to my needs. If 4 midi ports are not enough, just connect class compliant midi interface. Quad core ARM processor 1.8 GHz. Slot for extra hdd or ssd. 128 midi tracks and 8 audio simultaneously, but bounce, overdub, automation and everything is there. And 10.5" tilted touch screen like Oasis had.

Problems are all this fear driven crap "keep your computer safe" that create the problems IMO.

Probability to really have any issues is more like winning the lottery, get killed crossing the street or something. Just normal caution and everybody is fine. I tried anti-stuff and they cause more issues than any virus - so never kept them above trial period, usually uninstalled within hours. In 35 years never had to use it.

But fear-industry is huge market....so we have a choice to run along...or not....

I bought a windows 10 laptop to test and see if I can control it. Using Sledgehammer I had no updates in 90 days now. If that lasts another year I might consider getting a windows 10 daw computer. But think I will get aquainted with this MPC X in the meantime.

Hi all - we've released wavestate software 1.0.6, with support for macOS Big Sur and NCM networking. Please read the included documentation for step-by-step instructions!
Mac download here: https://www.korg.com/us/support/downloa ... /840/4518/

davc wrote:i fixed my Wavestate librarian/computer issues since Korg would not = sold it

...and now bite your fingers

First post here. Looking for info about the Wavestate updates.

I have the 1.04 in mine right now. If I install the 1.06 will I be able to use the librarian to manage presets?

Right now it's not working. (Mac 11 big sur, latest update).


I'd really want to be able to manage my presets, as well as to load new ones on it.

Thanks,

Librarian works great for me after 1.06 update.

ob1bazillion wrote:Librarian works great for me after 1.06 update.

Thanks!

Just updated to 1.06. Librarian NOT working.

synthM111 wrote:Just updated to 1.06. Librarian NOT working.

Did you switch the wavestate to use NCM?

It worked with the change to NCM,

thank you!