I have an iRig BlueBoard bluetooth foot controller that would be much easier to use with the Loopy looping app if it sent on-on commands rather than on-off commands. This means that I have to press the button twice to start and stop loops, making timing much more difficult. Can MidiBridge convert the BlueBoard signal (signals are routed through BlueBoard 's own app) from on-off to on-on and pass it along to Loopy? How difficult would this be to set up?
I have a few general questions before I get started If I'm using MidiBridge, will it handle all of the connections among my equpment and music apps? For instance, will I have to establish a connection between my guitar input (Apogee Jam) and effects app (JamUp Pro) in MidiBridge or willl that work the same as it has previously? Once I link the BlueBoard and Loopy, will I create the "bindings" for the various BlueBoard button presses within the Loopy app as I normally would? Will MidiBridge work each time I use my iPad without further programming? Is there a particular order I should use in opening the associated apps? Thanks for your help. I am pretty new to all of this, so although I have read some of the suggested articles, it's kind of like a foreign language at this point.
1) The signal between the apogee jam and jamup is audio, so MidiBridge will not come into play at all here.
2) Yes, once MidiBridge is setup as described, then you need to 'teach' Loopy what you want each button press to do. Although it may remember something about the previous bindings you set, I would recommend that you do this anyway.
3) Yes, MidiBridge will remember its state each time you run the app, so the programming need only be done once and then forgotten about.
4) Start BlueBoard and MidiBridge first (order not important), but start Loopy last so that it definitely sees the MidiBridge virtual port.
It has just occurred to me that maybe the BlueBoard's 'program change' mode may be all you need. As long as Loopy does not recognise and act on program change messages I think this will actually solve your specific problem without needing MidiBridge at all. I would suggest you test this first:
Change the setup in the BlueBoard app from 'controller' to 'program change'. In program change mode, each button press sends a program change message which is always the same value. You will need to teach Loopy to respond to the program change commands. As long as Loopy doesn't natively do something unwanted on program change (you'll soon know) this method would work.
Please post back if the program change mode works fine with Loopy.