[bug] slider offset misbehaves with negative values.
I just noticed a problem with slider when opening a Max 4 patch containing a slider using an offset.
max 4 inspector values:
slider range 128
output -127 – 0, as expected
imported in max 5, these are the values displayed in inspector:
output minimum -127.
output multiplier 1.
seems right, but output is -126 – 0
When I create a new slider in Max 5 the behavior is the same. When using a negative value, the output minimum in inspector needs to be set 1 smaller then the output wanted.
On 3 mai 08, at 17:05, Klaas-Jan Govaart wrote:
> I just noticed a problem with slider when opening a Max 4 patch
> containing a slider using an offset.
> max 4 inspector values:
> slider range 128
> offset -127
> multiplier 1
> output -127 – 0, as expected
> imported in max 5, these are the values displayed in inspector:
> output minimum -127.
> output multiplier 1.
> range 128.
> seems right, but output is -126 – 0
> When I create a new slider in Max 5 the behavior is the same. When
> using a negative value, the output minimum in inspector needs to be
> set 1 smaller then the output wanted.
Good catch! This has been fixed for the forthcoming incremental. Thanks,
I believe there’s still something wrong with slider.
See the patch: The range and minimum setting locate the value 0 at the middle of the slider. However when setting the slider with a "set 0" message, it jumps to the bottom (which would in fact represent -128).
Funnier still, when you send it a "0", the slider outputs -128.
----------begin_max5_patcher---------- 428.3ocuTFsaCBBEF9Z8ofv0VihUla2smikkFTYsznnAvF2Z569.Tq0Eylsq a2PB+b73+4ie8nqCLspkJgfm.u.bbN553XkLBN86cfkj1rBhzVFrjJkjsTnW 2YJZqxpGLn7VEWIYePMpgH+fdYdSIiWPU1tfFEqZTCpg8p0DU1NFe6FAMS04 MbrtQ.L1rFg7i8.gI9AfW6ehtlndul1UNDd9HVt0dUo6WgtzhbRosX3yBFo. ZN3jqqYw6WRBIUAlmFA2IZfB7QZDfe3BbfuZbDl7.99RDYAKmJF54Ah3bKUB BWVWIOSqI.H7FAPxiF.DZw.JdgDnlHztRQEanbRZgsfgqkgaJaylkXQCCf19 F8UgHcP7FXkdVSGY0RhIySIzORon3HCfhCrv5a+rgwUPO.Lkv2tLfMENqWVb x1YXAi+0+7XmAi9TtIqZDYCVbL4BFGjbpTw3DEqhOsrnIksikmS4W5+blzLR 1oX9awqvSQKySq+27D5uERc2ij55CTgruqVunS56qDlsXO2tuU51ZivPA8.a n9HqBQnytJcvsQzkYZSv5Di98bx8STHRGtD -----------end_max5_patcher-----------
This is actually the "correct" behavior. The minimum value is an offset applied at the output.
Today i faced the same problem. I can understand how the offset should behave, however, i think there should be a ‘message’ option which would enable the input value to determine the output value, directly. Is there a chance you to add this option?
Forums > MaxMSP