# Question on pluginval **URL:** \ **Category:** Audio Plugins\ **Created:** [August 26, 2020, 7:26pm UTC](https://forum.juce.com/t/question-on-pluginval/41433 "2020-08-26T19:26:53Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![kamedin](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/kamedin/32/11711_2.png) [@kamedin](https://forum.juce.com/u/kamedin)\ **Post date:** [August 26, 2020, 7:26pm UTC](https://forum.juce.com/t/question-on-pluginval/41433/1 "2020-08-26T19:26:53Z")
I’m getting “Parameters not restored on setStateInformation” sometimes, only when randomise tests is active. I have some parameters linked, so a change in one of them moves the other one, as in meta parameters. I also have some parameters bounded by the values of other ones, so their changes are checked and corrected if needed. All this linking and checking is done asynchronously, and if I disable it, the fail is gone. My guess is that PluginStateTestRestoration is not run on the message thread, and after setStateInformation a link or check may be performed. So, two questions: is this possible, and may it cause the plugin to be rejected by some DAWs / Apple / Avid? ---
**Author:** ![fuo](https://avatars.discourse-cdn.com/v4/letter/f/ba8739/32.png) [@fuo](https://forum.juce.com/u/fuo)\ **Post date:** [December 19, 2023, 10:47pm UTC](https://forum.juce.com/t/question-on-pluginval/41433/2 "2023-12-19T22:47:06Z")
Hi @kamedin, did you get to the bottom of it? I am facing the same issue, and even the most simple example with a single float parameter does trigger the error. At first I thought it was related to this thread [here](https://forum.juce.com/t/basic-audioprocessorvaluetreestate-plugin-wont-pass-pluginval/39543), but it does happen with floats too. As you mentioned it only happens when “Randomise tests” is selected. (using Juce 7.0.9 and pluginval 1.0.3) ---
**Author:** ![Rincewind](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/rincewind/32/10645_2.png) [@Rincewind](https://forum.juce.com/u/Rincewind)\ **Post date:** [December 20, 2023, 8:20am UTC](https://forum.juce.com/t/question-on-pluginval/41433/3 "2023-12-20T08:20:45Z")
Do you by chance have two parameters dependent on one another? The auval tool catches that case and warns you about marking those parameters with the “isMeta” flag. ---
**Author:** ![fuo](https://avatars.discourse-cdn.com/v4/letter/f/ba8739/32.png) [@fuo](https://forum.juce.com/u/fuo)\ **Post date:** [December 20, 2023, 3:58pm UTC](https://forum.juce.com/t/question-on-pluginval/41433/4 "2023-12-20T15:58:11Z")
No I don’t : it is the simplest possible processor implementation with just a single float parameter. If I set “num repeats” to 5 I generally get 1 or 2 errors. ---
**Author:** ![sudara](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/sudara/32/8071_2.png) [@sudara](https://forum.juce.com/u/sudara)\ **Post date:** [December 21, 2023, 12:46pm UTC](https://forum.juce.com/t/question-on-pluginval/41433/5 "2023-12-21T12:46:33Z")
I’d recommend [filing an issue](https://github.com/Tracktion/pluginval/issues) on the repo, as it’s likely others are running into the same problem. `setStateInformation` related stuff was [was touched](https://github.com/Tracktion/pluginval/pull/101) with 1.0.3, so you could also try to see if you could reproduce with 1.0.2. ---
**Author:** ![fuo](https://avatars.discourse-cdn.com/v4/letter/f/ba8739/32.png) [@fuo](https://forum.juce.com/u/fuo)\ **Post date:** [December 22, 2023, 3:38am UTC](https://forum.juce.com/t/question-on-pluginval/41433/6 "2023-12-22T03:38:45Z")
Yes that is probably what I should do 🙂 I tried versions 1.0.3, 1.0.0 and 0.3.0 with the same result. ---
**Author:** ![sc58](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/sc58/32/19854_2.png) [@sc58](https://forum.juce.com/u/sc58)\ **Post date:** [September 21, 2025, 9:20am UTC](https://forum.juce.com/t/question-on-pluginval/41433/7 "2025-09-21T09:20:25Z")
Did you ever resolve this issue? If so, how? I’m getting a similar problem and none of the forum posts on this are particularly conclusive, especially for float parameters. ---
**Author:** ![fuo](https://avatars.discourse-cdn.com/v4/letter/f/ba8739/32.png) [@fuo](https://forum.juce.com/u/fuo)\ **Post date:** [September 21, 2025, 7:38pm UTC](https://forum.juce.com/t/question-on-pluginval/41433/8 "2025-09-21T19:38:05Z")
I usually don’t run randomized tests, and simply ignore these particular errors when I do. ---
**Author:** ![sc58](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/sc58/32/19854_2.png) [@sc58](https://forum.juce.com/u/sc58)\ **Post date:** [September 21, 2025, 8:56pm UTC](https://forum.juce.com/t/question-on-pluginval/41433/9 "2025-09-21T20:56:04Z")
I ended up finding a solution. Pluginval 1.0.3 running via GUI was the one that failed on a true float parameter (filter cutoff), but then I tried CLI and realised that Pluginval was up to 1.0.4, and that version was failing on some other float parameters that were actually functioning as binary switches. So I tried the solutions here: [Pluginval can set an AudioParameterBools to odd values - #32 by dave96](https://forum.juce.com/t/pluginval-can-set-an-audioparameterbools-to-odd-values/50971/32) and that resolved the issue on Pluginval 1.0.4. I still get issues with 1.0.3, but I’ll leave the investigation there since I have everything passing on the most stringent tests on the latest Pluginval.