hi jasch and thomas
this approach has some disadvantages. first, [line~] does execute messages only on block boundaries, that means the start is floating somwewhere around between now and 1.45ms later (with blocksize of 64 @ 44100Hz sr), though i don't know if [line~]'s endpoint is quantized to a block boundary as well. however, [threshold~] does send 'bang's on blockboundaries as well. further, if possible, i would avoid 'measuring' the output of [line~] with [threshold~], since that means converting a message to signal and then back from siglal to a message again. this isn't necessary at all here, because [delay] does exactly what you want (see andy's post about the 'why'). to have it _really_ (even subsample) accurate, you could use [vline~]. [vline~] uses scheduled messages (that are generated by [delay], [metro] and probably other objects) to start a ramp at an arbitrary time, not only on the blockboundaries. using a [vline~]/[delay] construction is far the best solution for your needs, i'd say, jasch; and both objects are internals.
roman
On Sun, 2007-07-15 at 16:18 -0400, Thomas O Fredericks wrote:
Line~ is not the same as line~ But you can simulate Line~'s behavior with Pd's basic objects. See the attached patch.
Tom
On 7/15/07, jasch j@jasch.ch wrote:
hmm, errm, yes well, i'm actually running PDa on an ARM procesor ;=)
anybody wants to port cyclone to PDa ? (hello fixed point DSP...)
/*j {chuckles}
You can also use Line~ or curve~, both from the cyclone lib and included in Pd Extended.
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de