Bug: A2B erroneous range under certain conditions

[chevdor]

The exact issue is:
If you use A2B with zones, on an axis >8 and a precision >8, the range is messed up.

To reproduce, you need:
- a button, say P10
- an axe: say 3
- a virtual axe: say 9

Use AUX Ax on P10 with SWAP or SWITCH 0 to generate data on axe 9.
First set axe 9 with a precision of 8.
Setup you A2B, using 5 zones, on axe 9. This should work fine.

Now setup axe 9 on a precision of 12. Observe the result.

[Alex Oz]

You cannot assign and use the function for axes greater than 8.

[jukelo]

You cannot assign and use the function for axes greater than 8.

Boolean A2B allows referencing axes beyond 8:

This works fine if axis 11 is set to 8 bit.

However if the axis is set to 9 bit, the A2B range is offset and maps to only one half of the axis:

if set to 10 bit, the range is offset and maps to only the first quarter of the axis:

[Alex Oz]

Thanx, try v2_20_2(2)

By the way, A2B was transferred to Boolean as a result of this topic - thanx twice!