the technical reason is that clock timeouts can't happen in intervals smaller than 64 samples (pd's scheduler blocksize) *), so any objects relying on clocks (e.g. [print~], [bang~], [line~], [vline~], [del], [pipe], etc) might not work as expected.
Christof *) more generally, clock timeouts are limited to the largest parent blocksize. see attached patch. > Gesendet: Samstag, 28. Juli 2018 um 10:45 Uhr > Von: "mario buoninfante" <mario.buoninfa...@gmail.com> > An: Pd-List <pd-list@lists.iem.at> > Betreff: [PD] triggering [print~] faster than every 64 samples > > Hi, > > I'm trying to trigger [print~] every sample. in the same patch I'm using > [block~ 1 1 1] to change the block size and [metro 1 1 samp] to trigger > [print~]. > > but I noticed that [print~] is yes printing 1 sample at time (in accord > with the block size) but only every 64 samples. so it receives a bang > every sample but prints every 64 (default block size). > > can you guys help me understanding why? I'm pretty sure I'm missing > something here :D > > > cheers, > > Mario > > > _______________________________________________ > Pd-list@lists.iem.at mailing list > UNSUBSCRIBE and account-management -> > https://lists.puredata.info/listinfo/pd-list >
clock_test.pd
Description: Binary data
_______________________________________________ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
