When to stop/start/reinitialize an AUGraph?
When to stop/start/reinitialize an AUGraph?
- Subject: When to stop/start/reinitialize an AUGraph?
- From: Zachary Kulis <email@hidden>
- Date: Wed, 20 Oct 2010 10:25:45 -0400
Hi everyone,
I was wondering if anyone could provide some information on exactly when
it is necessary to stop, uninitialize, re-initialize, and restart an
audio graph.
For example, is it necessary to perform these steps when:
a) Changing the audio session category
b) Enabling Bluetooth input
c) Changing the "enable mixable audio" setting
d) Changing the "EnableIO" setting on an I/O audio unit
I have performed significant stress testing, and have discovered that
performing a full stop, reinitialization, and restart of an audio graph
when using the VoiceProcessingIO unit is quite problematic. By
repeatedly looping the above (stop, un-init, re-init, start), eventually
the AUGraphInitialize returns a -50 error. The issue does not occur
with the RemoteIO unit.
I realize that these issues may stem from a bug in the VPIO unit --
however, I am looking for a quick workaround. If I can eliminate an
unnecessary reinitialization and restart of the audio graph for (a)-(d)
above, then I think the issue will be solved.
Thanks very much in advance!
Zach
_______________________________________________
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