I've had various comments saying that people were surprised that the compatibility test does not offer bi-directional communication with the synth, so I have made some changes to allow it to send and receive parameter requests.
It's important to understand that Yamaha synths do not broadcast parameter changes when they are made on the synth - if you change a parameter directly on your synth, it won't send a message to connected systems informing them of the change.
Instead, connected systems have to send a parameter request, to which the synth will respond with the value for that parameter.
So, the compatability test now sends an initial burst of parameter requests when you select a synth, so the controls will jump to their correct value.
Moving the controls using the compatibility test will update the synth, so you can be assured that they continue to show the correct values, but if you change one of those parameters on the synth itself, the web UI will be out of sync.
To get around that in the same way as KDx does, there is now a Request values button at the bottom of the compatibility test, which will re-send those parameter requests, and update the controls on the web UI to the values held by the synth.
I have also had various reports from MODX+ users, saying that KDx does not work properly with their synths.
I believe it is related to the way KDx attempts to auto-detect the correct MIDI ports, and I am still investigating the reasons for this issue, although not having a MODX+ myself with which to test is proving a little difficult.
Many, many thanks to @HaPe for getting his MODX+ connected to the system while on a call with me so I could debug the issue.
I hope to have an update and a fix for you soon.
It's important to understand that Yamaha synths do not broadcast parameter changes when they are made on the synth - if you change a parameter directly on your synth, it won't send a message to connected systems informing them of the change.Instead, connected systems have to send a parameter request, to which the synth will respond with the value for that parameter.
So, the compatability test now sends an initial burst of parameter requests when you select a synth, so the controls will jump to their correct value.
Moving the controls using the compatibility test will update the synth, so you can be assured that they continue to show the correct values, but if you change one of those parameters on the synth itself, the web UI will be out of sync.
To get around that in the same way as KDx does, there is now a Request values button at the bottom of the compatibility test, which will re-send those parameter requests, and update the controls on the web UI to the values held by the synth.
MODX+ issues
I have also had various reports from MODX+ users, saying that KDx does not work properly with their synths.
I believe it is related to the way KDx attempts to auto-detect the correct MIDI ports, and I am still investigating the reasons for this issue, although not having a MODX+ myself with which to test is proving a little difficult.
Many, many thanks to @HaPe for getting his MODX+ connected to the system while on a call with me so I could debug the issue.
I hope to have an update and a fix for you soon.
