Ah, ok! So what I’m seeing is this, when I’m in Track on Equal mode:
- I create a knob mapping and set the min to 50%.
- I turn the virtual knob to 0% manually (or by using a second knobset)
- I go to the main knob set, which has the 50/100% min/max limit, and I can’t pick the knob up since it’s at 0 but I set a minimum of 50.
To get out of it, I can go back to whatever I did to get into this situation in step 2, and move it manually or with another knobset into a valid range.
I thought about this exact situation a lot while making Pickup modes. To indicate that this is what’s happening, I have a black square drawn on the knob in Knob set view (it’s not pretty and the GUI can be improved, but at least it’s a signal that the knob cannot be “picked up” due to the the mapping having limited the range).
This is something that’s a natural consequence of having these three features: 1) min/max ranges for mappings, 2) the ability to move a knob outside of those min/max ranges manually or using multiple mappings, and 3) pickup modes.
If anyone has ideas for how it could be done better, I’m all ears. But essentially when you set a knobset range you are saying “This knob should not go below 50%”, and when you enable Track on Equal mode, then you’re saying “The knobs should never jump values”. And then if you manually turn the knob below 50%, it’s kind of a contradiction – the only only way to resolve it is to either change the min/max range, or manually adjust the knob back into a valid range, or violate the “never jump values” rule.
As for the other glitches, they all sound like the settings file is not loading or saving. This has been reported by others, too. I have’t gotten it to happen to me, but I’m still looking…