RangedValue - Min/Max Values or Steps

[NukeArts]

Hello,

Is there a way in the API for RangedValue to find out how many Steps/what Resolution a parameter has?

I need to update the EncoderLEDs of my controller and they have different modes (ie. 128 Steps, 100 Steps, 32 Steps, 2 Steps....). So for a typicall on/off value I would use the mode for 2 Steps.

I do not only have this issue with the encoderLEDs but also with the encoder value handling. For example again this on/off value:
My endless rotary encoders give me +1/-1 Steps (up to +5/-5 Steps) of Value depending on the direction and the speed. Lets take this on/off parameters as example. When I tell the Bitwig API the resolution to read a value is 128 then a "off" becomes a 0 and a "on" becomes a 128.
When I hold an internal integer variable with the encodervalue, which gets incremented by 1 when you turn it normally/slowly, I would need 64 steps in the worst case to switch from "off" to "on". And thats a bit annoying.

When my script knows how many steps a parameter has, then I can "correctly" handle the Encoder LEDS and the Encodervalues with a better experience for the user. But I can't find a way to get this information. Please advice!

The only solution I can think of at the moment is to build my own datastructure for all possible parameters in all vst I use and thats not really worth it.

br, Ralph

[moss]

No, you can't. It always works the other way round: You tell the API in which resolution you want to have the values. But as you say this might cause issues with some parameters.