glad you like it
ok, so I had a quick look… I guess you are talking about rate?
so the issue is to do with how many ‘steps’ there are on the potentiometer and then how that maps to the real values… ( I can’t remember off hand exactly where than ‘quantisation’ happens)
you can kind of see this, if you twiddle the knob on the organelle to the end and back, sometimes you can get closer to 50 (e.g. 50.2 )
well you could edit module.json (in the slicer directory) , the smaller the range for play rate, then the more accurate it will be e.g. if you changed it to
then it will have double the resolution, this may help, but might not solve the issue entirely.
a ‘hack’ would be to change the sliceplay.pd
currently its [r rate-$2-$1] → [/ 100] →
you could instead round this to the nearest 10
currently its [r rate-$2-$1] → [/ 10] → [int] → [/ 10] →
it would then step 0,10,20
note: this is a HACK because the UI will not tell you this, it’ll just functionally behave like this!
another alternative would be to turn this into a division rate…
(which would be my preferred option, albeit fractionally more involved )
first in module.json we’d change the parameter , to an int (from pct) and to have a suitable range.
["int","rate-1","Play Div",-10, 10,1],
so now 1 = original speed, 2 = half speed
(I just changed ‘name’ to make more sense you can still leave the same)
then we need to change the spliceplay to reflect this change.
[r rate-$2-$1] → [expr 1 / $f1] →
again this primarily works, since the number of steps is smaller
note: any saved presets, would have to be ‘updated’ as they’d have the wrong value.
you can actually edit the preset file that you save.
… as mentioned above, this ‘stepping’ is a feature of the UI.
if you edit a preset, and load it in Orac… it will use using the exact value from the preset.
(just don’t touch the rate in the UI )
so lots of options…