Midiflow for MIDI Mapping on iOS

Recorded on December 22nd, 2016


While pressing NanoStudio into service today, I realized that it doesn’t allow any control over velocity curves. A NanoStudio organ sample I was playing from the Alesis Micron sounded weak, because real pipe and electric organs don’t respond to velocity. If only I could filter out velocity messages from reaching NanoStudio.

Midiflow does this and way more! I remember 30 years ago reading a review of the Axxess MIDI Mapper in Keyboard Magazine. It allowed for a zillion ways to reprogram and reroute MIDI notes, channels, and controllers into any way you cared to twist them. Well now you can do this same stuff in an iOS app, and it’s much easier to program than the Mapper.

Midiflow is like AudioBus for MIDI. You can string together inputs, modifiers, and outputs with a different configuration for each song. And NanoStudio has a good enough MIDI implementation that you can force it to “listen” to Midiflow’s virtual MIDI outputs and ignore the system MIDI bus. Midiflow can also respond to MIDI program change commands, and it can even send commands (like its own program changes) to a destination app when you load a song setup. It has a MIDI monitor so you can see the actual numbers flowing out of a controller if you need to debug something. You can also set it to filter out some or all notes from reaching a sound generator. It’s just too great to even believe. If you have any kind of MIDI rig going with hardware controllers and soft synths in an iPhone or iPad, you need Midiflow.

blog comments powered by Disqus