search

zynaddsubfx / zyn-fusion-issues

Issue Only Repo
31 stars 0 forks source link

Macro Control: mapping ranges results in poor number precision #116

Open unfa opened 7 years ago

unfa commented 7 years ago

I assigned a Macro driven by a standard 7-bit CC control (0..127 range), I wanted to use the Gain/Offset macro settings to achieve a better resolution by mapping my full CC range to a smaller part of the ADDsynth > VCE2 > Modulation > Amplitude control to be able to perform these cool growly sounds live.

However it seems like I don't get an increased resolution, but a further reduced one, as if the range mapping was performed after quantizing the CC values.

Could this be changes to that mapping a CC control will give you all 128 states mapped to a small range of a control giving you better precision?

fundamental commented 7 years ago

This is a combination of two issues:

  1. Many controls within zynaddsubfx have limited precision as they tend to be represented with 0..127 integers.

  2. The macro graphical view does not show these quantization steps and thus the user is surprised when smaller ranges don't provide continuous values.

Both issues are important IMO (for the second consider automations over enumerated types e.g. filter type), but separate.

unfa commented 7 years ago
  1. Would it make sense to make the continuous values use floats instead? I guess this is going to be a lot of tedious work...
fundamental commented 7 years ago

The 3.1.0 plan is to have all of the important controls using floating point representations. The groundwork was setup by https://github.com/zynaddsubfx/zyn-fusion-issues/issues/58 and as per being tedious work, it sure will be. Tedious, Error prone, but necessary for overall evolution IMO.