Midi Fighter Utility 3.0 Beta

What can be done is having the shift encoder re-use the switch’s MIDI number and channel when “Disable switch Shift MIDI” is enabled"

thanks for the reply, this would be perfect! exactly what i need. not much else i’d add at this point, perfect midi controller!

Great news !
Hope you will keep the compatibility with mf3D :folded_hands:
I had a big issue using mf3D and RME Digiface lately. Hope it will be once in a time and never happened again.

Not planning on dropping 3D support anytime soon. It’s fully compatible with 3.0 and we already issued a firmware update not that long ago. As I said on another comment. I should be able to work on 3D firmware post Black Friday launch but a friendly reminder that 3D’s LEDs are a fair bit dimmer than the Spectra/64 so the color specific bits won’t look as good.

If you can describe the issue you’ve had along with firmware date, mfu version and OS I’ll happily help troubleshoot.

MF3D_MIDIServer_fix.md.zip (4.3 KB)

Here is a markdown of the issue I got, with how I solved it (using LLM)
For a venue I used my RME digiface Dante (all worked fine)
Back home reconnecting everything to my RME Fireface 802
And then each time I connect the mf3D all the Midi Server on my MacBook Pro went down (osX 26.7)

New beta release is here!

Download the new utility and Twister firmware via the links below.

Utility 3.0b

  • MCU display (macOS only): select View, then MCU Display, or press Cmd+Shift+M. A floating window shows a virtual MCU display to complement Twister. (MFU must remain open to use this)

    Fixes menubar issues on Windows
    When editing multiple controls at once and reassigning the MIDI number or function they can now do it sequentially rather than applying the same number to all selected controls
  • Labels have two lines on the Twister: the rotary on top and the button below it. Right clicking on a control to rename has a field for each line.
  • Both Action Type lists are in alphabetical order. Saved settings do not change.
  • Rows that do not apply to the selected action type are hidden.
  • A device opens on the Device tab.
  • Fixed uncommon crashes during flashing or reconnection

Twister (20261001) - Download

  • Adds MCU protocol messages, allowing Twister to emulate a Mackie control surface on any software. A mfu file with the controls preassinged can be found over here.
  • Adds program change messages
  • Customizable detent size and dead zone
  • Reworked white color calibration (plus the base calibration is closer to white for more people)
  • RGB LEDs are ~25% brighter allowing better differentiation between the different dim and fully lit colors.
  • Shift encoder switch MIDI note can be disabled. this allows customizing the shifted encoder MIDI numer too
  • New “Disabled” action for encoders and encoder buttons that discards the hardware input (exiting I know)
  • Bank 1-8 side button actions can be held down to act as shift layers and return to the previous bank on release. A quick press still jumps to the bank normally. (This kinda makes the old dedicated shift layers redundant)

Thank you! Any chance of seeing 14bit midi soon?

Proper 14 bit MSB/LSB support is still in development. I don’t want to implement it just so it can be a bullet point in the product page and the experience be subpar.

MCU uses pitch bend messages (14-bit) for it’s faders so you can give that a taste of your software supports mapping pitch bend. Relative encoders can also send different velocity messages depending on speed which yields a similar effect.

The truth is the only way to have it feel natural it needs to be responsive to movement speed, else it’s either too course or too slow. The limitation here are the number of steps Twister sends per turn.

May I ask what software/hardware are you planning to control with it? If it’s Ableton then you’ll want to check out the new control surface script that will get posted here next week, that has context aware resolution like Push and results in even tighter control than 14bit can.

Long story short: it’s high in the feature request list, no ETA yet.

Thank you for the answer! I will try it soon.

There was a quirk specific to how macOS26 enumerate’s the 3D’s device name (macOS27, Linux and Windows were unaffected). I pushed a new firmware live that targets this directly.

  1. Open the MFU with your 3D connected and follow the prompt to update firmware (if you are on 3.0 click on the red dot in the device manager dropdown to update, orange Update button on older app versions)
  2. Let it do it’s thing
  3. Disconnect the 3D after the update is complete
  4. Repeat 1-3 for each unit if you are using multiple
  5. Once all unit(s) are updated open the Audio MIDI setup app and delete ALL “Midi Fighter 3D” entries
  6. Reconnect your 3D and the issue should be gone

Note: If the MFU is having a hard time detecting it before flashing then reconnect the unit while holding the 4 corner arcade buttons to put the unit in bootloader mode, flash the recovery firmware and then update.

I followed your instructions.
All is (still) working fine.
Btw the new mf utility is really nice. Good job.