The firmware design is fairly decoupled so it would not be too difficult to provide external control of the LEDs.
I have no experience with norns/touch designer, what is the control mechanism? I assume midi sysex. Perhaps someone could link some documentation or provide some insight.
The current design of the firmware provides 3 banks of encoders, each encoder has two assignable parameters (which can operate individually via toggling, or simultaneously), so a total of 48 parameters:
- 16-bit internal values (the encoders themselves are not 16-bit, but this provides the possibility of handling 16-bit parameters using acceleration and interpolation).
- Configurable operating arcs - each parameter can operate within a defined region of the encoder rotation (overlapping of the parameters is also supported).
- Configurable value ranges - you can limit the number range of each parameter, for example with Midi CC you could limit the range from 10 to 100.
- Midi Follow - parameters will be updated with MIDI data received from the external device. I have tested this in Bitwig using the DrivenByMoss extension to configure each parameter to modify a device parameters - any changes in Bitwig are represented on the controller.
- Display Modes - still a work in progress but I have something that closely resembles the original firmware. I am working on a mode that displays both the parameters at the same time but its complicated…
- Midi - you can set any channel, any CC for each parameter (was always a bit confused why this was not in the original firmware).
FYI this is a clean implementation from the ground-up, the project is setup to use vs-code and is fairly easy to get up and running (if you are on linux).
May I ask that if you have a feature request you create a ticket in the Issues on Github so that I can keep track.
6 Likes