CoreAudio vs CoreData
CoreAudio vs CoreData
- Subject: CoreAudio vs CoreData
- From: patrick machielse <email@hidden>
- Date: Thu, 13 Oct 2011 23:05:37 +0200
Hi,
I'm currently involved in the developement of an audio processing application which uses CoreAudio. In a nutshell it construcs a AUGraph on the main thread which is then played back by AUFilePlayer.
The played audio files and processing settings are stored within a document using CoreData. The upshot is that the high priority audio thread will access managed objects in read / render / processing callbacks.
So far we've encountered some problems: CoreData isn't very threading friendly, locking the NSManagedObjectContext from the render thread seems a sub-optimal solution.
My (broad) question: is CoreData + CoreAudio a viable combination? Are there any common problems or well known caveats to be aware of?
Thanks,
patrick
--
Patrick Machielse
Hieper Software
http://www.hieper.nl
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