MIDIFlow For iPhone Lets You Control How Your MIDI Is Routed

midiflowDeveloper Johannes Doerr has introduced MIDIFlow, a new iOS app that lets you send MIDI from app to app in a similar way to what you already do with audio.

That way, you can sync apps with each other or send MIDI parts from a sequencer app to different synth apps.

You can also route the MIDI from your keyboard to apps and assign different key zones to them.

In addition, all MIDI transfer can be monitored in order to find problems or just to learn what MIDI is doing (normally) behind the scenes.

Here is a demo of MIDIFlow in action:

MIDIFlow is available for US $4.99 in the App Store.

Note: This is optimized for iPhone.

If you’ve used MIDIFlow, leave a comment and let us know what you think of it!

18 thoughts on “MIDIFlow For iPhone Lets You Control How Your MIDI Is Routed

    1. I like this UI and I hate midi bridge to look at ! Session save is planned according to developer so this will be useful for me…

  1. This is a long-overdue utility! And a nice first release. The demo vid does a good job of explaining the limits of its functions and the relationship to how apps receive MIDI data.

    There is room for a little bit of tweaking. For example, being able to play two notes to set range is pretty basic. It would also be quite nice to be able to use velocity switching to change change MIDI channels– not that this would be used all the time, but could be a handy function. The other stuff– like being able to reassign controllers, trigger CC streams (like LFOs, ENVs), or even manage some clock stuff would be very useful, but could get quite messy.

  2. Yep… midibus and midibridge both do this just fine. Could be wrong here but I think midibridge has more capabilities especially with controllers like the BlueBoard.

    This is where apps are at right now. So many effects apps and midi and synth apps have been done now it’s just becoming an endless supply of copies. Oh well, more power to them. Apps have been given a lot of crap from some musicians, but like all new tech they will eventually be embraced,used and copied to no end.

  3. I like ipad, got the latest, and use audiobus 2 a lot, but it crashes often, and I cannot compare the sounds with the pc softwares soundqualtiy (native instrument), witch is boring

    I had a concert recently with only ipad and it worked well, but I was limited to what I could do

    the most fun is to use turnado as a filter in audiobus and to controll my hardware synths with ipad and midi

  4. looks very easy to use and handy indeed, does anyone know how it would work with iconnectmidi? My 4+ still hasn’t arrived yet, so I can’t try it out yet, but from what I’ve seen iconnectmidi has its own app, but I’m not sure if they would conflict with each other or do the same thing?

    1. iConnectMIDI has its own routing features which are implemented on the hardware and controlled by their app. In order to use Midiflow, it is best to disable all routings in the iConnectMIDI first.

      iConnectMIDI’s routings are very basic, but super-fast, because they are implemented in the interface’s hardware. iConnectMIDI can only route between its (external) ports. With Midiflow, the routing is done on the iPad’s processor (but is still fast enough for most uses). It can not only route between external ports, but also between apps.

      1. So does this make it a complete alternative to using the iconnect routing system? Its got powerful features but I don’t like the interface and I don’t think its laid out logically and this definitely seems to be nicer from the GUI side.

        1. After using both over the weekend they can augment each other nicely. I’ve still kept my iConnectMIDI4+ routings since they don’t deviate too far from the stock configuration much. MIDIFlow helps me easily visualize all the message flow once it lands on the iPad and in one interface without having to jump around from app to app. Looking forward to working with it more. Good job!

Leave a Reply