Example when the model doesn't support output calibration:
And when normalized output isn't supported:
If a non-supported option is chosen, then raw output will be used.
The "Normalize" control is removed from the front page since this extends it:
and the default will still be "normalized output" for consistency. Calibrated output is probably most useful for pedal models.
Might want to put some control on the "front page" when the selected output mode isn't supported? Maybe an orange Exclamation point in a circle and make the gear orange? Not sure.
[x] Does the VST3 plugin pass all of the unit tests in the VST3PluginTestHost? (Download it as part of the VST3 SDK here.)
[ ] Windows
[x] macOS
[Y] Does your PR add, remove, or rename any plugin parameters?
[N] If yes, then have you ensured that older versions of the plug-in load correctly? (Usually, this means writing a new legacy unserialization function like _UnserializeStateLegacy_0_7_9.)
Description
Implement output calibration. Resolves #529
Normalized output is selected:
Example when the model doesn't support output calibration:
And when normalized output isn't supported:
If a non-supported option is chosen, then raw output will be used.
The "Normalize" control is removed from the front page since this extends it:
and the default will still be "normalized output" for consistency. Calibrated output is probably most useful for pedal models.
Might want to put some control on the "front page" when the selected output mode isn't supported? Maybe an orange Exclamation point in a circle and make the gear orange? Not sure.
PR Checklist
format.bash?_UnserializeStateLegacy_0_7_9.)