Robin Schmidt
Robin Schmidt
...or wait...you are actually shifting your exp-function to the left...i think, this is different from what our exp-scaling does. it's an exp with shifted input....hmmm...
make sure that you choose your b-value wisely. later changing it will break the mapping to meta parameters (i.e. may break patches with connected metas and daw automations)...it's similar to...
> still hitting this i need to know, which class/function this is. you cut the top off too early ;-)
here's how you can see the actual mapping function in term of max (m) and b: https://www.desmos.com/calculator/pamgkqwry9 i chose a range -20000 to +20000 as would be appropriate for frequencies...
ok, i'm allowing to set Parameter::CUSTOM from client code now (have dragged the value before NUM_SCALINGS)
as said above, actually the idea was that the user/client doesn't manually sets this option but it is only set internally as soon as you pass a mapper. but i...
hmm..you need rounding somewhere...but then, how would the inverse function "unmap" look like? such a function is actually not invertible. we need inversion, because when client code calls setValue and...
what's your b-value?
look at this - such low b leads to almost linear scaling: https://www.desmos.com/calculator/pamgkqwry9 you need something of the order of 1...10, you need moar beee!!!
this actually doesn't matter. the shape stays the same, just the whole graph gets scaled down by another "a" factor then