Quote:
Originally Posted by Andi!
Why should normalized values used in the presets?
|
Why shouldn't?
Quote:
Originally Posted by Andi!
The values in IParam are also readable and when serializing params I see no conversion. At some point you have to convert normalized to readable values anyway: when reporting them to the host.
|
The problem is that you set normalized value (in both case, via Host or GUI/IControl) and I (personally) use only normalized values within plugin/audio processing.
How do you smooth params if not with normalized values? I dunno you use a 1pole filter IIR on "real values". The same for automations: you always go between 0 and 1, THAN (only in the end) you need to wrap on "real value".
Thus, at the moment, control/host set values as normalized, which are than converted on IParam in real values (1 step of "round error"), than I re-convert on normalized (another step), process it (smooth+automation), and than re-re-convert in real value (another step of quantization error).
Basically I use 90% of the times normalized values, converting them often. Also storing on presets will go back/forth one time from real/normalized (having a loss of data so). That's why I feel logic stay always in normalized domain.
If all was normalized, you only quantize one time (when you need to process audio on calculated parameter, after smooth and automation). No less in store, no less in smooth/automation/set.