[PD] how to know line~ has finished

Frank Barknecht fbar at footils.org
Mon Jul 16 10:10:52 CEST 2007

Andy Farnell hat gesagt: // Andy Farnell wrote:

> If you would like a bang message when [1 300(-[line~] is complete then you merely
> have to say
>        [bang(
>          |
> [t       b         b]
>  |                |
> [del 300]      [1 300(
>   |               |
> [outlet done]   [line~]
>                   |
>               [outlet line]
> Even though the evaluation goes right-left and depth first the bang appearing
> at [outlet done] happens at the **exact** logical time that [line~] is complete.

As Roman noted it is not exactly exact if you're starting your [line~]
and [delay] from a clock-delayed message, because then [delay] will
still keep logical time, while [line~] is quantized to 64 samples.

But in practice this generally isn't an issue: If such accuracy is
required in an application (e.g. granular synthesis), nobody  would
(or should) use [line~] anyway, [vline~] is the line to go for here.

If one *really* wants get back the inaccurate block-quantized delays
one's used to from Max, attached patch illustrates a possible approach
using [bang~].

 Frank Barknecht                 _ ______footils.org_ __goto10.org__
-------------- next part --------------
A non-text attachment was scrubbed...
Name: un-clock.pd
Type: application/puredata
Size: 1946 bytes
Desc: not available
URL: <http://lists.puredata.info/pipermail/pd-list/attachments/20070716/3ae6bf82/attachment.bin>

More information about the Pd-list mailing list