Remote IO input breaks when used after VPIO. How do I clean up after VPIO?
Remote IO input breaks when used after VPIO. How do I clean up after VPIO?
- Subject: Remote IO input breaks when used after VPIO. How do I clean up after VPIO?
- From: Michael Tyson <email@hidden>
- Date: Tue, 26 Jun 2012 23:43:43 +0200
Hi!
I mentioned in an earlier thread that died a death ("Echo removal vs latency: Switching between VPIO and Remote IO") that I was having trouble using the Remote IO audio unit after using the Voice Processing IO unit - the input level for the RIO unit was extremely low after using the VPIO unit, and a sensitive tester tells me the audio quality is reduced as well. If I quit and restart the app and use the Remote IO unit first, this input level issue is no longer present.
My question: How does one correctly shut down and clean up after using an Audio Unit? Is it supposed to be sufficient to simply call AUGraphClose and DisposeAUGraph? Is there something else I need to do?
I need to be able to switch between using VPIO and RIO, as VPIO performs vital echo cancellation and feedback reduction when the app is used via the speakers & microphone, but provides very high latency. I need to offer low-latency audio, and this is only possible with RIO - which is perfectly adequate for use with headphones, as echo cancellation is not required. I need to be able to transition between these two states without the mess-up which is currently happening.
Of course, I can work around the issue to some extent - for example, I can remember when VPIO was used, and automatically increase the input gain for the RIO unit, but this is obviously a hack. I'd prefer to address the root cause, whatever that may be.
Any thoughts?
Many thanks,
Michael
_______________________________________________
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