[PD-dev] scheduling: clocks & audio
mpuckett at man104-1.ucsd.edu
Thu Aug 21 18:51:52 CEST 2003
Actually, you can write control functions that take any "reasonable" amount
of time to execute... they just can't exceed the audio FIFO size, and as
noted earlier, can't be called so often that Pd can't catch up between calls.
Something about this (in a more general context) is in my "FTS" article
on http://www.crca.ucsd.edu/~msp/publications.html (number 17).
On Thu, Aug 21, 2003 at 02:13:07PM -0400, Yves Degoyon wrote:
> >Well, yes. you better write functions that take less that
> >1.45 ms to finish, .. .much less. PD is not multithreaded or
> >asynchron, thats what makes messages deterministic wrt to the
> >audio processing.
> hum, that's right but looks like there's no way of
> achieving some longer operations, in fact,
> if you know some operations will take time,
> you just have to thread them,
> check out cooled~ for an example of this.
> PD-dev mailing list
> PD-dev at iem.at
More information about the Pd-dev