I was using a DSI Polyevolver as my main controller, and for sustain ON it sends CC64 with a value of 64. Running the most current version of wavestate native, which is 1.0.5.0 as of this post.ĮDIT: Ok, I figured out what the problem is here. If someone can confirm this broken behavior it may serve as a warning for other potential buyers, as well.

Alternatively I'd love this to be something I'm doing wrong. I love the Wavestate so much that I'd likely purchase the hardware version if this is really broken and not fixed soon. I can even use a MIDI monitor plugin in Live to see the CC being sent with values on/off. My sustain pedal is being interpreted correctly by my controller and is respected by every other synth in my studio, including VSTs (such as Pigments). This is the behavior for me regardless of whether I am running them standalone or within my DAW (live). What I'm wondering is if someone can confirm that neither synth responds to Sustain/Damper CC64? There is even a button on every layer in the Wavestate setup page for enabling it, yet nothing seems to happen when it is sent. I'd like to think my system isn't the issue as I have no trouble running multiple instances of Pigments with plenty of plugins etc.

Opsix runs well, Wavestate has some pretty bad UI lag for me when adjusting parameters, but the sound is good and using a controller for parameters is smooth (occurs in both standalone and in live). I recently purchased both the Opsix and Wavestate native plugs during their black friday sale.

Korg wavestate black friday