hello,
in a rack, when you map a parameter to a macro-knob, the current parameter-value is overwritten because the "macro-morphing-range" is set to full range: is there any way to change this behaviour?
macro-controllers would be so much more fun if you didn't have to remember the current value and punch it in manually.
on the other hand, if you WANT the mapped parameter to be macro-controlled full range and lose it's current value, it's only one click.
i have done a quick search for this topic on the forum but couldn't find a related thread.
anyway, i apologize if this has been asked before. i was hoping that this might change with live 10, but didn't ...
all the best from vienna
illinx
why must parameters lose their value when mapped to a macro?
why must parameters lose their value when mapped to a macro?
Last edited by illinx on Fri Feb 09, 2018 4:25 pm, edited 1 time in total.
Re: why do parameters lose their value when mapped to a macro?
Thats how it works....
Cheers
D
Cheers
D
Re: why must parameters lose their value when mapped to a macro?
that's pretty accurate ...
but does it have to be this way ? : )
greetings!
but does it have to be this way ? : )
greetings!
Re: why must parameters lose their value when mapped to a macro?
I’d love to see this changed myself.
tarekith
https://tarekith.com
https://tarekith.com
Re: why must parameters lose their value when mapped to a macro?
This is very annoying and shouldn't happen. Ideally on first map macro knob shoudl align to target.
Trance producer, DJ, sound engineer, synth programmer
http://djwarmonger.wordpress.com/
https://open.spotify.com/playlist/1vgP3 ... zUR4MpD4Sm
https://soundcloud.com/djwarmonger/
http://www.mixcloud.com/Warmonger/
http://djwarmonger.wordpress.com/
https://open.spotify.com/playlist/1vgP3 ... zUR4MpD4Sm
https://soundcloud.com/djwarmonger/
http://www.mixcloud.com/Warmonger/