[ios] graph init and start in separate thread
[ios] graph init and start in separate thread
- Subject: [ios] graph init and start in separate thread
- From: steph ohara <email@hidden>
- Date: Wed, 25 May 2011 01:11:23 -0700 (PDT)
hello
i have 2 questions regarding creating, initialising and starting a coreaudio graph with ios devices
1. is it safe to place the init/start calls in a separate thread thus "free-ing" the main thread to do other work such as ui updates? i have tried this technique and it works but i have not tested on all devices.
2. this is
more an open question to developers. what is the more efficient technique if one were to build say a modular audio structure. either (a) use coreaudio's built-in graph/audio unit or (b) roll out your own. as an example
technique (a) create an AUGenerator -> AUFilter -> AUDelay ->AUOutput, each being a audio unit.
technique (b) create an AUOutput and inside rendering, have a custom node/graph structure.
i am mostly interested in efficiency (cpu use) and if there are accumulative bottle-necks between AUUnits.
cheers steph
_______________________________________________
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