Sample rate and block sizes can change as a result of messages to "block" objects. This causes DSP to be re-sorted. The only safe way I know to determine block size is to make a tilde object with a signal input or output and catch "dsp" messages.
cheers Miller
On Sat, Jun 11, 2016 at 08:02:47PM +0200, Thomas Grill wrote:
Dear all, i am sorry, my previous email to the list was obviously GPG-encrypted.
My question is the following: What is the best way to find out the DSP block size within an abstraction/sub patch? It could be set differently than 64 samples using block~ in a parent patch.
Right now, i am counting audio samples but this is not ideal since it is non-instantaneous and can therefore not be used for initialization purposes at the time of loadbang.
thanks, Thomas
-- Thomas Grill http://grrrr.org
Am 11.06.2016 um 18:54 schrieb Thomas Grill gr@grrrr.org:
<encrypted.asc>
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list