Some of you have been following my ranting about MIDI on the iPad. Suffice to say, I've been doing a lot of research, emailing, buying, and testing. Here goes:
MIDI on the iPad is only half realized. This is not the fault of Apple or the iPad. These are shortcomings of the apps themselves.
You've got 4 basic connection options:
1. Line6 MIDI Mobilizer
2. Apple Camera Connection Kit plugged into a USB-To-MIDI cable like the M-Audio Uno. This is a USB to 5pin connection.
3. A piece of hardware (synth or controller) plugged into the Apple Camera Connection Kit plugged into the iPad.
4. WiFi MIDI - via Apple's MIDI Networking or whatever hocus pocus roundabout system that PCs use.
The problem? There are lots of them.
The App Issues
This is the biggie. MIDI is only half realized on nearly every single app. While app developers have updated their product pages on iTunes to say something like "MIDI support!", it's all just a half-truth. Hardly any of them have offered MIDI send from the app.
I was going out of my fucking mind trying to figure out why some apps could receive MIDI data, but were completely dead when trying to send. I'd hook shit up differently, say a prayer, light some candles...no luck. Well, after lots of emailing and forum exchanges, it's because they haven't fucking implemented them in their apps yet.
How's about a note to that effect on the product page? I realize that app developers have lives outside of their work, but I don't care. How the fucking Korg iMS-20 ONLY has MIDI IN is just fucking well beyond me. No clock sync, no MIDI out, no Line6MM support. Jebus.
Hardwire Connection Choices
Both the Line6 MM and the CCK are proprietary (CCL in the sense that it ties into Apple's Core MIDI). The app developers need to code their apps to support one, the other, or both. This isn't the universal 'MIDI Works Everywhere' type of thing we've all known and loved - where the hardware or software developers simply follow the MIDI guidelines for implementation. The Apple CCK isn't just an adaptor. The devs must provide code in their apps to work SPECIFICALLY with the CCK/Core MIDI. Does that mean the Line6MM doesn't use Core MIDI? I think it does. It respondes to standard MIDI coding that the devs provide in their apps, but then feeds the MIDI data through their proprietary device - which has some sort of translator code going on...? I think that's what is happening here. Fuck if I really know, but that's a pretty good guess.
Some apps like NLogPro Synth have been written for both. Some just one or the other. And therein lies the first big problem. If you've got the Line6MM, you are shit out of luck in terms of using an external keyboard with the Korg iMS-20 syth app. Same goes if you've only got the CCK, and one of you're fav apps doesn't support that connection type.
I'm already pissed off, but I must maintain my composure.
At this point, you may well have to own both types if your library is as large as mine is (about 8 apps or so).
Right now, the Line6MM supports more apps; but that's because it's been out longer. This is likely to change towards the CCK.
Clock Sync
Molten is the only app that's got it. Period. The funny thing about clock sync is that app developers I reached out to and heard back from (about 10) were genuinely perplexed that I was asking for this feature.
Them:
"Why would you need that?"
Me:
"Because you use words and phrases like 'professional' and 'taking mobile music to a whole new level' and 'professional/studio grade' when describing your app?"
I'm still scratching my head over this one.
It's NOT THE MOTHERFUCKING CABLE
There's been a number of people I've seen that make claims about the M-Audio MIDI Uno (or a handful of other USB-To-MIDI cables) not working with this or that app or the iPad in general. I'll say this right now: It's Not The Mother Fucking Cable.
I did a simple test. It went like this:
Loaded a great little iPad app called MIDI Monitor onto my iPad. Then I started up a program on my MacBook called *golly!* MIDI Monitor. Then I started up Ableton on the MacBook. The iPad MIDI Monitor app has a window to view MIDI activity, as well as some nice knobs and faders. With the M-Audio MIDI Uno connected to the Apple Camera Connection Kit, I started moving faders on the iPad app. The MIDI out light on the Uno started flashing, Ableton's MIDI signal started flashing, and MIDI Monitor on the MacBook side recorded the activity. That simple test proved that the iPad works just fine with the Uno, and that there's no issues with the iPad itself in terms of MIDI Out. A MIDI IN test on the iPad had the same results. Perfect communication. That means one thing:
Any and all MIDI issues are 100% on the developer side. It's got fuck all to do with your cable brand (unless it's really old), and fuck all to do with the iPad.
A SPREADSHEET
A guy named wmpeters over at the Korg forum saw my ranting and came up with this nifty little spreadsheet. It's not complete, and needs a clock sync column, but it's very telling nonetheless.
https://files.me.com/wmpeters/ktpgy3
I'll try to add to that list, or post new findings here.
I think this is a case of ENORMOUS expectations on my part simply not being met. But, I swear to you, in dev forum after dev forum I'm the only douchebag asking about this stuff. I think we'll eventually see everything working properly, but God knows when.
Stay tuned.
I don't own an iPad (yet) but will look to be in the family soon. The one thing holding me back is my need for better assurance that the whole MIDI thing works promising (without the use of WIFI MIDI--I'd much rather use cable connection right now) WTF is up with those guys you talked to wondering why you were so curious about clock sync?? Seriously? This shit is important 
I look highly forward to the future of midiCore & iPad awesomeness 
