MIDI Boards - MobiFlight/MobiFlight-Connector GitHub Wiki

Content

MobiFlight currently contains ready to use configurations for the following MIDI boards:

[!WARNING]
For a not yet supported board, you need to create a new configuration file. Without a dedicated configuration file, only some basic buttons do work and user experience is limited. Follow those instructions.

Settings

Settings dialog is opened via Extras -> Settings -> Peripherals.

  • General MIDI support can be enabled/disabled.
  • Single MIDI devices can be excluded by removing the checkmark in the active MIDI devices list.

image

Supported MIDI boards

The MobiFlight MIDI board configurations are based on the default firmware configurations of the boards. Some MIDI boards require some minor additional changes in their device configuration, usually to be done with a configuration software from the vendor. Follow the descriptions in the respective board chapter.

As an alternative, MobiFlight ships ready to use firmware board configurations, which might be loaded in the board editors. They are installed to the following directory: yourInstallationDir\MidiBoards\BoardEditorConfigs. Use at your own risk.

Behringer X-TOUCH MINI

Productinfo: Behringer X-TOUCH MINI.

Download X-Touch Editor from Behringer Website. Software -> Editor for Windows V1.21. Or try this direct Link. Extract and run.

Necessary default configuration:

  • Fader is of type "CC". Exact configuration, see screenshot.
  • All Buttons are of type "Note". Exact configuration, see screenshot.
  • Encoder Turns are of type "CC". Exact configuration, see screenshot.

fader (Benutzerdefiniert) enoders (Benutzerdefiniert) buttons (Benutzerdefiniert)

Changes to default configuration:

The Encoders need to be set to “Relative2” Mode. Instructions:

  • GLOBAL → Get A
  • ENCODERS → Bottom Section → Set all “MIN VALUE” to Relative2
  • GLOBAL → Dump A
  • GLOBAL → Get B
  • ENCODERS → Bottom Section → Set all “MIN VALUE” to Relative2
  • GLOBAL → Dump B

encoderRelative

Akai MPD218

Productinfo: Akai MPD218.

Download and Install MPD218 Editor

Necessary default configuration:

  • All Pad Banks are of type Note. Note ranges are 36-51, 52-67 and 68-83.
  • All Knobs are of type CC. Ranges are [ 3, 9, 12, 13, 14, 15 ], 16-21 and 22-27.

defaultMPD218 (Benutzerdefiniert)

Changes to default configuration:

The Knobs need to be set to “INC/DEC 2” Mode. Instructions:

  • File → Load From Hardware
  • Set all Knobs to TYPE: INC/DEC 2
  • File → Send To Hardware

mpd218knobs

KORG nanoKONTROL2

Productinfo: KORG nanoKONTROL2.

Download and install KORK KONTROL Editor. KORG KONTROL Editor

Necessary default configuration:

  • Assigned CC numbers as in the screenshot
  • All Knobs and Sliders enabled
  • All Buttons need to be of Type "Control Change", Button Behavior "Momentary" and Off Value "0".

korgDefaultConfig

Changes to default configuration:

LED Mode should be set to “External”. Instructions:

  • Communication → Receive Scene Data
  • CONTROL → Common→ LED Mode: External
  • Communication → Write Scene Data

korgled

Akai MPK MINI PLAY

Productinfo: Akai MPK MINI PLAY.

Necessary default configuration:

Just take care that you are in the standard octave.

defaultConfigMini (Benutzerdefiniert)

Intech EF44

Productinfo: Intech EF44.

Download and install Grid Editor.

Save EF44 Profile to a json file like "Mobiflight-SessionProfile.json" and load in editor.

Create your own configuration for new MIDI board

Main MIDI messages are CC (Control Change) and NoteOn/NoteOff. Each message consists of a channel number, id and a value. Without a configuration file all Note and CC messages are mapped to Button press. To examine the default mapping, activate logging in MobiFlight via File->Settings->Logging:Enabled. Each message shows in a pattern like CHANNEL_ID. For example CC 1_50 is a Control Change message with id 50 and channel number 1.

image

For more detailed examinations use MidiMonitor and MidiMessageSender in SimpleMidiLib.

To fully support a new MIDI board, create a new configuration file in the MidiBoards subdirectory in the MobiFlight installation folder, similar to mpd218.midiboard.json. The "InstanceName" attribute must match the identification string of the MIDI board. Documentation of the parameters is in mfmidiboard.schema.json. A nice editor with json schema support is Visual Studio Code.

For support, or if you created a new configuration which shall be included, contact the developers in the MobiFlight Discord.