Well, those are totally unusable to me…
That is not really the issue here… The iMic, for example, works fine on the iPad Air but DOES NOT WORK AT THE SAME TIME as somethings connected to the headphones.
Also, the NI Traktor Audio2 mkII interface I bought (and returned) didn’t work even when powered by its own power supply.
And the Griffin DJ Connect which has no power supply is reportedly working.
Anyone tried if the iOS 8.1.2 update fixed things?
Might be as you say and that’s why apple killed the possibility to use USB and headphones at the same time.
But one thing that I was always impressed with the batterylife using the DJay/iMic/headphones was the battery life. After DJing 5 hours straight I usually had around 60% battery left. So the issues with power draw must have been minimal, so it would seem strange that Apple changed it.
Also, if that is the case, the information about it should have been known to the developers by the time of the release of iOS8 and Algoriddim and other should have been able to inform us, their customers, of why it’s not working and that we have to buy new interfaces.
So it still smells like a bug to me.
Gonna install 8.1.2 now and see if anything’s changed…
Tried as well now, no luck here either.
Both Algoriddim and Griffin claim that the DJ Connect is working. Haven’t been able to find anyone who’s an actual user comfirm it though and nobody in Europe seems to have it in stock or I would have bought it. But prefer to buy it from a store in case it’s not working…
Well, unfortunately drunk guests aren’t always following those rules 
I gave up and bought the Griffin DJ Connect.
Finally found it at Just Music (Moritzplatz) for €79.
Although I hate that I had to spend money I really needed for other stuff when my old iMic should be working, the DJ Connect seems like a great product and is working as advertised… Haven’t used it for an actual gig yet so we’ll see how it performs then and if it’s draining the battery more than the iMic (I sort of suspect it does). With the iMic I still had 60% battery left after 5 hours of continous DJing!
Let it run in Automix for an hour… used 8/9% battery in that time. Of course no cueing etc was performed during that time so might be slightly higher in real use. As long as I get 7 hours out of it, I should be ok.
I gave up and bought the Griffin DJ Connect. It was rather good, but it started acting up almost immediately, and now less than two months old it sort of stopped working all together. There was no sound through the main outs, and if I unplugged and re-plugged the lighting cable, there was sound. But very disorted and totally unusable. The distortion was both in main out and in headphones.
And now to the weird part:
If I connect headphones to the iPad when the DJ Connect is connected, I can choose headphones as output option (along with DJ Connect 1-2 and 3-4).
And the iPad headphone out works at the same time as the headphone out (3-4) on the Griffin DJ Connect!!! SO WITH THE GRIFFIN DJ CONNECT YOU CAN USE INTERFACE AND HEADPHONES AT THE SAME TIME! So why isn’t it working with the iMic, I now wonder?
Mine was defect too, but found a workaround (using cue on DJ Connect and headphones on iPad). Had no time to return within the month so then the store wouldn’t give me a new one but I would have to send mine in for repair which of course takes too long…
Yes, I got the Griffin DJ Connect. But it was broken on purchase and then got worse. I can now use it by using headphones as main out and the DJ connect headphone for headphones. But the output of the DJ Connect is glitch and have to fiddle with the volume knob (haha) quite a bit before there’s sound. I fear it will stop working completely at any time… The main outs were noisy on purchase and later stopped working all together. So haven’t been too happy with the product.
I confirmed this morning that the Vestax Spin2 doesn’t seem to have the problem.
I was able to plug in the Spin2, cue from its headphone jack, and output properly. When plugging in headphones to the iPad’s jack, the dialog box popped up and I was again able to output from the Spin2 while cueing from the iPad’s headphone port.
I tested Traktor DJ with my Z1 controller and it had some weird behavior. The headphone port on the Z1 was mirroring the main out, and would only cue if I manually selected them. Crossfading left or right didn’t change this behavior. Similar behavior when headphones were plugged in to the iPad’s headphone jack also.
So, at least my Vestax works…but it does look like a greater iOS issue, rather than djay or USB devices.
Here’s a video I made this afternoon showing the issue in more detail:
https://www.youtube.com/watch?v=s3QcO…
It doesn’t matter which output is cue or main, switching between the USB at cue or main only changes what comes out of the headphone jack.
This is with iOS 8.0. I was not quick enough to get 8.0.1 to test and see if this is resolved in that update. I’ll test it first thing when 8.0.1 is reissued.
Have you watched the video I posted Warren?
One of the cards I have has stereo output and a mic input. The other is stereo only. Neither work as they should, and both worked many, many times under various versions of iOS 7.
Fiio E07K - Stereo USB DAC
Syba SD-CM-UAUD USB (C-Media CM119) - Stereo output, Mono mic input
From others:
Line6 Sonic Port
iMic
I’m glad I have my Vestax Spin2, which seems to be working properly, for use tomorrow during World College Radio Day 2014. I’d hate to resort to mono cue and main again. Ugh.
Please, Algoriddim, please let us know if you have confirmed this issue with Apple or any of your friendly staff.
i had hopes that the updates Native Instruments did to Traktor would fix the problem, but it might have made it worse in that I can’t reliably get output from a USB DAC. Oh well.
Any luck duplicating this problem we’re all having?
This topic is exactly that problem, Terrace, and we are all stuck in the same boat.
I do wish Algoriddim would confirm the problem, in the very least, and let us know if it is an issue with Apple or not.
I have pondered joining the beta testing of 8.1 to see if the issue persists, but have yet to do so.
I’m very hopeful that the iOS 8.1 release on 10/20 will solve this.
