Ok, here are my observations/suggestions for the hardware “control view”. I have not dug thru the forum at all, so i’ll apologize in advance if these are already addressed or suggested.
First, i’ll start with basic suggestions in terms of naming labels. In the example of the “faders” element, the fader group can be renamed but the individual faders/knobs in the macro can’t be named. The macro dials indicate fader 1-4. These need to be freely renamed in the editor.
Now, I’m not sure if the limitations are “by design” or simply not implemented yet but there should be a better use of the macros to freely assign more controls. For example, creating an 8-dial bank element. Dial 1 (in the control view) could be assigned to dial 1 (like in the fader element) OR the last edited control in the macro view. Entering dial 1 macro view would give access to 8 nameable dials, any encoder click would revert back to control view, as implemented.
Another neat idea would be to implement a “shift” element assignable to buttons only. This would function as a second control per dial (in the control view and macro view). So, for example, if my dials layout in the main control view are: OCT/ SEMITONE/ FINE/ KEYTRACK/ MIX LVL/ PAN/ NOISE TYPE/ NOISE LVL, then a “shift” or associated “toggle” would be great in a 2 OSC synth scenario; Dial 1 controls OCT for OSC1, Shift+Dial 1 controls OCT for OSC2,… This would allow for a more structured hardware experience with less page jumping/preset loading.
I’m still REALLY new to this but my first project is to map CC controls for the Waldorf Protein… I did not do the math but I’m pretty sure that i’ll need several presets to achieve this. I completely understand if there are limitations to my suggestions. Thanks! Nicolas
