MIDIbox NG

User Manual --- Installation

The MIDIbox NG firmware is released as a precompiled binary, which can be easily updated via USB MIDI by using MIOS Studio. Details about the bootloader are explained here.

Step by Step

it's assumed that you already tested the USB MIDI communication by pressing the Query button in MIOS Studio as explained in the Bootloader page - you should get some informations about the chip and the running application.
If this procedure sounds unfamiliar to you, please follow the hardware test procedure first as explained in the MBHP_CORE_LPC17 page.
download the latest midibox_ng_v1_* release package from the MIOS32 Download Page.
unzip the .zip archive.
load the MBHP_CORE_LPC17/project.hex file with the "Hex Upload" window of MIOS Studio and press the Start button.
the new firmware will be transfered to your MIDIbox.
once the "Upload completed" message is displayed by MIOS Studio (after ca. 20..30 seconds), your MIDIbox will reboot, and the new firmware will be started.

Now you could start to explore the capabilities of MIDIbox NG by going through the First Steps chapter, and/or you could try out some premade configurations which are part of the release package, and located in the cfg directory.

Working under Windows?

MIDIbox NG enables 4 USB MIDI ports. Unfortunately some windows versions can't handle this correctly: MIDI is stucking sometimes, Filebrowser operations are failing, etc.

In order to overcome this issue, sometimes it helps to install the GM5 USB MIDI driver, which can be downloaded from the MIOS32 Download page.

Unfortunately the GM5 driver can cause new issues if multiple cores are connected. And users reported that it doesn't work stable under Windows XP. In such cases it's recommended to force the usage of a single USB port which solves the MIDI transfer issues with the drawback of the reduced functionality.

So: if you notice MIDI transfer issues, please enable the single_usb option with the MIOS32 Bootloader update application.

Working under MacOS?

The USB MIDI implementation of MacOS is perfectly working, regardless of the number of USB MIDI ports!

So far we only noticed a minor issue when an app changes the number of USB MIDI ports or the device name. Such changes won't be taken over automatically, instead you've to delete the old interface description in the Audio-MIDI-Setup:

start the Audio-MIDI-Setup of MacOS (e.g. search for "audio-midi" with Spotlight)
disconnect the core module from USB
delete the interface in the Audio-MIDI-Setup
connect the core module to USB again

Thereafter you should see an interface with the new names and the right number of USB MIDI Ports:

Last update: 2024-05-08