MidiBridge is truly awesome, but I can't get the Note Splitter to work for the life of me. I did manage to get two apps/instruments playing simultaniously on the entire keyboard, but that's about it. I tried switching MIDI channels and ports but to no avail.
Anyway, I'd like to use Note Splitter with any two apps I own (Animoog 2.1.1, iMini 1.4, Nave 1.3, Magellan 2.1, SampleTank 1.7.2) and would appreciate it very much if you could help me out. Ideally, it would be awesome if I could also make the audio output to some effects app such as improVox or EchoPad.
My music configuration is quite non-modern: ● an old Yamaha keyboard with basic MIDI functions ● MIDI nTour CX interface cable ● iPad 2, iOS 6.1.3
My version of MidiBridge is 1.58 (I don't know if that's relevant, but I also have Audiobus 188.8.131.52. – I saw a MidiBridge/Audiobus tutorial, but couldn't get it to work).
Finally, here is how everything looks like in MidiBridge:
There are many ways to organise splits across apps. Here is how I like to do it.
First and most importantly you need to configure each of the sound generator apps so that they only react to MIDI events coming from MidiBridge. You are probably experiencing the case where the apps are reacting directly to your controller which I assume is transmitting on channel 1.
My suggestion is to run each of your apps on separate MIDI channels starting from 2. Each app should be configured to listen only on that channel and (where applicable) each app's virtual MIDI port. Let's take your MidiBridge picture above and assume that you have configured Magellan to react on channel 2 and iMini to react on channel 3. Ensure also that in each of these apps that they are configured to listen to their virtual MIDI inputs.
Now, you need to setup the routing in MidiBridge. Touch 'MIDI nTour in' on left and then touch 'Magellan' and 'iMini' both on right. Touch nTour on left again to finish connecting. You should have green lines running from nTour to both Magellan and iMini.
Finally, do the splits; Touch the 'beaker' icon on nTour (left) and touch the (i) on the Note Splitter module. Press 'On' to enable and then set the Lower Split channel to 2 and the Upper Split channel to 3.
Often an app will always react to its own virtual port and the developers don't give you an option of selecting or deselecting.
So, in Magellan/Naves case, as long as no ports are selected then this should be exactly what you need. ie. you should not select nTour or MidiBridge as MIDI inputs in these apps.
For troubleshooting you could try each app separately (with the Note Splitter bypassed) and in MidiBridge connect nTour -> <App> and leave the app reacting to channel 1. If the app in question has no MIDI inputs selected and if you play your keyboard and the app sounds then you know the app is correctly listening to its virtual port.
In terms of Animoog, from memory, that is the correct way to configure it to listen to it's own virtual in.
2-3 seconds latency is very odd. Does the latency increase over time by any chance?
Again, very helpful tips – many thanks, Nic! I managed to get a few apps sound in MidiBridge when playing my keyboard with no MIDI inputs selected. (Pardon me for saying so but you either have a patience of a saint, or nerves like anchor chains. If only every developer was as responsive and committed as you.)
As for latency, unfortunately it is constantly there, even when I'm trying each app separately and setting it to react to channel 1 only (with the Note Splitter bypassed). Latency does increase over time – from 2-3 seconds to 10 or even more. Also, from time to time, some of the notes I played are repeated 20-30 seconds later.
Keeping my fingers crossed there's a workaround to this.