Shouldn't there be a constant range transform from 0,1 to -1,1 before the waveshaper?
As a matter of fact, yes, there should be (I'm wondering if I shared the wrong snippet), exactly like you configured
It seems waveshaper is just all around broken
I've checked it out and it sounds like you are right, the Node fails to correctly restore itself (e.g. when you restart the app): it gets stuck too early on something that's supposed to smooth transitions between 2 changes, to avoid clicking while editing
(unfortunately, this is some pretty old logic that was left unattended)
The fix for this will be in the next update (probably next week, brought earlier to get this issue, and another bugfix out)
Thanks for the heads up on this one, and sry about the confusion