Ableton Live macro jumping to different values to that of Midi Fighter Wist
Ableton Live 11 or 12 beta macro values not tracking true to my MFT, when using MFT to change the value of an Ableton Live macro on a track then changing the value of another macro on a different track then returning to the first, the initial movement of MFT even only to the value of 1 will cause the macro to jump up and the jump is greater the higher the resting value that is changed.
MFT is set to factory reset, the controller template is from the CSS library and the script
Note MFT controller wound down to 0, CSS monitor shows 0 Velocity and the Ableton macro value is 0, however as the MFT encoder is wound up by 100 the Ableton macro has already reached a value of 127.
Havel also tried Control type Absolute and Relative as well as the various pickup modes as well as changing the Velocity Control Settings range to 100
The closest I’ve got to a 1 to 1 control was Value Scaling as I’m guessing it minimises the controller value discrepancy I mentioned earlier.
I would appreciate help in achieving consisttant a one to one response between MFT and AL macros.
Thanks
Could it be because the maximum Device Parameter Range is set to 126%? Try setting it at 100%
I would also suggest setting Controller Override back to default.
About Controller Override
For Controller Override, the default is the Absolute (Velocity) Value range from min. 0 to max. 127. This is the full velocity range a knob can have.
If you only want to use a small part of the knob’s range, (for example only the first half of a knob’s turn) then you can override this default by setting the Absolute Value range from min. 0 to max. 63.
Using a Relative (Velocity) Value allows you to divide the velocity range into steps (for example, if you want your knob with a range of 0 to 127 to be divided in 3 sections, so that the value change only happens when you’ve turned the knob a third of the way, then you can enter 3 into Steps).
Sign up
User registration is currently not allowed.