iOS: Multiple AUs versus everything in one render callback
iOS: Multiple AUs versus everything in one render callback
- Subject: iOS: Multiple AUs versus everything in one render callback
- From: Hari Karam Singh <email@hidden>
- Date: Fri, 06 Jul 2012 20:26:29 +0100
- Expiry-date: Tue, 04 Sep 2012 00:00:00 +0100
- Keywords: iOS
- Organization: Amritvela
I'm doing some development on the custom sampler and audio engine for my (iPhone 4+) app, particularly adding recording and send effect features. I'm stuck trying to decide whether to go down the route of having everything handled in one big RemoteIO render callback or breaking it up into separate AU nodes.
Might anyway know whether a more complex AUGraph with multiple RemoteIOs and a mixer AU to sum it all imposes significant overhead compared to doing it all in a single, well-tuned render callback? Is there any other reason why one would want to go one way or the other (such as perhaps the AU boundaries clipping/truncating the audio)?
Performance is big issue and I'd probably just go with the single render callback but I don't want to miss out on the ever growing list of fx AUs available.
Thanks!
Hari Karam Singh
http://soundwandapp.com/
http://club15cc.com/
_______________________________________________
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