thank you for the reply! it doesn't have soft takeover in hardware, but it allows to change the CC that knobs send in hardware. so an example midi stream that the controller sends out might be (if you intersperse rotating the same knob up with changing its CC in hardware):moss wrote: Fri Dec 30, 2022 5:14 pmI am not sure if I followed everything you did but if I understand correctly you have a keyboard controller with a soft takeover in hardware? I guess this will simply not work since Bitwig is not aware of these values stored on the hardware device.mushrouxm wrote: Wed Dec 28, 2022 4:17 am edit2: well clearly i'm fixated, fiddled a bit more and thinking now that maybe it's a bitwig bug :/ i set up the generic controller script again, with different programs on the akai setting different ccs for the knobs. i change a device parameter with a knob, and catch or relative scaling are both working, then i change programs and reset the knob, change programs back to the original and it behaves as immediate againseems like bitwig's takeover setting is unable to understand any soft control behavior besides its own. any help still appreciated but might need to take this to the bitwig forums!
CC20 45
CC20 46
CC20 47
CC20 48
CC20 49
CC20 50
CC35 51
CC35 52
CC35 53
CC35 54
CC35 55
CC20 56
CC20 57
CC20 58
CC20 59
if CC20 is bound to a parameter with initial value 47, then that parameter's value when that midi stream is received would go
47
47
47
48
49
50
50
50
50
50
50
56
57
58
with a jump when the knob starts sending CC20 again. i also see a similar behaviour if the knob is always sending the same CC but i instead switch between volume and parameter modes in drivenbymoss
any help deeply appreciated!
...
