[PD] triggering [print~] faster than every 64 samples
mario.buoninfante at gmail.com
Sat Jul 28 11:50:29 CEST 2018
thanks for that, this clarifies quite a lot of things. that said it
seems that objects like [del] and [pipe] can deal with this kind of
situations (ie [del 1 10 samp]). the "issue" seems to appear when you
start using "hybrid" objects (control signal to audio signal or the
other way around). am I right assuming that?
On 28/07/18 10:43, Christof Ressi wrote:
> 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.
> *) 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.buoninfante at gmail.com>
>> An: Pd-List <pd-list at lists.iem.at>
>> Betreff: [PD] triggering [print~] faster than every 64 samples
>> 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
>> 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
>> Pd-list at lists.iem.at mailing list
>> UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
More information about the Pd-list