live.slider cannot be set without outputting values ??

    Dec 27 2013 | 12:14 am
    is it me or live.slider doesn't take message (set) for only changing value without outputting it ?
    (discovering things every day omg)

    • Dec 27 2013 | 12:57 am
      I just tested it, seems to work for me - did you do a "set $1" with a float going into it to test?
    • Dec 27 2013 | 1:56 pm
      Hi @wetterberg, yes I did of course.
      apparently, it occurs in m4l only here. we all noticed some (few) inconsistencies when we are patching (edition mode) and we are playing (live as runtime mode)
      and apparently, it doesn't occur in playing mode, which is fine. anyway, this is VERY strange :)
    • Dec 27 2013 | 3:10 pm
      Hi Julien, in theory the set message works for live.slider and live.dial. In practice though if the set messages arrive too fast those objects put out values occasionally. This is due to their implementation in the Live undo history. I had some conversation about this with support a while ago. Unfortunately they don't consider this a a bug, but as a flawed behavior due to the implementation. So there are no fixes to be expected any time soon. The way i work around is not very elegant: closing a gate preceding the ui object and opening it after the value has been set. Merry Xmas!!
    • Dec 27 2013 | 3:13 pm
      Dear Jan, thanks for this answer. Indeed, it lights this thread on.
      Which is very strange is that I use [live.remote~] and I have the live.slider itself "hidden" for automation so it shouldn't deal with the UNDO part at all.
      Yes for the closing/opening gate. not elegant but working fine, which is the point :)
      Merry Christmas to you to :)
    • Dec 27 2013 | 3:20 pm
      Maybe i didn't recall properly the explanation from cycling. I think their words were something like "the data take a round trip through Live". Whatever that might mean in detail... :)
    • Dec 27 2013 | 3:22 pm
      ... Lo siento for all the typos. I am an my crappy mobile ...:)
    • Dec 27 2013 | 3:22 pm
      anyway, that explains well why the behavior would be different from Max to Max for Live...