On 2/18/20 11:56 AM, Peter P. wrote: > * IOhannes m zmölnig <[email protected]> [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?
yes. > >> 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. gsdmr IOhannes
signature.asc
Description: OpenPGP digital signature
_______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
