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: "Phil (omenie.com)" <email@hidden>
- Date: Tue, 8 Jun 2010 10:30:57 +0100
Chris
FYI I've used 'printf over WiFi' to debug a hardware interface I've been working on - just run up a TCP server on the Mac that accepts and prints everything sent to it, it's a lifesaver.
On 8 Jun 2010, at 10:23, Christopher Penrose wrote:
> Bug report on the way... Thanks for responding on the first day of WWDC, must be busy! I answer your other questions below:
>
> On Jun 7, 2010, at 1:51 PM, William Stewart wrote:
>
>>> 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
>
> You are right, thanks!
>
>>
>>> 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?
>
> Yes, the iPod app on the iPad plays audio reliably through the Turtle Beach Micro II device. I am even using SPDIF and routing it into my iMac via an M-Audio 410, which is a fantastic development.
>
> In my own app however, my audio callback is never called, in both the situation where my app starts with the device already plugged in (after being used by the iPod app successfully) and in the situation where I plug in the device after my app has already launched and established a connection with the iPad's internal audio hardware. In both situations, after removing the Turtle Beach device my aurio audio callback resumes and audio plays through the iPad's internal speaker or analog output. Just to be clear: the aforementioned behavior occurs when the audio session is set to MediaPlayback. When the audio session category is PlayAndRecord, my app plays audio fine through the iPad hardware, as it simply doesn't recognize the attached interface (which you indicated to be expected behavior for a playback only audio interface).
>
> As for debugging I was slow to figure out that I could do printf debugging by writing to a file within the Documents folder so I have that recourse at least now. But lack of a debugger is worth reporting as you suggest I do.
>
> Thanks,
>
> Christopher _______________________________________________
> 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