[Beta Program] Midihub Review by tob_har

Hey MIDI People,
this review is the result of me Tobias (tob_har) and Max from CYLVESTER testing MIDIhub together within our setup.

We recorded two videos on how we got issues solved with MIDIhub.
Feel free to take the shortcut by scrolling straight to the videos linked below
or read through some more details and thoughts on MIDIhub before watching them.

First Impressions and a brief description

MIDIhub is a rock solid (metal!) piece of gear for handling MIDI data in many different ways.

It connects to other MIDI equipment via 4 MIDI DIN IN and OUT ports and it can also act as a USB to MIDI interface at the same time.

MIDIhub is powered via its USB port and has its own dedicated power switch.

Eight bright and beautiful LEDs on the top give instant information on MIDI data that is being processed.
They also display the current active preset.

MIDIhub running DAWless

Within the MIDIhub Editor software it is super easy to choose and edit all functions, MIDIhub should perform standalone (!). So it is up to you to decide what MIDIhub is actually capable of.

By now, MIDIhub can perform merging, splitting, routing and various processing of MIDI data, like filtering and remapping.

8 different presets can be stored in the device. They are selected by pressing a button on the device (dialing through all presets) or via MIDI messages sent to MIDIhub.

Each preset represents a whole setup of MIDIhub which has been created in the Editor Software.

As a bonus: changing presets can be done on the fly without any interruption of current MIDI processing.


MIDIhub can act as a MIDI to USB connector between DAW and MIDI gear.
But it still is a MIDI merger, splitter, filter and router at the same time!

So you can realize even the most complex routings between the four DIN MIDI IN and OUT ports and the USB port.

It can transmit 4 virtual USB MIDI streams over its single USB port, which can be very helpful when working on MIDI routings with multiple software and different hardware involved.

The MIDIhub Editor is easy to use because of its graphical and self-explaining interface.

The Editor features so called pipes. These are MIDI event functions, that can treat the MIDI signals in different ways.

Using these pipes, MIDIhub can perform advanced and stacked functions such as MIDI channel remapping, MIDI note remapping, clock division, MIDI data filtering, and many more.

… and there will be even more useful pipes to come in future updates!!!

How we use and test MIDIhub in our setup

My colleague and friend Max and me tested MIDIhub within the running live setup of our duo CYLVESTER. We play electronic music live without a computer, DAWless, so to speak.

Our setup consists of sequencers, synths, samplers, FX processors and a digital mixer all of which are interconnected within a complex MIDI network. Watch our CYLVESTER-Documentary to learn more, about our hows whats and whys.

After a lot of work, our whole setup is now up and running as is, but for this review, we chose to focus on two issues, that we still have with our setup and that we finally got solved with MIDIhub!!!

During testing, it turned out, that we could replace all our current MIDI merging and splitting devices by only one MIDIhub. We were surprised how fast and easy we got everything improved.

Problem 1: MIDIhub as MIDI Program Change Filter for Master-Keyboard

Have a look at how MIDIhub made Maxs life much easier during recording:

Problem 2: MIDIhub as MIDI Channel Remapper for Master-Keyboard

Here we want to show you, how MIDIhub made the MIDI live-recording process on Tobias part of the setup way faster, more failsafe and less annoying by using the MIDI channel-remapping pipe:

How could MIDIhub be improved?

  • USB port for class compliant devices - We would love an additional USB port for USB MIDI class compliant devices like controllers, pedals, master keyboards, etc. Using additional Midi-USB-Converters is simple, but adding such a port (like on the Axoloti) would change the way we can interact with our instruments entirely! It could change Dawless-Electronic music making.

  • Labeled Ports - It would be useful if all MIDI ports where labelled on the sides of the device. They are clearly labelled on the top… but we use to stack devices in our live rigs. Once the hub is covered with another piece of gear, you have to be very carefully where to plug new cables.

  • MIDI note dispatcher pipe - The most wanted new pipe in the Editor would be a MIDI note dispatcher, that would allow polyphonic spreading of MIDI notes received on one MIDI channel to multiple different MIDI channels and/our MIDI output ports. With that feature, we could use the Elektron Octatrack also as a polyphonic sampling-instrument, or treat multiple external monophonic synths as a polyphonic one.

  • Codable Pipes - It would be awesome if the MIDIhub team would find a way to let the community write their own simple code-functions for MIDIhub. Possibilities could be endless.

Final words

MIDIhub is an incredibly versatile MIDI router and processor which is developed by a very ambitious team that cares a lot about its users!!! And this really is one of the most important features.

120 - 150 € seems to us as a fair price for a tool that replaces splitter, merger, processor and a MIDI-USB interface.

We are looking forward to future versions and iterations. But for now, we already fell in love with the tiny grey box and its huge potential in the MIDI world. MIDIhub already is a killer tool to look out for!

Thanks blokas!


Tobias Hartmann

Max Schweder


@tob_har this is pure gold! :blush: Thank you so much guys for spending your time creating these videos and the write-up. :hugs: It’s really gratifying to see that the Midihub is helping improve your workflow! Give Max our best!

P.S. We definitely need to add “Select/Deselect All” buttons for the Filter Pipe. :slight_smile:

Thanks a lot for your whole introduction of the midihub. very much looking forward to work with it myself very soon.

You address something that I’ve waited for being able to implement in my dawless setup.
Do you need to unmute the Nord on your mixer in order to just play the remapped channel? Or is that a specific function of the Nord, to be able to play it without the internal sounds?
In your video I cant really tell, if you also play the internal sound while playing notes into your octatrack.

thank you in advance!

Most synths with a keyboard and/or internal sequencer/arp, will have a local on/off function.

With local on, playing the keyboard/sequencer will play the internal synth and transmit the notes as MIDI.

With local off, it will only transmit MIDI. The internal synth can then be played by yet another keyboard/sequencer, which is all kinds of awesome (and will be a lot easier to route with Midihub)


Hey ony,

thanks for your question!
I hope I get it right but Ill try to answer, as I understood.
also the point that @alexander mentioned is an important aspect when choosing how to build your audio/midi setup.

In this Video (MIDI Channel Remapping) I am only referring to MIDI notes and never Audio.
In this case I use the Octatrack NOT as a sampler, but only as a MIDI sequencer.
All you hear, is sound produced by the NL4 and it is triggered by MIDI notes coming from the Octatrack. Recording notes into the Octatrack means, recording MIDI notes into the Sequencer.
Maybe this gets a little bit more clear in this video from the series my colleague Max and I did to introduce Midihub:

My Setup is in this case like this:
NL has 4 different Layers, it behaves like four times the same synth in one instrument.
Every Layer can be triggered/played via MIDI on one specific MIDI channel. (I use three of them, listening to the MIDI channels 14, 15 and 16).

But the NL can output only one MIDI channel, which is 13 in my case.
So when I would play the Nord lead as it is, I would hear just on of the four layers.
But when using MIDI hub, the information coming from channel 13 gets addressed to channel 14 and send back to the Nord Lead. In this case, only the second Layer of Sound is beeing played.
(The keyboard of the Nord Lead then just behaves as an external MIDI keyboard)
Same for the other two layers.

Hope that this helps a bit…


hey @alexander and @tob_har,
thank you both for your ideas and answers!
I think i got it right and just discovered that my r3 has the local on off in the midi menu :))
Thats already an advantage i wasn’t aware of.

So I guess the best way to be able to not only play all the different midi notes (and switching different channels with the button) but also the internal sound would be looping the midi back into the r3? In order to not needing to menu dive for the local on/off?
Is that possible? like playing on ch9 (with local off) but if it hits back on ch9 it will play “locally”? If thats something thats specific to my synth I guess I’ll just try.

–you kind of answered that one, sorry if I misunderstood it in the first reply–

I use a digitakt for sequencing everything and basically search for an option to use the r3 as a master keyboard for all the different instruments (midi channels) in my setup including the r3 as an instrument.

I’m planning on doing this exact thing, once I receive my midihub. You can try it out yourself by setting your synth to local off, and connect midi out to midi in on your synth. If it makes a sound, you are golden:)

1 Like

it just became a golden synth :dizzy:

1 Like

nice!!! :slight_smile:
… that little grey friend is just awesome!
You should check out, that nearly all the features are also controllable via MIDI CCs remotely…
So you can even avoid pushing and maybe map this function to a more suitable controller.

1 Like