Re: RemoteIO and iPad class compliant interface issues
Re: RemoteIO and iPad class compliant interface issues
- Subject: Re: RemoteIO and iPad class compliant interface issues
- From: William Stewart <email@hidden>
- Date: Mon, 7 Jun 2010 13:51:11 -0700
Please file a bug report (including a report about the debugging problem)..
On Jun 6, 2010, at 3:10 AM, Christopher Penrose wrote:
> Hey folks,
>
> I am trying to get my app to work with a class 1 compliant device on the iPad. The device sends audio out nicely with Apple's iPod application. My first issue:
>
> The device I am testing with is an audio out only device (a Turtle Beach Micro II). Adding the device while my app was running did nothing when my audio session category was set to kAudioSessionCategory_PlayAndRecord, the preferred category for the app.
Yes, because your device is audio out, so it can't run in play and record.
> I checked (see my postscript below) and I simply did not receive route changes with my listener at all. Is there any way to override this behavior and have a route change get sent or is my app locked out from using a device that conflicts with its audio session category setting?
a bug report would be good (but I'm not sure what we'd do about this)
> If the latter is true, I can use settings to force my app to use kAudioSessionCategory_LiveAudio on launch.
_LiveAudio is deprecated. Please use the MediaPlayback category instead
> But it would be nice if I could support playback only devices cleanly regardless of the current session category of my app.
good point.
>
> The other more confounding issue is that when I do receive and handle the route change (in the situation where I have disabled recording at launch and use a session category of kAudioSessionCategory_LiveAudio) after the audio interface is added, my audio callback ceases to be called (despite my previously adequate route change handling as my app handles headphone to external speaker transitions fine). I dispose of the current aurio and initialize and start a new one within the route change listener.
I don't think you need to do this - the IO unit should work fine across route changes
> I also get the same behavior when I launch the app with the audio device already attached. I am not sure what I am missing. The app doesn't hang or crash and playback immediately resumes through the iPad speaker or headphone outputs as soon as the external interface is disconnected (more evidence that my route change handling is at least partially correct).
As far as I know other apps will work in this scenario, but can you verify that. If you are plugged in already, does your app then play audio out USB?
Bill
>
> Any input would be appreciated!
>
> Christopher
>
>
> p.s. debugging aurio is really fun with this dongle; I can't printf or nslog to a console and I can't use a debugger so I have been using exit() as a debugging tool rofl _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Coreaudio-api mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden