• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Problems with iOS devices lacking a built-in microphone
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Problems with iOS devices lacking a built-in microphone


  • Subject: Re: Problems with iOS devices lacking a built-in microphone
  • From: Gregory Wieber <email@hidden>
  • Date: Sat, 16 Mar 2013 19:54:21 -0700

Out of curiosity, on which thread are you handling the tear-down and setup?

Sent from my iPhone

On Mar 16, 2013, at 3:08 PM, Andreas Gustafsson <email@hidden> wrote:

> Chris Adamson wrote:
>> You can deal with this problem by setting up a listener for the
>> AudioSession property
>> kAudioSessionProperty_AudioInputAvailable. When you lose and regain
>> audio input, tear down and rebuild the AUGraph (or the standalone
>> audio units if that's how you roll).
>
> I am setting up a listener for kAudioSessionProperty_AudioInputAvailable
> and getting the notifications as expected.  I'm disposing of the
> RemoteIO using AudioComponentInstanceDispose() when the audio input
> becomes unavailable, and recreating it when the input becomes
> available again.
>
> Recording works if the headset is already plugged in when the app
> starts, and it even works if it is initially unplugged and then
> plugged in after the app has started (once), but if it is unplugged
> and replugged while the app is running, AudioUnitInitialize() fails
> with error -10875 when I try to set up a new RemoteIO instance in
> response to the property change notification.
>
>> I imagine this is not handled by the aurioTouch example because that
>> sample code is already hard enough for beginners to follow without
>> adding the needed resilience for route changes and/or the loss of
>> input hardware.
>
> While aurioTouch2 does not specifically listen for change
> notifications for kAudioSessionProperty_AudioInputAvailable, it does
> listen for route changes, and does check the current state of
> kAudioSessionProperty_AudioInputAvailable when route changes occur,
> so it looks like it is at least trying to handle this.
>
> It would be interesting to know if this case works in 5.1.1 in other
> apps that were designed to handle it but tested against earlier iOS
> versions.
> --
> Andreas Gustafsson, 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

 _______________________________________________
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

  • Follow-Ups:
    • Re: Problems with iOS devices lacking a built-in microphone
      • From: Andreas Gustafsson <email@hidden>
References: 
 >Problems with iOS devices lacking a built-in microphone (From: Andreas Gustafsson <email@hidden>)
 >Re: Problems with iOS devices lacking a built-in microphone (From: Chris Adamson <email@hidden>)
 >Re: Problems with iOS devices lacking a built-in microphone (From: Andreas Gustafsson <email@hidden>)

  • Prev by Date: Re: Problems with iOS devices lacking a built-in microphone
  • Next by Date: Re: Some questions and problems on recording in measurement mode
  • Previous by thread: Re: Problems with iOS devices lacking a built-in microphone
  • Next by thread: Re: Problems with iOS devices lacking a built-in microphone
  • Index(es):
    • Date
    • Thread