[PD] samplerate~

IOhannes m zmölnig zmoelnig at iem.at
Tue Feb 18 11:29:11 CET 2020

On 2/18/20 11:56 AM, Peter P. wrote:
> * IOhannes m zmölnig <zmoelnig at iem.at> [2020-02-18 10:30]:
> [...]
>> remember, that a [loadbang] in a child-patch fires after a [loadbang] in
>> the parent patch (this is by design).
> Does "child-patch" mean subpatches as well as abstractions?


>> if you have a child-patch that uses [loadbang] to query [samplerate~],
>> and in a parent-patch you use another [loadbang] to change the
>> re-sampling, then the re-sampling will change *after* you have queried
>> the samplerate.
> I can't seem to understand the logic of the sequence of the three
> loadbangs in this example. Why would "another" loadbang in the parent
> patch fire after the one in the child-patch?

i only count two [loadbang]s.

once the patch is built, the loadbangs start to fire.
first, the [loadbang] in the child-patch fires, querying [samplerate~]
and outputting something like 44100.
then, the [loadbang] in the parent-patch fires, sending something like
[set 1024 1 2( to [block~], thus upsampling the entire parent-patch
(including the child-patch) by a factor of 2.

the actual samplerate (of both parent- and child-patch) is now 88200,
but [samplerate~] has already reported 44100.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.puredata.info/pipermail/pd-list/attachments/20200218/a832e38f/attachment.sig>

More information about the Pd-list mailing list