# BR: possible APVTS bug **URL:** \ **Category:** General JUCE discussion\ **Created:** [April 24, 2024, 8:00pm UTC](https://forum.juce.com/t/br-possible-apvts-bug/61064 "2024-04-24T20:00:22Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![hugoderwolf](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/hugoderwolf/32/14039_2.png) [@hugoderwolf](https://forum.juce.com/u/hugoderwolf)\ **Post date:** [April 25, 2024, 9:52am UTC](https://forum.juce.com/t/br-possible-apvts-bug/61064/3 "2024-04-25T09:52:43Z")
Yep, that’s been bugging me for a while too. I described the problem here (including possible fixes): > [@Pluginval can set an AudioParameterBools to odd values](https://forum.juce.com/t/pluginval-can-set-an-audioparameterbools-to-odd-values/50971): > > I’m debugging a strange issue that sometimes leads to Pluginval’s state restoration test to fail. This is with an AU plugin, I’m not sure yet if it also happens with the VST3. The test checks if the sum of parameter values is the same before and after a state restore. Under some circumstances, when the test starts, the two AudioParameterBools that the plugin uses have random values that are not 0.f or 1.f. After saving and restoring the state they are correctly set to either 0.f or 1.f, and thu… It affects both AudioParameterBool and AudioParameterChoice. If I’m not mistaken, to really get rid of the error, the fix needs to be applied to both the plugin and pluginval itself. Edit: just noticed it’s not about a bool or choice, so it’s probably a different bug. Nevermind. 😉 --- _[View the full topic](https://forum.juce.com/t/br-possible-apvts-bug/61064)._