Re: CoreAudio vs CoreData
Re: CoreAudio vs CoreData
- Subject: Re: CoreAudio vs CoreData
- From: patrick machielse <email@hidden>
- Date: Fri, 14 Oct 2011 14:43:31 +0200
Op 14 okt. 2011, om 02:54 heeft Paul Davis het volgende geschreven:
> suck the data out ahead of time, and make it available to the render
> callback via some other (lock- and block-free) method.
>
> CoreData is not a suitable place to store dynamic, realtime data
> (where "realtime" is in the audio sense, not the financial trading
> sense). if you need to "store" modifications by the user, don't go
> directly to CoreData except as a serialization technique.
If I interpret correctly, that would approach would erase most advantages we would gain by using CoreData in the first place (f.i. easy undo support) -- and add more code. Your advice would be to not use CoreData and just use a custom data representation?
p.
--
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