Great news! Thanks for the quick repsonse! Good to see you are keeping things up and not falling behind. Many good controllers out there atm, but the twister still does the job with style. Do keep us posted about the future & Good luck!
I managed to turn a low precision knob into a high precision one by sending the current value back periodically, and after each change, add up one tenth of the difference between new and old value to the old value. Sending the new value at the same moment when it was set doesn’t work, so I have to send it periodically. Then I can make it control any number range!
Now all is good! (besides of small inconvenience with missing magenta)
Trinitou did an implementation with RGB values and hex…
There is a fork in there… Doesn’t look too well documented but you can see how to use it in the bitwig extension.
I’ll keep the magenta issue in mind when I revisit the color palette. Thanks for giving it a try!
Cool! I’ll keep this one in mind too
Ended up not being the white correction but me bodging the palette mapping. I’ll ping you when i have another firmware to test
Midi_Fighter_Twister_MF64_colors_fix.hex.zip (37.3 KB)
@rasiel @Danielle77130 @Imaginus @kirkwoodwest Here is a new firmware file that actually matches the colors i shared before.
The sheet below shows the actual colors along with the rgb/hex ones. Still need some extra white balance tuning to get the most out of these. Might need to compromise white a bit so others show better/brighter.
Here’s a sneak peak on what I’ll be actively working on Twister in the next week or two. Studying on what is possible with the hardware and implementing it if it is.
- Select device number on the MFU instead of relying on extra firmware files
- More useable color palette selectable via the MFU, classic palette available to keep backwards compatibility
- Selectable channel for Shift encoders channel
- Sleep timer
- Bank change animations + bank indicator on change
- More than 4 banks ( 8 or 4+sequencer)
- Shift Page A/B toggle
- Native Mode
There will be a new MFU to go along with it which is mostly done which where we focused on fixing common quirks/bugs but more importantly, upgrading the code to 2026. Stay tuned
I just signed up for this forum so say that i am very looking forward to the new features for the MFT!
I just finished my Ableton Live Script which I might share at some point when I have the time to document the functions.
Thinking of keeping a similar dim/bright swatch on the MFU to what the other MFs do while in expanded mode for consistency and to make having dim colors not require the extra message on simpler mappings. Classic is what the MFU does now. Is this something you guys would find handy or would you rather have more unique color options instead?
Expanded
Classic
Awesomeness! I’ll try the firmware this weekend, thanks a lot!
Hard decision aboud the small palette, they both have colors I want 
Having more than 20 selectable colors in the MFU is something I’m adding later on with a bigger MFU UI redesign later this year. Spectra will get this palette too so it’s consistent across models.
Re Banks + Native mode
Native requires all encoder settings to be kept in RAM for it to be responsive so 8 banks is out of the question if Native stays. We have to keep in mind each encoder can have its own shifted state + superknob so virtual encoders alone take most of the available RAM.
That said, 6 banks is tight but possible. I do need to confirm memory requirements of one other feature I have planned for later on.
I can say for myself that i don’t use banks as knobs state is fully managed in software. Side buttons are bound to something else
I didn’t fully get what a native mode is, but if it allows me quickly change the type of knob without causing hitches, it’s what I need
Also, a side note, I personally think using this controller for tracks in ableton would be strange. It would be the best if it automapped to first 16 pRoarameters of selected device. And anyway, I find this workflow still very slow - I want to quickly add a vst somewhere and expect knobs do work for the most important parameters, but that’s how it works - you have to prepare in advance 
The colors are great.
One goal could be to match or be able to match the colors as near as possible to Ableton.
I myself am using 3 MFTs along Push and Ableton. Having similar colors would be nice because it would be easier so keep focus.
I am using 4 sends per track, Volume, Mute and 8 Parameters of a device along navigation controls.
Recently I looked up how to able to match the MFTs colors to Ableton. But I gave up.
I think consistency over the other product also is a valuable thing to consider.
I have 3 MFTs as I don’t like switching bans that much. So I would am good with 4. 4x16 is already much to remember.
But that’s just me thinking out loud.
Animation channels are now customizable via the MFU. I know some of you guys had some crosstalk issues
Hey there is there an ETA for the release of the updated MFU? I would also like a larger color palette and one that matches the Ableton track colors would be awesome as well!
We released it yesterday 
You can find all the changes and download links over here.
Ah wow I see thanks I have updated to 2.91.
Were the larger color palettes part of a later release? I still only see 20 colors per bank of two banks.
Make sure you have “Expanded” selected as the Color Map. The 20 colors displayed are the same as the other MFs for consistency. The rest are assigned via MIDI for now.
Being able to pick any from the MFU directly is coming later this year in a larger UI redesign since I didn’t want to jam more boxes in there making clicking the right one harder.
The updated User Guide has the new values on pages 4 and 26.
2.91 and the accompanying firmwares are a case of “let’s fix everything that’s wrong and get a solid foundation again” while 3.0 will be “let’s build on it”