iOS updates are slowly killing off my audio and midi devices

Ringleader

It started when updating from iOS6 to iOS7 when my line 6 FBV mkii midi controller suddenly stopped working. Tested it on my son's ipad 1 with iOS5 and it worked there as normal. But just an error message that it was not compatible with my iPad Air with iOS7 so I sold it.

Today I pulled out my trusty tascam us-800 and plugged it into my iPad Air with iOS7.1 and it was recognized but no sound coming out of the headphone jacks. So I tested it on my wife's iPad 3 with iOS7 and it worked fine. Swapped it over to mine again and still nothing. I even went and bought a 30pin to lightning converter cable to see my lightning CCK was the issue but still no output on my Air.

So... I'm pissed, and even more I'm confused. These are both class compliant devices. If I can't trust that class compliant devices are going to work on iOS then what can I trust? Aside for MFi devices, ensuring that a device was class compliant was the "key" to it working with iOS devices via a CCK. Is iOS regressing? Is it a ploy to get me to buy all MFi devices? Anyone else noticing this?

ShawnLeonhardt

Just like in a computer when you install new software, files can get corrupted. Perhaps you need to do a reset. First just try shutting down. Then try reset. Back everything up first... this does not sound like normal behavior.

supadom

A similar thing happened to me with novation launchkey. Are you using genuine CCK? Mine is not. Works with most but some devices are super fussy.

Ringleader

Yes, I have a generic 30 pin but it sits in the drawer and I only use genuine CCKs (30 pin and lightning).

And it is unlikely that it is a reset issue since another person experienced the same thing with the same Line 6 controller. http://forum.loopyapp.com/discussion/comment/6264#Comment_6264

I forgot to mention the iUR2 (which I also own) that became a paperweight once iOS7 was released. However, it does still works with my jailbroken iphone 4 with iOS5. Tascam even acknowledged this issue but haven't done anything to fix it (they are horrible with device support/fw updates). http://www.tascam.eu/en/iur2.html

In addition to my Apogee one I like to have an audio/midi interface on hand that supports 4 or more audio inputs for times when I need this. I thought I had one (us-800) but now that ship seems to have sailed. I've been looking at the RME UCX and other bigger class compliant interfaces but now I am gun shy to get anything since there are no guarantees that they will continue to work as iOS develops. It's just frustrating and makes me wonder if I am missing something here? Is there another aspect to iOS compatibility that I am overlooking?

obiwahnkentobi

I bought an original! ios adapter 30pin<>lightning to us my "old" stuff with the new ipad mini2,
Thumbs up apple for this useless adapter, nothing worked with it....
New cck-lightning and it worked again with quneo/korg nanokontroll2/....
A forgett the useless original 30pin<>lightning adapter worked for charging, nothing more.
So i buy a charge adapter for 30 bugs....WTF!

telecharge

I would try a reset if you haven't and test it before you restore your backup. Also, Tascam was recently acquired by Gibson, so device support and updates may improve.

MusicInclusive

@obiwahnkentobi - just want to make sure I'm reading you correctly. Are you saying that you had an Apple 30-pin -> lightning and it didn't work, but you bought another and it did? Or was it indeed a CCK -> lightning? Or both? Also - I note you tried on a mini 2 - do you have another iDevice with lightning to try it with - just wondering if it's a problem with the 30->lightning with the newer iPads...

obiwahnkentobi

i bought a new cck-> lightning and this works. (Ipad mini2 / iphone 5s)

Ringleader

Tried reset, thought it fixed it, about 5 mins later the audio became distorted and/or dropped signal after multiple attempts. Now it's for sale on CL. Ugh, life's too short to be constantly putzing with this crap. I'm taking a break!

supadom

Haha, you may have made the best decision. For your mental health at least. lol

StormJH1

This is a legit complaint, and one of the reasons I have argued for why a more "realistic" price point for iOS software wouldn't work. For the whole thing to work, there has to be people like us that send money to the developers, and I'm happy to do it. But the difference between an iOS app and a 30-year-old BOSS guitar pedal is that the latter still works like brand new even though it survived the end of the Cold War, the introduction of PC's and digital technology and so on. iOS software and, by extension, the peripheral hardware that works with it, can become non-functional simply because Apple updates something, or changes a jack from 30 pin to Lightning. That's not even addressing the issue of whether iOS devices will still be in regular use 10 years from now, or what the "it" thing will be then for mobile music. It's a low price for the software, but it's far from futureproof.

And the hardware that goes with it is worse. I'd be interested in buying a MIDI controller or keyboard to go with my apps, but how do you pick one? The Akai SynthStation25 is one that I've seen some apps REMOVE support for. I suppose if it's USB, you can always find an adapter and it may be usable on other devices, but it is a risky investment.

peanut_gallery

I'm wondering if this is the fate that has befallen my Griffin StudioConnect. I had one that worked perfectly until about a week after the release of iOS 7.1 I was using the Apple Branded 30 pin to lightning connector and it all worked flawlessly until mid March (I didn't make the connection until now with the 7.1 release).

It was under warranty, so I had a new one sent and it also appeared to not work right out of the box, but I'm wondering if the issue is with 7.1 and not the StudioConnect unit itself.

Edit: Also wanted to add, that my iRig Keys works just fine with the same 30 pin to lightning cable I was using with the StudioConnect, so I believe the cable is not the issue.