Zita1 reverb: Display setting doesn't match the actual setting
Reported version
3.2
Type
Functional
Frequency
Once
Severity
S4 - Minor
Status
active
Regression
No
Workaround
No
Project
Win 7 / 2.0.3
Create a new Zita 1 module. That is, by changing "No effect" to "Zita1" in "Synthesizer > Master effects".
The problem is that the nominal settings of the newly-created module do not match the actual settings. For example, you can immediately hear that reverb is being applied although "Output" reads as "Dry"! This seems to affect all the controls, not just the "Output".
Solution: Ensure that the actual values of all the controls always matches the nominal values, especially when Zita1 is first created.
Comments
Still the case in 3.2.3:
Result: There is no reverb (as expected).
Result: Although the "Mix" is set to "Dry" you can still hear a default reverb.
Related to #292995: [EPIC] Synthesizer issues.
OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.4.2.9788, revision: 148e43f
Still apparent in 3.4.2.