Re: [PD-dev] timing of a clock_delay(x-x_clock, 0);

2006-12-30 Thread Mathieu Bouchard
On Thu, 28 Dec 2006, Miller Puckette wrote: It's indeed as soon as possible, except that if someone else has previously scheduled something ASAP that ASAP will get in earlier than yours. You can chain arbitrarily many clock_delay(..., 0) calls without DSP or event polling getting in between.

Re: [PD-dev] timing of a clock_delay(x-x_clock, 0);

2006-12-30 Thread Miller Puckette
That would be an error (silently 'corrected' to delay zero). On Sat, Dec 30, 2006 at 03:12:19PM -0500, Mathieu Bouchard wrote: On Thu, 28 Dec 2006, Miller Puckette wrote: It's indeed as soon as possible, except that if someone else has previously scheduled something ASAP that ASAP will get

[PD-dev] timing of a clock_delay(x-x_clock, 0);

2006-12-28 Thread Hans-Christoph Steiner
If I issue a clock_delay(x-x_clock, 0), will the registered tick function be executed in the same clock tick, or will it always wait for the next clock tick? Basically, I am looking for a way to schedule something as soon as possible. .hc

Re: [PD-dev] timing of a clock_delay(x-x_clock, 0);

2006-12-28 Thread Miller Puckette
It's indeed as soon as possible, except that if someone else has previously scheduled something ASAP that ASAP will get in earlier than yours. You can chain arbitrarily many clock_delay(..., 0) calls without DSP or event polling getting in between. cheers Miller On Thu, Dec 28, 2006 at