When running level 10 tests in pluginval (which is an AWESOME tool) I sometimes get this inconsistent error:
Starting test: pluginval / Plugin state restoration...
!!! Test 1 failed: Parameters not restored on setStateInformation -- Expected value within 0.1 of: 126.763, Actual value: 127.656
How can I debug it? Is there a place where I can set a breakpoint to catch the specific parameter which is failing? In the same way that a breakpoint in AllocatorInterceptor::logAllocationViolation() will catch Allocations during process errors.
Honestly I don’t remember exactly how I solved it, but most likely it was something to do with macro parameters. Are you using macro parameters that can affect other parameters? If so, do something like this to inherit and make your macro parameter a meta parameter
I’m just fighting with a similar issue during the pluginval validation for AU. Looking into the source code I just noted how pluginval and juce construct the AUInstanceParameter object. This object basically doesn’t handle the meta value and it doesn’t override isMetaParameter.
This is why using pluginval the parameter.isMetaParameter() in the testParameterInfo is always false. I looked for it here in the forum, but I didn’t find any issue related…