-
Notifications
You must be signed in to change notification settings - Fork 5
FB_MFT_RGB
This feedback processor allows you to send specific color values to the MIDI Fighter Twister (MFTwister for short), and the information in this page is only applicable to this device.
Note: Within CSI, only the buttons on the MFTwister can be colored, not the encoder rings themselves. This means the below section will only be applicable to the button/press widgets.
Let's say you've got a button widget called ButtonA1 on your MFTwister, and it's at the address b1 00 7f. If you would like to take control of the button color within CSI, you would first open the .mst file and setup your widget to use the following format:
Widget ButtonA1
Press b1 00 7f
FB_MFT_RGB b1 00 7f
WidgetEnd
Do this for any buttons you would like to control the colors for. This just tells CSI that the colors for this button can be controlled within CSI. We will define the color values that get linked to a particular action in the .zon files so continue reading below.
Background: the MFTwister color settings are a little tricky. From Geoff, "the RGB table is such that any one colour (r, g, b) MUST be 0 AND any OTHER colour (r, g, b) MUST be 255 -- the third colour can vary in the range 1 - 255 or so -- the colour table is a bit quirky." So for any state (i.e. off/on), two of the 3 colors must be 0 and 255.
Following your action, colors must appear in curly brackets following the action and require a space after the first bracket and before the last one. The first 3 numbers in the brackets are the RGB values for the off state. The second 3 numbers are the RGB values for the on state.
In this example, the color will change from deep blue (off), to light blue (on) based on the Playback state in Reaper.
Zone "Buttons|"
ButtonB8 Play { 0 25 255 0 189 255 }
ZoneEnd
In this example, from an FX.zon, the MFTwister button will turn green when the effect is on, and red when bypassed. If you wanted green in the off state and red in the on state, you'd flip the order of the first-three numbers and second-three.
Zone "VST: AR-1 (Kush Audio)"
FocusedFXNavigator
Toggle+ButtonB8 FXParam 0 "Bypass" { 90 255 0 255 50 0 }
ZoneEnd
Let's say our fx.zon includes some unmapped encoders and you want to give yourself some visual feedback that says, "hey, ButtonsB1 through ButtonsB3 have nothing mapped to them." You could setup your fx.zon files to include a color for this. This way, when you see the color, you know there's nothing mapped to that parameter.
For example, here I'm a dummy FX parameter (parameter 999 doesn't exist for this plugin) combined with Navy Blue to indicate there's nothing mapped to an encoder or button:
ButtonB1 FXParam 999 "Dummy" { 0 25 255 0 25 255 }
ButtonB2 FXParam 999 "Dummy" { 0 25 255 0 25 255 }
ButtonB3 FXParam 999 "Dummy" { 0 25 255 0 25 255 }
Now, let's say I want the light to turn green under any mapped rotary encoders. You can use the same method as above, when combined with your normal widget action. Example: here, RotaryA2 is mapped to a stepped ratio control of a plugin. At the lowest ratio, the encoder rings don't light up. So how would I know that encoder is mapped to something? Well, I can light the button below it green by doing the following:
RotaryA2 FXParam 5 "Ratio" [ 0.0 0.34 0.67 1.0 ] //these are the parameter steps not the colors
ButtonA2 FXParam 999 "Dummy" { 90 255 0 90 255 0 }
Lastly, to save you the time and effort, here are approximations of the MIDI Fighter Twister Utility's color codes, adapted for use in CSI.
R G B
Navy Blue 0 75 255
Dodger Blue 0 145 255
Deep Sky Blue 0 215 255
Aqua 0 255 255
Spring Green 0 255 135
Lime Green 25 255 0
Bright Green 90 255 0
Spring Bud 165 255 0
Yellow 242 255 0
Selective Yellow 255 188 0
Safety Orange 255 115 0
Scarlet Red 255 50 0
Tarch Red 255 0 80
Hot Magenta 255 0 225
Magenta 255 0 255
Psychedelic Purple 240 0 255
Electric Purple 165 0 255