Hello. A great feature would be a possibility to change a default colour of a CV level.
Change a level indicator colour
Hi @patrykt and welcome. Would you mind giving a bit more detail on what you mean there?
Control mode is always red but I want it to be white because then the module looks prettier 
9 months later
I was brought to this post through a web search. I don't really care how "pretty" my Gliss looks, however I would like to be able to change colours of the different indicators in order to better differentiate them.
I have two Gliss and the Red, Orange, and Yellow states for settings look very close to each other. I understand I experience some level of colour insensitivity. Basically, for myself, the Red and Orange are almost the same, while the yellow is hardly different from the Red.
Can the colours be changed in software or are colors determined by LEDS on the module?
I also read in another thread that the front panel has something to do with colour visibility.
- Edited
The available palette is limited by the interaction of the RGB led colors and the faceplate's color-dependent absorption. In the first batch of the module, the faceplate absorbs most of the blue color, so that blue is visualised as a pale white and even purple is hard to distinguish from green. This restricted our available color choices to red, orange, yellow , green, white. And yes: it's not always easy to distinguish between red, orange and yellow, especially if someone is experiencing some form of color insensitivity. We did limited testing with self-reported color-blind users before release and they reported they were able to distinguish between the colors,but I am understand these conditions can be pretty unique to each.
Our solution to address forms of color-blindness has been to add what we call "animations": with animations enabled, tapping a selector will result in an animation being played on the screen which should inform the user of the setting they just activated, similarly to the per-mode animations that are displayed on mode change. This also benefits users who can reliably recognise colors but don't remember what setting corresponds to each color.
To enable these , enter the global settings menu and hold press the middle selector, this will start pulsating indicating that animations are active. Repeat the procedure to disable if needed. I understand this is only a partial solution to the issue in that you may not be able to recognise the current state of the menu by simply looking at it.
Now, to get to your question, colors at the moment can only be customises by editing the code and uploading it to the module. This is not necessarily straightforward to do currently, but we are working on a web-based update application that should make this easier and possibly even allow to customise colors via midi (can't promise that right now).
Modules that came after the first batch have a faceplate that allows a wider range of colors to pass through and in this case the blue color looks like an actual blue. However, we kept the exact same firmware across versions in order to maintain consistency in the documentation, so the colour palette hasn't changed, except for the color of the white/blue selector.