I was thinking about ways to get around the limitations imposed by the design choices on the KeyLab MK3. Right now the main encoder wheel is set when turned to use CC28 that it seems is the HUI midi channel for selecting a track. Looking on my minilab3, if I hold down the shift key then it remaps my main encoder wheel to use CC29 that is used in the HUI midi channel for transport shuttle on a track… or to move back and forth along the length of the track.
Now I am told by Arturia that asking for a feature change to the KeyLab to for example use the contextual screen button 7 (that is currently not used) to add in similar shift key that will allow the main encoder to shift to dual duty and toggle between. CC28 and CC29 like is done on the minilab3 is a non starter as then there would be two methods of moving on the controller (even though they use totally different midi control methods) and would be too confusing for the average user (musician).
Is there a way to reassign the default setting for example Encoder1 in DAW mode to use a different CC-id on default? or is the DAW mode preset and cannot be changed? I am not sure if I can replicate the whole DAW mode on a user program except with one of the encoders changed to use CC29 so I can get a workable transport shuttle on a track.
just trying to figure out a work around to see if there is a way to use the KeyLab if I can solve the buffer I/O issue