strange behavior with [live.observer id]


    Jan 02 2017 | 3:20 pm
    I'm experiencing some strange behavior with an object that I found inside a very functional albeit confusing patch that I found a long time ago as part of one of the standard M4L devices included in Live (I think). It's a patch for manipulating a single parameter in another device that exists in the live set. What I don't understand is that there's this object written like this:
    [live.observer id]
    it takes an id in its right inlet and passes an id out of its left outlet. The intended behavior seems to be that when it gets an id it outputs that id and then outputs the id again when something in the set changes. The strange thing is that when I create an identical object and hook it up the exact same way, it does nothing. Even if I just copy and paste the existing object, the copy doesn't work but the original does. This is baffling to me, is this some sort of deprecated behavior of live.observer? That it resends an id when the subject of that id changes place? And this particular instance of [live.observer id] only works because it was created in a previous version of Max?

    • Jan 05 2017 | 12:53 pm
      Anybody know anything? Would like to hear from C74 on this
    • Jan 05 2017 | 1:43 pm
      if you save and reopen the device after you've made the changes does the [live.observer] then work?
      if so this is a known issue (bug) with [live.observer]. it's why i've stopped ever using [live.observer] with arguments. i.e [live.observer id] [live.observer name] etc.
      i now always send the property to the [live.observer] object as a message.
      using [live.observer id] etc with the argument also stops the object working when loaded dynamically via [poly~] or when loaded via scripting.
    • Jan 08 2017 | 2:00 pm
      Myr thanks a lot for your answer, this fixed the problem for me. It stopped working after a while and setting the id as a property with a message fixed it. Cheers