Params that can hold negative values are not initialized properly

[korginc]

Params that can hold negative values are not initialized properly

[h2g2guy]

@etienne-korg , I hate to ping devs directly, but I've not received feedback on this for several months. I'm prepping for release of an oscillator in the next few weeks, and if this bug is not resolved, I will need to release with an workaround that will be unpleasant from both the dev and user perspectives (and I'll need to explain to my users that this issue is an issue with the synth, not with my oscillator).

I can confirm that this bug still exists in prologue version 2.10, using the very latest version of the SDK (I pulled master before building).

If there's anything I can do to help drive this bug to a root-cause and a resolution, please let me know. I'm happy to supply a sample oscillator and a repro video, if that would be helpful.

[dukesrg]

I can confirm thet bug too. Current workaround is to limit bipolar parameter to -99 and add 100 in the parameter handler if zero value is received.

[dukesrg]

Some additional details on bipolar values:

• minilogue XD initializes params internally by raw 0 value (i.e. -100%), displaying first time 0%. On the second selection of the same parameter, the lower bound value (which is stated in the manifest) is displayed, but parameter value is unchanged. On program recall all parameters are restored and displayed fine.
• NTS-1 initializes to the lower bound value - both internally and displayed value.

@etienne-korg I really hope drumlogue won't have such issues and all logues firmware will be aligned.