WaveState Update - Is Sucking my will to live

[danatkorg]

I completely agree ! What I am most worried about is the fact that nothing is moving at Korg it seems. They don't publish any explanation, timeline, whatever to see that they are on the connection issues and it will be solved some time in the future. When I checked their Compatibility Chart this week I could see an incredibly long list of issues that are under investigation for different Windows 10 versions and for Windows 11 (?) for many Korg instruments...

My impression is that "under investigation" is the default entry in the "Compatibility Chart."

I'd like to emphasize that there are no known issues with the network communications on the wavestate. Most reported issues have been resolved by closely following the installation instructions and, where necessary, troubleshooting steps. (I absolutely agree that it would be better if less manual setup was necessary on Windows, btw.) A few Windows users have had to reconfigure Bonjour. Back when we were using RNDIS on the Mac, we had one user who had an old version of RNDIS installed; removing that solved the problem. The other handful of problems have been related to networking in general. For example, two users on Frontier internet providers in the USA have had difficulties with an obscure DNS setting - which we know about because it causes issues with non-Korg products as well.

Regardless of the cause of the problem, the first thing to do when you need help with any Korg product is to contact your national Korg distributor, such as Korg USA, Korg UK, etc. - for a full list, see https://www.korg.com/us/corporate/distributors/ . They will be happy to help! Forums can be extremely helpful, but it can also be difficult to use them for detailed one-on-one support.

[DungBeatle]

Coming back to the Wavestate.. I'd love to know why Bonjour was deemed necessary to write a firmware updater.

An alternative would be for the user to manually enter an IP address, which would have its own points of failure.

Excuse my ignorance of USB protocol internals, but surely USB does not entertain the concept of an IP address? I've designed and implemented a number of custom protocols on top of the TCP/IP stack.. there users may have to be exposed to IP addresses.. but USB?

Fortunately, very few people have had trouble with Bonjour on the wavestate - which makes sense, as it is an industry standard mechanism. Those were only on Windows;

.. as in only on the most popular OS in the world? Call me critical, but the use of the expression "only on" doesn't seem appropriate.

I'm not aware of a single issue with Bonjour on the Mac, since it's a fundamental part of Mac networking, though I'm always happy to be corrected. The bigger difficulty appears to be in getting through the steps required for Windows network setup, and I'd like to make that easier.

The logic of my argument is that Korg should first have investigated the risks of imposing Bonjour dependencies on your Windows customers before giving the green light to develop an updater that relies on this technology on all supported platforms (e.g. Windows and Mac).

I would still appreciate reading why Bonjour was such an absolute must. Just saying it's an industry standard doesn't cut it for me. There are tons of industry standards that could remotely find a use in an electronic music context.. that doesn't mean there are really solid reasons to use all of these industry standards. So, without wanting to be too pushy here: what exactly within Bonjour made it so unresistable to your (otherwise undeniably clever) software engineers?

[danatkorg]

Coming back to the Wavestate.. I'd love to know why Bonjour was deemed necessary to write a firmware updater.

An alternative would be for the user to manually enter an IP address, which would have its own points of failure.

Excuse my ignorance of USB protocol internals, but surely USB does not entertain the concept of an IP address? I've designed and implemented a number of custom protocols on top of the TCP/IP stack.. there users may have to be exposed to IP addresses.. but USB?

The wavestate communicates using networking (TCP/IP) over USB. Have you had a chance to read the documentation which accompanied the updater? At the top of the first page, there's this section:

* * *
What’s installed on my computer, and why?

The Updater communicates with the wavestate using networking over USB, as opposed to MIDI. To automatically identify and connect with the wavestate over the network, the Updater uses the mDNS standard. On Windows, this requires Apple Inc.’s Bonjour, which is installed along with the wavestate Updater application.
* * *

As an engineer, you might be interested in this overview:

https://en.wikipedia.org/wiki/Ethernet_over_USB

Fortunately, very few people have had trouble with Bonjour on the wavestate - which makes sense, as it is an industry standard mechanism. Those were only on Windows;

.. as in only on the most popular OS in the world? Call me critical, but the use of the expression "only on" doesn't seem appropriate.

You noted that you were on a Mac, and were complaining about use of Bonjour - hence my response.

I'm not aware of a single issue with Bonjour on the Mac, since it's a fundamental part of Mac networking, though I'm always happy to be corrected. The bigger difficulty appears to be in getting through the steps required for Windows network setup, and I'd like to make that easier.

The logic of my argument is that Korg should first have investigated the risks of imposing Bonjour dependencies on your Windows customers before giving the green light to develop an updater that relies on this technology on all supported platforms (e.g. Windows and Mac).

As I mentioned above, zero-config (aka Bonjour) has not proven to be a significant issue - certainly no more so than any other aspect of network configuration. Not surprising, since zero-config is a mature and widely-used technology.

I would still appreciate reading why Bonjour was such an absolute must.

As I mentioned above, the alternative would have been for the user to manually enter an IP address. I didn't write that it was an "absolute must," but in general it makes connection much simpler.

[jb58]

I completely agree ! What I am most worried about is the fact that nothing is moving at Korg it seems. They don't publish any explanation, timeline, whatever to see that they are on the connection issues and it will be solved some time in the future. When I checked their Compatibility Chart this week I could see an incredibly long list of issues that are under investigation for different Windows 10 versions and for Windows 11 (?) for many Korg instruments...

My impression is that "under investigation" is the default entry in the "Compatibility Chart."

I'd like to emphasize that there are no known issues with the network communications on the wavestate. Most reported issues have been resolved by closely following the installation instructions and, where necessary, troubleshooting steps. (I absolutely agree that it would be better if less manual setup was necessary on Windows, btw.) A few Windows users have had to reconfigure Bonjour. Back when we were using RNDIS on the Mac, we had one user who had an old version of RNDIS installed; removing that solved the problem. The other handful of problems have been related to networking in general. For example, two users on Frontier internet providers in the USA have had difficulties with an obscure DNS setting - which we know about because it causes issues with non-Korg products as well.

Regardless of the cause of the problem, the first thing to do when you need help with any Korg product is to contact your national Korg distributor, such as Korg USA, Korg UK, etc. - for a full list, see https://www.korg.com/us/corporate/distributors/ . They will be happy to help! Forums can be extremely helpful, but it can also be difficult to use them for detailed one-on-one support.

Hi Dan,

I really appreciate your presence on this forum, and I am also not here for long discussions. What well intrigues me why can I not make the connection work with 20 years of IT experience ?? To begin with, my Wavestate never appears now in my Bonjour browser since august 2021, whatever I remove/purge/reinstall. So I don't even try with the editor.
I have done the installation process more than 10 times, on 3 different Windows 10 laptops, recently also on a Windows 11 laptop. On two of the laptops was no Korg software installed before.
Believe me, once or twice I could maybe miss something from the instructions, but not 10 times. My Wavestate is on v2, I could only do the upgrade in USB boot mode. My laptops are either on Windows 10 20h2 or on Windows 11.

Btw: could you please elaborate what do you mean by reconfiguring Bonjour service ? I don't see such an option in Windows 10/11.


Best regards,
Janos

[jb58]

See my recent post here:

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

Antivirus software was the bottleneck in my case, now I could connect my Wavestate on two different Windows 11 laptops .

[danatkorg]

Hi Janos,

I really appreciate your presence on this forum, and I am also not here for long discussions. What well intrigues me why can I not make the connection work with 20 years of IT experience ??

My guess, and I mean this with no disrespect, is that you missed the note in the troubleshooting section which warns that software firewalls can prevent the required ports from being accessible.

To begin with, my Wavestate never appears now in my Bonjour browser since august 2021, whatever I remove/purge/reinstall. So I don't even try with the editor.

If you can use the updater, you can use the editor. Both rely on Bonjour.

Btw: could you please elaborate what do you mean by reconfiguring Bonjour service ? I don't see such an option in Windows 10/11.

One or two people have solved weird Windows problems by uninstalling and then reinstalling Bonjour.

Best regards,

Dan

[jb58]

Hi Janos,

I really appreciate your presence on this forum, and I am also not here for long discussions. What well intrigues me why can I not make the connection work with 20 years of IT experience ??

My guess, and I mean this with no disrespect, is that you missed the note in the troubleshooting section which warns that software firewalls can prevent the required ports from being accessible.

To begin with, my Wavestate never appears now in my Bonjour browser since august 2021, whatever I remove/purge/reinstall. So I don't even try with the editor.

If you can use the updater, you can use the editor. Both rely on Bonjour.

Btw: could you please elaborate what do you mean by reconfiguring Bonjour service ? I don't see such an option in Windows 10/11.

One or two people have solved weird Windows problems by uninstalling and then reinstalling Bonjour.

Best regards,

Dan

Thanks Dan, now it is even more clear. Concerning the upgrade, I could only do it in USB boot mode so Bonjour was not involved. In the meantime I just see that the software firewall of AVG makes it impossible to enable the ports for Bonjour - it has fixed rules to block the ports I need, and it has no option to deactivate them.

Best regards,
Janos

[transmit]

Hello

just for info on the subject of WIN 10 updates.

I now have Win 10 version 21H1 on my 1st DAW Studio PC and WIN10 version. 21H2 on it.
Both versions run clean without problems, my Wavestate with the editor!!! works wonderfully and my Modwave with the editor!!! also works perfectly without errors. Both editors are recognized without problems and both run side by side as intended over USB network: NCM

Kind regards

Translated with www.DeepL.com/Translator (free version)

[Muriatic]

I am using linux as my OS and, by hosting a Windows 10 virtual machine via the free virtualbox application, I was able to update my firmware from 1.01 to 1.04 to 1.06 to 2.01. I can also easily run the editor/librarian and I will try the sample builder too.

I hope this encouragement will be of use to people who are having or who have had difficulty with the Korg software running on a "native" Windows OS.

[dreamingstillness]

Hey all, I just wanted to say I've been having this same problem on Win 11, and tried everything I could think of without success, but after reading about how it was likely a firewall issue it occurred to me that I was running a VPN.

Turning off my VPN immediately allowed my Wavestate to be identified and update.

Hope this helps!

[Acheron]

My thought on this is why not update the firmware from a file on a USB stick/drive and bypass the WIndows/MAC operating system?

[Space Girl]

I want to update to the latest OS for Wavestate Mk1 and haven't tried it yet. After reading this post I have been pondering if this update will cause me more grief than it's worth.

I have some behavioral issues with my Mk1 and need to do something to fix it.

Is this 2.1.3 updater definitely for use with Mk1 Wavestate or is it for new Wavestate version Mk2? I want to be sure I get this right.

Anyone have any good feedback on Wavestate SE yet? Is it worth the money to upgrade from a Mk1?

[Derek Cook]

Hi

Every time I have updated, I have had no issues, but I have always read the update instructions (nit sure how much of an influence that is).

[Space Girl]

Unfortunately it's all now a mess as I tried to update after fully reading the instructions. The updater failed on something failed with a code 193.
I am on 64bit windows 7.

Then the drivers messed up, even though I went through the Rndis set up fine.
It seemed to have installed new OS to Wavestate and plays OK I think but now I have now editor librarian as the drivers arn't working right.

I then deleted the Wavestate drivers in Korg midi drivers Drv and when I plugged usb back in it saw the Wavestate OK but no longer shows any RNDIS or NDIS. The librarian update is just waiting for device now as others have mentioned here.

Was going to have a creative day yesterday but ended up quite stressed with all this. I'd like to just get back to my old 1.6.6 version but can't now.

I have to get the new librarian working and still not 100% sure it works on win7. You'd think if they made the update for win 7, then the librarian editor would also be for win 7. The download page does not say it only says win10/11. I've contacted Korg but who knows if they will reply.
It's SUCH A MESS!

Any know know if you can do a factory reset or some how can you uninstall the latest OS update and go back to the previous one?

My or firewalls never caused issues with the old librarian editor so don't think that would be a problem.

All so much easier with analogue Prophets!

[Space Girl]

Update on recent updating issues: Latest 2.1.3 OS seems to be working but cannot get drivers working now and get a code 10 everytime. I reinstalled the Librarian editor 1.2.1,. Bonjour running fine, firewall not blocking and even added allow Wavestate just incase. I have gone over everything, uninstalled, installed, tried another usb cable, re-checking and still cannot get drivers to work.

When I first plugged Wavestate usb in to laptop, it installed driver, but it just fails to work. OH, if only there was a disc with drivers on like the old days.

Anyone else manage to resolve a code 10, that wasn't Bonjour related?