FWIW, it took me seconds to drop these files into the SAFP. If I could switch between them with completion-before-change, I’d be home.
In any case,if it is up to the SAFP to set the upper bound of a widget controlling the track parameter, then I think it would be good if the SAFP kept that upper bound at the highest track number actually loaded.
OTOH, if the widget has a say in the top scaled value it can output, how can I set that?
What I haven’t been able to get from the docs (so far) is how to set up so that the full range of the widget causes traversal from the min to the max at the destination (scaled value).
Here I am trying to range from Track 1 to Track 14 in the SAFP.
I want those 14 outputs to take place across the full range of the knob, not across 0 - 1.4 on the knob (leaving the vast majority of the knob unused).
It is implemented this way.
When the Knob is fully right is sends 0.14 (yes you entered 14, but the value is 0.14)
So 100 means 100% and sends out the value 1.0
For this particular example, if you look at the max Track Number value with the knob all the way up without any scaling, it shows 1001.
You have 14 tracks, which means you need 13 additional values after 1.
That’s why you’re scaling to 1.3 to get a total of 14 increments.