Best practice for creating knobs with limited ranges

#1

The default P Knob is always 0-64 value output. This range then binds to an assigned controller like a midi knob. If I need to work with a much smaller range (for example 22) should I patch together a logic network to bind the full range of a knob to these values or is there a simpler way to quantize all of the values into the needed range?

Oscillating the filter frequency
#2

I do it this way: set the dial to 0, followed by *c also at 0. + it with another dial that sets the minimum value for the sum. Set the original dial to maximum, open the *c until at desired maximum value. Then don't touch the another dial and *c anymore.

#3

pretty cool, gonna try it. I ended up using the denominator division and then some less, greater gates. but it isn't exact enough.

#4

Here is a picture of a way to do it:

#5

hey there , i want to make a midi controller for mssiah (c64) and already
connected everything and paste it in patcher with inlet .
There are all cc messages but some have limitations and some cc numbers
start from 1till 4 like for example slide .
wich i can't figure out how to start …or how to do best ?
what i have till now is that i do limitations with math/+c for end values…
like cc7 patch volume is 0-15 than i will do it like (math/+c 7,5 )
because 0/127 original cc values is this correct ?
i would like to add later control dial and find a way to save patches and control further …Thanx in advance greets Reinhard

#6

using *c is one way...
the other approach I use is just using bit shifting, when its a multiple of 2. (which I find is very often the case). I use this, as its simply more efficient (i.e. lower cpu load)

also look at oneliner_k, this allows you to enter an 'equation' to convert the inlet to outlet, and has a 'dial' to feed into the 'equation'.

with axoloti, there are many different ways to solve these kind of problems.
if your not trying to squeeze the last bit of performance out of axoloti, then often any of them will work.

you can use sub-patches (or custom objects, advanced use :wink:) , if you wish to create a dial that has this built in.

what you cannot do, is to change the way the UI works, i.e dials have to run 0..64, or -64..64.
this is because the dials are rendered in the axoloti java UI, so cannot be changed by patching.