Re: CoreAudio vs CoreData
Re: CoreAudio vs CoreData
- Subject: Re: CoreAudio vs CoreData
- From: Iain McCowan <email@hidden>
- Date: Fri, 14 Oct 2011 07:32:15 +1000
Hi Patrick,
I've developed an application using both Core Audio and Core Data, but have taken the approach of just storing the audio file names (and other metadata) in Core Data and storing the audio in conventional audio file formats in a directory structure.
This has proven a good way to play to the strengths of both APIs. Not sure if you have specific requirements of storing audio in your database directly, but it seems this will be prone to issues both with slowing down the database due to lots of data and with the audio access as you mention.
cheers,
Iain.
On Fri, Oct 14, 2011 at 7:05 AM, patrick machielse
<email@hidden> wrote:
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
_______________________________________________
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