Hi,
I'm currently creating some analysis patches which have to run upsampled (simply because I don't want to wait ages). Inside these patches I need to know how many samples have been passed (or how much "upsampled time" has passed). So I can't use [delay] and made a counter which counts samples, based on current blocksize and bang~.
I get the current blocksize from [bang~] [timer] and [samplerate]. (see attachment) But in upsampled patches the [samplerate~] outputs the "upsampled" samplerate, so my calculated blocksize is upsampling-factor
is there a way to get the "upsampling factor"? or is there already a blocksize based [delay] for messages i have overseen?
attached the abstraction I use for block size at the moment.
cheers
; artin
I get the current blocksize from [bang~] [timer] and [samplerate].
(see attachment) But in upsampled patches the [samplerate~] outputs the "upsampled" samplerate, so my calculated blocksize is upsampling-factor * audio-samplerate.
hmm. this seems to be only the case when the logical time for bang~ happens to be below the duration for a 64 samples block (or perhaps below 1ms?). I found an old thread in the list from 2002 which seems to explain my problems:
http://lists.puredata.info/pipermail/pd-list/2002-04/006123.html
thanks anyway
cheers ; artin