Live objects give false outputs

    redhexagonal
    Nov 06 2018 | 6:58 pm
    For a while (from before Max 8 ) I often notice that live.numbox and live.dial's output do not always reflect their value. If you move the value quickly it takes a short time for the output to catch up so, if I move a dial of values 0-127 quickly to zero for instance, it might output a value of 24. It means that i am never sure if I have truly zeroed a parameter, very annoying. Has anyone else notice this?
    • stoersignal
      Nov 08 2018 | 8:31 am
      yes, noticed that too
    • Gregory Taylor
      Nov 08 2018 | 3:11 pm
      Max for Live is running and doing its work in the Live application's low-priority queue, which almost certainly accounts for that lag.
    • redhexagonal
      Nov 08 2018 | 3:37 pm
      So... is there any way to ensure that live objects output reflect their displayed value? Is this a bug or a limitation?
    • Gregory Taylor
      Nov 08 2018 | 4:04 pm
      As I suggested, the problem is the lag time for the display of values, not their reception. I'm sure you can figure out how to add some patching to test that. Honestly, it's never been a problem for me - but I suppose that I'm not a big fan of lots of UI eye candy and fader-whacking at lunch-launching speeds. :-)
    • redhexagonal
      Nov 08 2018 | 4:20 pm
      The problem is the lag of the output value , not the object's displayed value. If i pull a slider down to zero, the output of the slider , which displays zero, doesn't always reach zero, and can stay as high as 40 for instance.