ok we're officially no too smart onesYokai wrote: ↑Fri Jan 18, 2019 6:00 amThat's a neat trick, and TBH I had overlooked the MIN/MAX aspects of the Math modulator! But it's also kinda counter intuitive, and look how you had to set up THREE different modulators (and puzzle out the the inter-modulation among all three, and empirically "test" where to set the 2nd knob in both Math modulators) to do what in Ableton is a simple and very intutive matter of setting a specific min value and a specific max value on a single macro knob.xbitz wrote: ↑Fri Jan 18, 2019 5:45 amhmmmYokai wrote: ↑Fri Jan 18, 2019 4:56 am....
In Ableton you can easily specify min and max ranges for a macro knob (for example) in an "inspector panel" kind of way. But the Bitwig design principle is to make such details more VISUAL. They prefer you to set some target knob to its min (or max) value, and then assign a macro modulator to it and VISUALLY just set where range of movement should end, relative to that starting point. Yes, they do give you an inspector panel for the modulator to adjust that visually-assigned "range" value, but you have no way at all to fine-tune the starting value of the target knob. The Bitwig design always requires you to touch two different things to effectively set the exact min/max for a constrained range of values.
the routing is for homework
btw. the quantize (QUA) operator is missing from the docsso it even works using discrete steps too18.104.22.168. Math
One control source derived from two continuous knob controls. The output signal is a mathematical relation of the two signals, which is derived either by MUL(tiplying), ADD(ing), or SUB(tracting) the two signals, or simply taking the MIN(imum) or MAX(imum) of the two values.
done, and the non-documented QUA operator
also lovely, and it's still not absolute "just" asymmetric quantised relative modulation, respect to Bitwig