Given your existing code base, and RT constraints, I would suggest
you consider pushing changes over to the RT thread in batches.
Basically, update the configuration the RT thread is using in
response to the NSManagedObjectContextDidSaveNotification.
It's sinking in that this might be an even
Thanks to all for your suggestions.
On 27-Mar-2009, at 18:09, Quincey Morris wrote:
the key question seems to be: what is the thread safety model of
your existing code? Generating audio from parameters and file lists
held by a different thread seems disaster-prone, so presumably your
code
Brief background: I'm porting an audio generation system to Mac OS.
The code for generating audio is in C and has run on a couple of other
OSs. It's been reasonably straight forward to model the parameters for
this system with Core Data, and I'm excited about getting CD to handle
multiple Undo
On Mar 27, 2009, at 08:08, Peter Castine wrote:
I'm porting an audio generation system to Mac OS. The code for
generating audio is in C and has run on a couple of other OSs. It's
been reasonably straight forward to model the parameters for this
system with Core Data, and I'm excited about
On Fri, 27 Mar 2009 10:09:20 -0700, Quincey Morris
quinceymor...@earthlink.net said:
The other question that comes to mind here is: why Core Data? Core
Data may simplify your life if you have a very complicated (database-
ish) data model, or if you have very many (tens of thousands) data
model
