Thanks for the input! So, here's a few things to know regarding brightness in this mapping. The light level (particularly sunlight) in one's working environment can seriously effect the visibility of colors and the contrasts in brightness on the Twister. Also, many of the layers have LEDs that brighten or dim depending on whether a parameter is active or not or on which deck flavor was chosen or whether a deck is loaded, to name a few variables. I basically used 4 different brightnesses on ch.3 LED output: 18–unlit, 24–dim, 36 and 0–normal, 48–bright. There's also the occasional use of lower numbers for blinking color LEDs and higher numbers for the blinking ring LEDs I don't know that there's a lot more I can do with brightness at this time*, but if you have any specific suggestions, please put them forward. *If anyone working on firmware updates is listening, it would be nice to be able to control the ring LEDs and the colored LEDs on different output channels (as with the input channels). That would open more possibilities.

As for coloring, my broad strategy in choosing particular colors and schemes was to help distinguish between layers (i.e. whether I'm on the mixer layer, which is mostly blue, or the tempo layers, which are mostly yellow and red, or the effects layer which can be basically any color on any LED) moreso than between individual knobs/buttons (hi eq, low eq or tempo master and sync on), particularly on layers where each column of encoders represents a deck and each row is the same action being executed on a different deck. On layers beyond this format, you'll see more distinctive colors between. Generally commands like tempo, syncing, and phase are in the yellow to red spectrum; mixer functions, cue points, track/stem decks are in the blue-cyan spectrum; looping is green; cue-ing, recording is pink-red; the remix deck is orange. With a mapping this complex, though, there are many exceptions as well. Again, specific suggestions are welcome.