hi again,
that seems to be the case, since [del] works by setting a clock, and clocks fire only at DACBLOCK (hardwired to 64) boundaries (whatever that means).
Krzysztof
sme wrote:
i think this is, because the delay-object cannot go below a vectorsize of 64. the block~ 1 does not seem to change this...
Frank Barknecht wrote: ...
But I do have a [del x] object, that bangs the textfile to put out
the next
message.