Mapping a macro resets its value to zero, any workarounds?

This is a pretty minor complaint but whenever I map a macro in a rack, the value of the parameter resets to zero, so I have to change it back to the value it was initially at. For example, say I wanted a filter cutoff mapped to a macro and its cutoff was set in the perfect place, mapping that to a macro for ease of use/performance later would immediately reset it to 20 Hz or whatever.

There are forum posts about it dating to 2009 so it's not a new issue, I'm just wondering if anyone has any tips for how to work around this so I don't have to re-set some often finicky parameter values. Thank you!

3 followers

pinklemon 8 months ago | 0 comments

2 answers

  • S.Rueckwardt
    contribution
    36 answers
    32 votes received
    1 vote

    Hi, yes you can use the option.txt file to implement a feature that the mapped Parameter are mapped with the actually value ... Lock at option.txt Features live 9 .

    WFG S.Rückwardt

    8 months ago | 1 comment
  • ChampDuggan
    contribution
    5 answers
    6 votes received
    1 vote

    you can also edit your midi mappings and set max/min values for each individual parameter the macro is controlling. the macro resets the value to zero because it is taking over for the instrument/effect/etc that you're modulating and it needs to allow itself full range of motion (0-127). you can invert the max and min so turning the macro up turns the parameter down, etc. there are a number of ways to find the value of the parameter, then just set values accordingly. there are excellent tutorials on youtube for this

    8 months ago | 1 comment

You need to be logged in, have a Live license, and have a username set in your account to be able to answer questions.

Answers is a new product and we'd like to hear your wishes, problems or ideas.