|
Post by forestcat on Jan 26, 2015 21:26:05 GMT
Just purchased MIDIBridge & MIDIVision in an attempt to end the weeping and knashing of teeth re: iRig MIDI (1st version) and literally ANYTHING I own IOS-related.
The skinny: iPad 2, iOS 7.04
I can send MIDI data to the iRig DIN input via whatever, it lights up the iRig input activity LED, shows activity on that port in MIDIBridge, and MIDIVision correctly displays the incoming MIDI data. However, nothing that I have tried will result in any coreMIDI-compatible app on the iPad responding to that data, including routing directly to the app (iMS-20, for instance) within MIDIBridge. Other MIDI ports, yes, iRig, no joy.
Now here's the wierd part: If I patch the iRig In directly to the iRig Out within MIDIBridge, the incoming data now lights BOTH the In & Out activity LED's on the iRig, but NOTHING comes out of the iRig DIN output jack.
At my wit's end. Anyone have any idea WTF is going on here? Thanks.
|
|
nic
Soapbox Supremo  
Troublemaker
Press any key to continue
Posts: 2,011
|
Post by nic on Jan 26, 2015 21:45:05 GMT
Hi forestcat, Given MidiVision can see the events it sounds like this could be a channelisation issue. If MidiVision can see them, then so should any other app. Can you try the iRig with GarageBand? Normally GB is problematic co-existing with other apps, but because it listens to all channels on all ports it will be a litmus test instead. Run up GB, select a piano (always a good choice for testing) and connect a keyboard's MIDI out of some sort to the iRig DIN input and see if GB responds. Run up MidiVision, play the keyboard again and see if it picks up events. If it does, please feel free to use the 'email' button in the 'Actions' tab in MidiVision and email the files to me and I can take a look to see if the events look sane. Regards, Nic.
|
|
|
Post by forestcat on Jan 26, 2015 22:46:48 GMT
nic,
Don't have garageband. But I think I've nailed it to a defective iRig MIDI out. Part of the confusion for me was not realizing that both MIDIBridge or MIDIVision appear to interrupt an existing "flow" of CoreMIDI data if they are loaded AFTER the target app (iMS-2 in my case, and no amount of routing, etc will have any effect until after iMS-20 is closed & restarted.
I was originally trying to troubleshoot an issue w/ TB MIDI Stuff not transmitting MIDI via the iRig, even though the output activity LED was blinking. So I went back to square one, which, for me, involves acquiring monitoring/debugging tools, and proceeded to really confuse myself when nothing flowed as indicated :-)
Since I'm in the market for a new interface, is iConnect MIDI the best game in town at the moment?
|
|
nic
Soapbox Supremo  
Troublemaker
Press any key to continue
Posts: 2,011
|
Post by nic on Jan 27, 2015 13:16:23 GMT
Hi forestcat, The iConnectivity (I have a 2+) are solid units but you do have a bit more cabling mess with them. If you get the power supply I think you can power the iDevice too. The iRig MIDI (the one you have) does also handle power whereas the new one does not (I think). If being able to power the iDevice while working is important than that is something you need to consider. If it isn't there is a wider range of units that will work from simple cheap USB/MIDI 'cables' to iConnectivity or m-audio units with more ports. As long as the interface is 'USB Class Compliant' it should work. Regards, Nic.
|
|