Pluginval can set an AudioParameterBools to odd values

[dave96]

@kamedin

(edit) And the fix was already proposed here, in this thread… I think the confusion was caused by

@dave96 mentions in the other thread that it might be required by auval that a parameter set to some odd value should return that odd value.

which doesn’t make sense to me (it already doesn’t happen for any type other than Bool), and is also contradicted by Dave himself here

As far as I can remember, there is no test in pluginval that sets a random parameter value and expects to be able to read that same value back is there?

This is only a contradiction in terms of different tools, auval vs pluginval. And like I said, I can’t remember exactly what auval tests for, maybe it doesn’t do this test and if so that’s good, pluginval doesn’t either and that’s consistent.

---

Can I clarify if it is only AudioParameterBool’s that are causing this failure?
If so, yes I think this would fix it:

@kamedin

Maybe this would fix it:

void setValue (float newValue)
    { value = (newValue >= 0.5f ? 1.0f : 0.0f); valueChanged (get()); }

Or even using the range member and the same body as the AudioParameterInt/AudioParameterChoice. E.g. (not tested):

float getValue() const
    { return range.convertTo0to1 (value); }
void setValue (float newValue)
    { value = range.convertFrom0to1 (newValue); valueChanged (get()); }

Does making that local change fix the problem for everyone here? If so, maybe we can propose this to the juce team?