user_osc_param::cutoff and user_osc_param::resonance not working...

[hammondeggs]

Description Currently, with the minilogue xd running the latest 2.01 firmware, with a user oscillator, at void OSC_CYCLE(const user_osc_param_t * const params, int32_t *yn, const uint32_t frames)

, params->cutoff and params->resonance appear to constantly return values of what appear to be 0x1FFF (8191), regardless of the settings of the cutoff, resonance, any filter modulation, or the multi oscillator being routed pre/post VCF.

To Reproduce Steps to reproduce the behavior: Do something with params->cutoff and/or params->resonance. To test this, I created a simple oscillator that used the params->cutoff as the oscillator frequency. With the multi oscillator selected and a simple (default) gated amplitude EG, this oscillator's frequency should change with the filter cutoff knob, and / or when filter EG / LFO is applied (if applicable)

Expected behavior The params->cutoff and params->resonance should perform the expected behaviour. Note at this time this isn't explicitly specified in the current API documentation, I myself am hoping it follows the current filter value including any modulation or envelope generation.

Additional context I am curious to know how this will perform, as mentioned earlier - at least for my current use case - it would be ideal if it followed the existing VCF frequency including any modulation. Note, in testing I also divided this params->cutoff value by 4 and sure enough the generated frequency was fixed at around ~2047hz, so I can be reasonably sure the maximum value of 0x1FFF was only ever being passed.