thanks Miller and Rich for the help.
We thought at first that it might be better to package all our pattern data
together, but after reading what you guys have written, i can see that
individual values should be the best way to go.
We do have some arrays though, so that PdBase copyArray* will
I'd second what Miller said, for a different reason though: every time you
send a message from your app's main thread (the iOS / obj-c bits) into pd
(the libpd bits), a mutex will lock because the audio thread runs on a
different thread and needs to be synchronized. Breaking the lists down
(not
:)
On Wed, Apr 30, 2014 at 5:57 AM, Miller Puckette m...@ucsd.edu wrote:
Hi Matt -
From Pd's perspective at least, it would be more efficient to handle the
messages separately (some of Pd's list operations have to copy the list,
which would be expensive if done iteratively over a long
Hi Matt -
From Pd's perspective at least, it would be more efficient to handle the
messages separately (some of Pd's list operations have to copy the list,
which would be expensive if done iteratively over a long list).
cheers
Miller
On Wed, Apr 30, 2014 at 01:37:05PM +0900, i go bananas wrote:
I've got a six voice synth, each with about 20 variable parameters, and
then sequence data, etc... and all of this data is being stored by the
objective C front-end of my app.
can someone tell me, hopefully from experience, what the best format is to
send a lot of pattern data between obj C and
