OSC_PARAM changes all parameters to zero before first OSC_CYCLE call

[korginc]

OSC_PARAM changes all parameters to zero before first OSC_CYCLE call

[h2g2guy]

@boochow -- I think it's reasonable that OSC_PARAM is being called upon initialization of the oscillator program. If your oscillator program is used as part of a preset on the prologue or minilogue xd, OSC_PARAM is likely the way that the correct parameter values get set when that preset is recalled.

There are bugs related to this behavior though, particularly with bipolar parameters. Please see my bug #36 .

[boochow]

@h2g2guy thank you for your comment! I agree with you that OSC_PARAM should set the parameters to the appropriate value when a preset program is loaded. It is a completely reasonable behavior.

My point is that I want to define initial values of parameters for NTS1, which is not able to have any preset programs. Currently, the SDK always sets all parameters for their minimum values. I also think that maybe the initial-value feature would be useful for Prologue/Minilouge xd because it could give default parameter values for a new patch.