Multislider

gentleclockdivider

Something that has bugged me it when using the mouse area (for sweeping ) and multidisplay , I always have to start the index from 1 , for both the mouse area and multidisplay to work correctly
So If I hvae 16 elements in the M.D , index goes from 1- 16 , and the same for the mouse area
Choosing 0-15 always messes with the first element

When choosing 0-15 range for both mouse and multi , the first two elments always behave eratic

colB

Hmm, difficult to say without an example to test. Also depends on what you mean by 'erratic'…

One thing that looks wrong here though is the quantisation approach. The way you have it set up is going to change the index when the the mouse pointer x coordinate crosses 0.5, 1.5, 2.5 etc.

I would imagine you want it to change at 1, 2, 3 etc.

A general approach is subtract 0.5 from the input coordinate, then clip the quantizer output to the required range (set your multi display and event table to 'clip').

A simpler approach for this specific situation would be to make your range 0.501 to 16.499 instead of 1 to 16.

gentleclockdivider

In the end I just used 1.0 as the minimum value for mouse x , since the multidisplay also starts at index 1
Works great , and supersmooth action , exxept when elements exceed 256 , but then I just use the event table .

colB

https://community.native-instruments.com/discussion/comment/231493#Comment_231493

If there are enough elements, you probably won't notice the quantisation alignment error.

Michael O'Hagan

https://community.native-instruments.com/discussion/45800/multislider

This is because the snap value array and the multi display both index natively at 1 instead of 0.

One of my long standing gripes about reaktors design is the inconsistency of index values.

Enent table and audio table, index is 0-N.

Core arrays and data tables, index is 0-N.

Primary snap value arrays and multi displays, index 1-N.

I think there are a few other that have index offsets, but I don't remember what they are now.

The number of times that I have forgotten this and spend a decent amount of time trouble shooting, just to later remember that it's an inconsistency issue in reaktor and not a error in my code is a lot of times, I've just drilled it into my head over the years.

I think the sine bank and the modal bank index at 1 instead of 0 as well, but I'd have to look to make sure.

PoorFellow

One of my long standing gripes about reaktors design is the inconsistency of index values.

IMO then that's really bad design, especially if they did not supply a referenced list of these inconsistent 'index values' and then left it to each and every user to have to compile their own list 🤔

.

gentleclockdivider

Max-msp has the same inconsistency for certain modules .

Mutlislider starts from 0 , gui matrix from 1 etc… or was it the other way around …