|
Post by dylanpeters on May 26, 2014 0:07:12 GMT
I've been having issues running both apps through Audiobus and controlling Loopy via my FCB1010 and NanoKontrol. That being said, no matter what channel I put the receive MIDI to on the IK Multimedia Voicelive app to, it still changes the preset. I emailed them to see why this is. This was their response:
"We have received reports of this and have certainly forwarded this to our development team. It appears MIDI Program Changes will be received regardless of what the MIDI Channel is set to in VocaLive's settings.
We hope this will be resolved in a future VocaLive update. Please note that it may take some time for our development team to have an update ready. We do not have a specified timeframe for release."
Can Midibridge help me out in this regard? To make sure the FCB only controls Loopy?
|
|
nic
Soapbox Supremo  
Troublemaker
Press any key to continue
Posts: 2,011
|
Post by nic on May 26, 2014 7:20:14 GMT
Apps that insist on picking up events from all MIDI ports in the system indiscriminately are a core (ahem) bane with CoreMIDI. iOS will not permit a 3rd party app to sit between a CoreMIDI device and another app. Thus, MidiBridge cannot prevent the IK app from seeing those events from your FCB directly.
Having said that, there are two options (in outline form):
1. Configure your FCB to send something different MIDI-wise instead of program change messages and either re-learn Loopy to deal with those or use MidiBridge to map the new messages back to program changes which are fed only to Loopy by MidiBridge. The IK app will see those events, but will not do anything with them. I don't know the FCB so I am not sure what can be done.
2. Get hold of a Line 6 Midi Mobilizer (version1, the original) which is not a CoreMIDI device and use that in place of your current MIDI interface you use with the FCB. You can pick up those Line6 units on ebay for peanuts. The benefit is that apps like the IK ones, GarageBand, JamUp et. al that listen promiscuously cannot see the MIDI interface directly. You can then use MidiBridge to route the Midi Mobilizer events to Loopy only.
For more assistance/detail on either of the above options just post a followup and I can expand.
Regards, Nic.
|
|