You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 38e61d7
Browse filesBrowse the repository at this point in the historyBrowse files
Only send 0 or 1 to two-step parameters below strictness level 8
Some plugins keep in-between values for on/off parameters rather than
mapping them to a step (e.g. juce::AudioParameterBool), which made the
plugin state restoration test fail at level 6. Arbitrary values are
still sent to these parameters at level 8 and above.
Hosted VST3 parameters don't report isBoolean, so two-step parameters
are identified by their number of steps as well.
Copy file name to clipboardExpand all lines: CHANGELIST.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,6 +15,7 @@
15
15
-`--help` output is now generated by CLI11
16
16
- Added a "Discrete parameter state restoration" test (strictness 8) which checks a discrete parameter has the same value after restoring a state, whatever value it held beforehand. This fails for parameters that keep the raw normalised value from the host instead of mapping it to a step (e.g. `juce::AudioParameterBool`)
17
17
- Fixed false failures in the "Plugin state restoration" test where the first parameter was compared against the last value sent by a previous test rather than the plugin's own value
18
+
- Below strictness level 8, two-step (on/off) parameters are now only sent 0 or 1 when tests randomise parameter values. Arbitrary values are still sent to them at level 8 and above, and to all other parameters at every level
18
19
- Enabled the editor stress and extreme (real-time allocation / oversized block) tests that were present in the source tree but had not been compiled into the build
0 commit comments