automating M4L parameters messes up mapped controllers

    Feb 01 2011 | 2:03 am
    In order to be able to automate M4L parameters inside a midi clip, apparently I have to activate a modulation mode for the parameter. That done, when I map a midi controller to that parameter, if I have a parameter ranging from 0.00 to 1.00 , my midi controller selects only 0.00 or 1.00, with no values in between.
    If modulation mode is set to none, my midi controller will select a range of float values between 0.00 and 1.00
    Is this supposed to happen? It doesn't seem right.

    • Feb 01 2011 | 12:22 pm
      What do you mean with "M4L parameters inside a midi clip"? An example would be helpful.
    • Feb 01 2011 | 4:57 pm
      I have a M4L device whose parameters are controllable by automation envelopes within a midi clip. These parameters are also mapped to a midi controller. When I enable "modulation type" as "absolute" in order to enable automation within midi clips (otherwise I can only use parameter automation in the arrange window for some reason) the midi mapped controller will only control the parameter in integer steps, whereas before I allowed modulation of that parameter, i could control it in , I guess, 127 steps form my midi knob.
      This midi device has two parameters, one with modulation enabled, one not. if you map a midi controller to them both, one quantizes to integers, the other gives floats.
      I don't understand why.
    • Feb 01 2011 | 8:29 pm
      Ok, problem is clear and I can confirm the unexpected behavior. It seems that modulation modes and midi mapping are somehow not compatible. I think this needs clarification from the experts/developers.
      As a workaround one could use a dummy live.dial (with modulation disabled) for midi mapping and connect it to the modulation enabled live.dial. Not convenient but seems to work for me.
    • Feb 01 2011 | 9:31 pm
      One can also release the control from being controlled by the api, restoring the existing midi mappings, in my experience. g'luck j2k aka cfb
    • Feb 01 2011 | 10:12 pm
      That workaround will work, yes, but its very inconvenient...
      "One can also release the control from being controlled by the api, restoring the existing midi mappings, in my experience."
      i don't really understand what you mean?
    • Feb 04 2011 | 5:04 pm
      so is this quantizing of parameters a bug or is it intentional?
    • Jun 02 2011 | 3:32 pm
      Hello all, I'm not sure if I understood what you are discussing here, but someone talked about storing automation in midi clips. As far I understand "midi clips" in session view don't store parameter automation, they store the envelope that modulate the current parameter value in automation. Maybe one way around, is to use parameter modulation in unipolar mode and set all the parameters at maximum value, and then you have all the parameter range available in the modulation envelope. Please correct me if I'm wrong. I have also another question, I don't know if this the right place to put it. I would like to use automation as way set the parameter current value while something else is modulating around this current value, It seems that i can not read and set the value at the same time. If you use just live.object to read values, live turn "back to arrangement" red. If you combine live.remote~ and live.object to read and set value it's ok in ableton, but the scaling goes wild because you are reading and changing value at the same time. M4L don't give access to parameter modulation envelope, do you know any way around this, I think i tried all my options and I'm tired.
      thanks in advance.